Because hey, if 30-40 people in velvet rainbow butterfly jumpsuits can't run around in the city and advertise a product, then I say the terrorists have already won.
For the person who is learning, it's beneficial to see exactly which package a particular class belongs to.
I agree completely, but in a printed book paper costs money. An entire page of imports in a code sample doesn't help the reader at all and simply wastes trees.
I'm def in the "start importer" camp. The only time you really need to explicitly import individual classes is to resolve a class name conflict (e.g. org.cpfeifer.ListItertor and java.util.ListIterator).
In the past I have used individual imports if I was using an external library and wanted to make the dependancies explicit. But in 1.4 they through in the kitchen sink (60% more classes than 1.3), so it's not as big of deal as it used to be. And I'm lazy.
I think for keeping Taco gainfully employed she should buy us (each, not collectively, it is cold and flu season) a beer at the next/. meetup in Ann Arbor!
Just like many companies that have an official policy to use WebSphere find many of their applications being deployed on Weblogic.
Now that's shelling out the big bucks. I don't know many orgs that could afford lic's for 2 different app servers, no matter how many of each there are deployed.
Either that or they're downloading the demo versions and reinstalling each month. =^)
That means if you have a 4 CPU machine, you need to buy 4 1 year contracts of support that run concurrently. How crazy is that?
I agree with you, but Management(r)(tm) eats this stuff up with a spoon as "cost of doing business."
Either way it doesn't matter to me, I just want a fast java app server that always works and doesn't provide any surprises. If JBoss suits your needs, use it and keep your money in your pocket. If the suits want name brand parts, show them the price tag and hold out your hand.
Or better yet, show them the two price tags (BEA vs. JBoss) and ask them to pick one.
Isn't the purpose of J2EE to avoid vendor lock-in? If that is the case then a generic EJB book coupled with the WebLogic manual should do the trick.
Don't make me laugh, my lips are chapped.
But seriously, yes that is the point. But each vendor has it's own little deployment nits. In my own experience, an app will cross deploy between BEA and JBoss with little/no effort. But cross deploying between BEA and iPlanet or WebSphere is a totally different (and far more frustrating) story.
or actually give you a full fledged app server to begin with (JBoss)
This is true, but BEA is the largest player in the app server market and many large organizations that currently are betting big on J2EE have a hard time basing their business on free software. You need someone on the hook when things go wrong. You need guarantees.
Here's an entry from Moby's journal where he claims that bands with technically savvy audiences don't do well in the charts because their fans rip & burn their CDs. I guess he's a little bitter about '18' not doing as well as 'Play'.
My $.02: I listened to '18' on MP3 with full intention of buying the album if I like it (I did this with Play), and I just didn't like it. IMHO, it sounded lik 'Play' warmed over, and didn't do much for me. So I didn't buy it, and I deleted the MP3s.
If you buy the new Counting Crows CD (and you should, because it's quite good) it gives you access to a secret bit of their site with unreleased tracks and whatnot. Makes for an interesting reverse engineering project.
This is coming from someone who hasn't done big, multi-tier DB app development. Stored procedures, views, triggers and the like are crucial to keeping the persistance related logic in it's proper place - the database.
I like MySQL, but without a good object relational mapping tool (like Castora decent sized schema turns into an icky mess of code. On my last project I wasn't allowed to use Castor and ended up writing 3000 lines of JDBC code to support basic CRUD operations on business object on an 11 table schema. I couldn't use EJB's container managed persistance because the relationships were too complex and the schedule was too short.
The book discusses the 802.1x stack & family, but only enough to give a frame of reference. It focuses in mainly on 802.11b, with a chapter on 802.11a and a blub on 802.11g.
Now maybe I can get some good 802.11b support under windows
How would you define "good"? I bought an 802.11b card, and it works under win2k/XP w/the manufacturer's drivers. Heck XP even sees that it's a wireless network device and has special functionality for it. What more are you looking for?
Slashdot Mirror
I know, I screwed up when I posted it. Mea culpa. What's an order of magnitude among friends?
Original video of breakup, in real player format, about the size of a postage stamp. free registration required
still video slideshow of the breakup & astronauts.
It's really been bothering me that this was modded as flamebait
Have you MetaModerated lately? (hint) (hint). That's what it's all about.
A few more photos that aren't slashdotted. [yet]
Talk about the quitessential library. I bet it's the most photographed library in Ireland.
Because hey, if 30-40 people in velvet rainbow butterfly jumpsuits can't run around in the city and advertise a product, then I say the terrorists have already won.
Perhaps this is just a stunt for MS' new product, MSJackass for their new cable channel MSMTV?
This is true, and is a good solution if you need to use both conflicting classes in the same class.
For the person who is learning, it's beneficial to see exactly which package a particular class belongs to.
I agree completely, but in a printed book paper costs money. An entire page of imports in a code sample doesn't help the reader at all and simply wastes trees.
I'm def in the "start importer" camp. The only time you really need to explicitly import individual classes is to resolve a class name conflict (e.g. org.cpfeifer.ListItertor and java.util.ListIterator).
In the past I have used individual imports if I was using an external library and wanted to make the dependancies explicit. But in 1.4 they through in the kitchen sink (60% more classes than 1.3), so it's not as big of deal as it used to be. And I'm lazy.
I think for keeping Taco gainfully employed she should buy us (each, not collectively, it is cold and flu season) a beer at the next /. meetup in Ann Arbor!
Just like many companies that have an official policy to use WebSphere find many of their applications being deployed on Weblogic.
Now that's shelling out the big bucks. I don't know many orgs that could afford lic's for 2 different app servers, no matter how many of each there are deployed.
Either that or they're downloading the demo versions and reinstalling each month. =^)
That means if you have a 4 CPU machine, you need to buy 4 1 year contracts of support that run concurrently. How crazy is that?
I agree with you, but Management(r)(tm) eats this stuff up with a spoon as "cost of doing business."
Either way it doesn't matter to me, I just want a fast java app server that always works and doesn't provide any surprises. If JBoss suits your needs, use it and keep your money in your pocket. If the suits want name brand parts, show them the price tag and hold out your hand.
Or better yet, show them the two price tags (BEA vs. JBoss) and ask them to pick one.
Isn't the purpose of J2EE to avoid vendor lock-in? If that is the case then a generic EJB book coupled with the WebLogic manual should do the trick.
Don't make me laugh, my lips are chapped.
But seriously, yes that is the point. But each vendor has it's own little deployment nits. In my own experience, an app will cross deploy between BEA and JBoss with little/no effort. But cross deploying between BEA and iPlanet or WebSphere is a totally different (and far more frustrating) story.
or actually give you a full fledged app server to begin with (JBoss)
This is true, but BEA is the largest player in the app server market and many large organizations that currently are betting big on J2EE have a hard time basing their business on free software. You need someone on the hook when things go wrong. You need guarantees.
Here's an entry from Moby's journal where he claims that bands with technically savvy audiences don't do well in the charts because their fans rip & burn their CDs. I guess he's a little bitter about '18' not doing as well as 'Play'.
My $.02: I listened to '18' on MP3 with full intention of buying the album if I like it (I did this with Play), and I just didn't like it. IMHO, it sounded lik 'Play' warmed over, and didn't do much for me. So I didn't buy it, and I deleted the MP3s.
Yeah, saw this on the site. So why didn't the extra tracks make the US version, when they did make the international version?
If you buy the new Counting Crows CD (and you should, because it's quite good) it gives you access to a secret bit of their site with unreleased tracks and whatnot. Makes for an interesting reverse engineering project.
A total back of the napkin calculation, the answer is probably yes (based on the size of the ad & the detrimental affects to the wireless connection).
When the story goes live on the website, here's the link
I think ActiveState should file a lawsuit to force MS to ship a PERL runtime with windows under this same argument. Where does it stop? TCL? Python?
If you want it, download and install it.
lock, change, test, commit, unlock
or
change, test, commit, merge?
Are you a locker or a merger?
Now it is in stock, FWIW.
This is coming from someone who hasn't done big, multi-tier DB app development. Stored procedures, views, triggers and the like are crucial to keeping the persistance related logic in it's proper place - the database.
I like MySQL, but without a good object relational mapping tool (like Castora decent sized schema turns into an icky mess of code. On my last project I wasn't allowed to use Castor and ended up writing 3000 lines of JDBC code to support basic CRUD operations on business object on an 11 table schema. I couldn't use EJB's container managed persistance because the relationships were too complex and the schedule was too short.
Once again, bookpool has the cheapest price in town. $27.50
'Sokay.
The book discusses the 802.1x stack & family, but only enough to give a frame of reference. It focuses in mainly on 802.11b, with a chapter on 802.11a and a blub on 802.11g.
It does cover 802.11g and the 802.* stack (but not 801), but only very briefly and from a high level.
Now maybe I can get some good 802.11b support under windows
How would you define "good"? I bought an 802.11b card, and it works under win2k/XP w/the manufacturer's drivers. Heck XP even sees that it's a wireless network device and has special functionality for it. What more are you looking for?