The Artima Developer Community
Sponsored Link

Java Buzz Forum
Editorial: Where Java EE goes horribly wrong

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Max Zone

Posts: 9170
Nickname: dzone
Registered: Jun, 2006

dzone.com is a link-sharing community where member participation determines what gets published
Editorial: Where Java EE goes horribly wrong Posted: Apr 7, 2007 9:14 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by Max Zone.
Original Post: Editorial: Where Java EE goes horribly wrong
Feed Title: dzone.com: java
Feed URL: http://feeds.dzone.com/dzone/java
Feed Description: dzone.com: fresh java links for developers
Latest Java Buzz Posts
Latest Java Buzz Posts by Max Zone
Latest Posts From dzone.com: java

Advertisement
Sure, Java EE covers everything but the corner cases... but why, oh why are there so many corner cases?! Java EE rocks, it really does. I'm usually quite happy working with it. But it strikes me -- while it handles nearly everything but the corner cases, it leaves so many corner cases as to make itself less useful than it could or should be. It's the Achilles' heel of Java. For example, look at my recent travails with getting a JMS destination populated for an EIS component. This shouldn't be that big of a deal, really, considering that I've an inbound EIS component that communicates with a resource in JNDI.

Read: Editorial: Where Java EE goes horribly wrong

Topic: Don't Stop Previous Topic   Next Topic Topic: Named Parameters for PreparedStatement

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use