Slashdot Mirror
Java EE 6 Platform Draft Published
synodinos writes "The public draft of the Java EE 6 Platform specification has been published and will remain open for public review and feedback until the 23rd of Feb, 2009. Perhaps the most notable part of this delayed draft is the Web Profile, which is first profile in the history of the Java EE platform. The draft is available for download and contains both the Java EE 6 Spec and the Web Profile Spec. There is a poll running at java.net regarding what the community thinks about the new spec. Although participation is yet rather small the results tend to show that the released draft did not cause any excitement."
There are gorrillas on the Island of Java, part of Indonesia. I know this because I have mated with them. Smooth, luscious, hairy breaks with pizza-sausage nipples which cause KoKo to say, "OO...OOO!" when they are being nibbled.
Gorrillas usually do it doggystyle. That was the position in which KoKo and I first made love. It was problematic because of the muscle tone of her buttocks. She would clench up so tightly that she would push me right out of her if not painfully squeeze my penis.
So then we started doing it missionary. I taught her to lay on her back after receiving a banana as a treat. That way, I could enter her and the angle wouldn't put my manhood in danger. I know when I bring her to orgasm when she screams, "OOOOOOO! OO! OO! OOOOOOOOO!" and tries to pound her chest like King kong but pounds my back instead because i'm on top of her. It's not painful and very enjoyable!
We now share a one-bedroom hut in the forest. I go hunt for food and she takes care of our child(actually, I'm the baby's stepfather, the baby's real daddy abandoned the mother shortly after the birth of the child. We decided to name the child "oo-ooo" and he took his first steps a few days ago. KoKo always smiles when she sees the photograph of our baby taking his first steps. He'll grow up to be a fine Silverback.
that's got to be sacrilege?
Some drink at the fountain of knowledge. Others just gargle.
I'll settle for 5 at this point. My shop is still using 1.4.2; it feels like I should be writing code on stone tablets! I suspect this is the case in any number of Java shops and it just reinforces the idea that Java is going to become the new COBOL. There is so much "legacy" code out there right now, and because of the inconsistencies between versions I can't see it going away any time soon.
God, schmod. I want my monkey man!
From TFA:
There is a poll running at java.net regarding what the community thinks about the new spec...
I like it 12.1%
I think the main spec is missing important JSRs 3%
I think the web profile spec is missing important JSRs 6%
I don't like it for some other reason 6%
I haven't read it, but plan to 9%
I haven't read it, and don't plan to 63.6%
Well, most people never read the specs (that are normally boring and with a lawyer-like style) but most Sun specs appear to being ignored because of bad timing for appearance (usually too late.) The "hot thing" are mostly the open source frameworks, from which Sun ends copying at the end.
The same is happening, albeit radically, in the Mobile editions with Android, despite the Sun auto-acclaimed ubiquity of Jave ME.
I've been leading the development of Java applications for around 8 years. On that journey, I have used fewer and fewer features of it with each succesive project.
Nowadays, it seems that specs are a kind of summary of what has been learned from the frameworks which were created in the trenches by people that actually needed to deliver.
My latest project, which has been in development for around 1 year, delivers as a plain web application, and uses Hibernate, Google Guice, AspectJ and Echo3.
It's wonderful.
Sun don't have the capability, and I'm not sure that anyone has, to provide a full and relevant specification that will allow code to be developed that will run on any application server from any vendor.
Instead, choose your implementations and go back to good old OO basics to design interfaces behind which to hide those implementation choices. You don't need Sun to do that for you.
It might be slow but it has been very successful. Sure many specs never saw the light of day. That is to be expected from every committee.
Like it or not, Java is king on the enterprise server-side. J2EE sucked at the beginning but successive versions addressed many issues required by the enterprise. Persistence (Hibernate, Toplink), transactions and messaging (JMS) and the many available and free implementations. Thank you Sun for sticking with the JCP. Standards are wonderful.
We have an ASP platform built on J2EE 5.0 handling hundreds of millions of transactions a day all on a free stack thanks for the JCP and Linux.
I will duck now since this is /. home of the anti-Java.
Most people are not going to read the standard before it is final: I don't. The only reason to do that is if you intend to give feedback on it (if you do that because you plan to use it in the next project, good luck to you who chooses to use a non existing technology for your project), and that's a fairly limited subset. Most of us will wait for the thing to come out, try to use it, see if it's any good, and then either use it while bitching about how it could have been better of not use it while bitching about on how crappy it is.
If a spec writer doesn't do anything except looking and what goes on in the market and then, after it is clear what approach is the winner, writes a standard (including the people that are winners in the industry), well then they are actually doing their job!!!
Standards are good to freeze what we know that is good. Standards that are in paper or that are written by people who "think hard" are seldom useful.
Ignoring your grammar difficulty, the majority of useful applications out there require a non-embedded database solution...therefore, some configuration is mandatory, for pretty much any application on any platform. To all of you complainers, I work on an application which deploys successfully to Jetty, Tomcat, JBoss 4.2, and Glassfish (as just the ones I've tested). In fact, I test it on all 4 platforms on a regular basis. Sorry, but it works perfectly for me.
Java is a great platform that gives excellent performance and scales well. Outside of initial JNDI datasource configuration (which is technically optional, but very much a best practice), I've had relatively few issues deploying from container to container. I think you folks are exaggerating the effort needed to successfully deploy Java applications.
I'm sorry, learning Java requires a bit of effort. It is a serious language designed to do serious work and optimized for larger, mission-critical projects. It's my first choice of a tool for writing a server side project and the one of the very few I'd choose for a project with more than 3 coders (.NET is the only other serious contender in the arena of large projects). I'm sorry you're having so much difficulty and all I can suggest is that you spend a little more time reading the tutorial and documentation and less time spreading baseless FUD.
I really wonder how many of these critical statements in these comments are being made by experienced, proficient Java developers, and how many are simply being made by a bunch of second rate self-proclaimed coders who are bitter that Java requires a bit greater understanding of OOP and the language to write a useful application than PHP or Ruby.
The only times when I've had to look up the EE APIs these days are when I need a refresher on the guts of a HTTPServletRequest/Response or a SQL Connection. Otherwise, Struts, Spring, Hibernate, derivatives of the previously mentioned items and the like are the de-facto standards.
"People are easily amused by quotes." - Some guy with a cool-sounding name.
I've never seen a serious commercial product shipped independently of an application server.
It depends on definition of 'serious' of course, but I was working for a company producing software for airline operations (briefing/loading, no booking nor avionics/realtime). We had number of clients, including some really big names in Europe. Software was written in J2EE and it was used on 2 different application servers, on 2 different databases (3 combinations in total) - only because companies we were supporting were mostly standarized on Websphere, so there was no need to test it on more. There is NO way any of the big names out there would start supporting new application server just to install our ear, which was probably managing less than 10% of their web activities.
Yes, it was a pain to port it from Websphere to Orion, but it was done by one guy in period of few months and after that I'm quite sure that next port would be already a brief (as most of WAS-specific stuff was cut off/replaced). My proposal to cut it properly and port it to Tomcat, getting rid of EJB was unfortunately ignored...
concerning the web layer you're right on the spot, its too low level and should not be dealt with directly, but jpa, session beans and mdbs are pretty sound and simple and should be dealt with directly, everything else, except for specific business needs, is nih and overhead. and hibernate is in fact a jpa implementation. and with spring, well you have an alternative to application servers, but jee is NOT about just application servers anymore.
On second thought, let's not go to Camelot. It is a silly place.
pretty well sums up the state of the Java language in general
Sigh... Was it not clear I was going for funny? Or was my joke that offensive? :(
And worth exactly what you paid for it.
I work at the MegaMegaCorporation in IT and we were "tasked" to "implement" a "departmental solution". I.E. we were told to write an app for a small bunch o' end users. The app we came up with used Java, Hibernate, Guice (for DI), Spring (for JMS) and Apache. Since we were in the Java world we had a huge range of OSS thingys we could plug into our app that did a whole bunch o' kewel things easily.
+1 for Java - all the widely available thingys
Then, as is usual at the MegaMegaCorporation, an upper management shuffle brought a new MegaMegaCorporateTard into the VP slot overseeing our little hive of worker bees. The new MMCT was demo-ed the 85% complete app we were developing and decided that it was was way too kewel to limit to just one departement; he wanted to make it "enterprise".
We don't have scope creep around here, we have scope explosions.
Anyway, we hit the brakes, wasted a full 2 months on corporate-nonsense design documentation and, in the end, decided to refactor the app into a full stack J2EE app. After I got over the desire to hang myself, I started the work with the rest of the team and found, much to my surprise, that scaling our little departmental app into a MegaMegaClusteredEnterpriseWideApp was, while not easy, at least doable.
+2 for java - it scales - no, really, it does!
My score is Java 3 - everything else I've ever worked with 0.