tag:blogger.com,1999:blog-7836204352369514180.post2548639517678926727..comments2022-03-25T05:11:20.110+01:00Comments on Around the World in Java: Java EE 6 Server Comparison: JBossHarald Wellmannhttp://www.blogger.com/profile/08039976160321882828noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-7836204352369514180.post-6699896130920993682011-07-13T06:55:02.809+02:002011-07-13T06:55:02.809+02:00I share your pain.
It's reassuring if not nic...I share your pain.<br /><br />It's reassuring if not nice to see that I'm not alone in my largely miserable and painful experience of developing on Java EE 6 with CDI using Glassfish *or* JBoss.<br /><br />I've found bugs in Glassfish that I simply cannot believe existed. "Does anybody even use this?" kind of bugs. Like:<br /><br /><a href="http://java.net/jira/browse/GLASSFISH-16917" rel="nofollow">GLASSFISH-16917: a giant classloader leak in any app that uses JSF, causing redeploy of medium to large apps to fail in one or two cycles</a><br /><br /><a href="http://java.net/jira/browse/GLASSFISH-13040" rel="nofollow">GLASSFISH-13040: calling methods of a bean that were inherited from a superclass not working</a><br /><br /><a href="http://java.net/jira/browse/GLASSFISH-16222" rel="nofollow">GLASSFISH-1622: asadmin can't set more than one context parameter</a><br /><br />and today <a href="http://java.net/jira/browse/GLASSFISH-17024" rel="nofollow">GLASSFISH-17024: resource reference indirection via web.xml and glassfish-web.xml non-functional in trivial test case</a>.<br /><br />Then there are things like aren't even considered bugs, like the inability to @Inject into a JPA 2.0 EntityListener (no planned fix in JPA 2.1 unless people start contacting the working group and stressing its importance!). Then there's the need to use a servlet filter and CDI extension like Seam 3 Faces just to get injection into @FacesConverter etc working. These are "how did we actually release the spec with these holes in it" severity issues. What's the point of CDI and dependency injection if it only works in some places some of the time? <br /><br />CDI was bashed into Java EE 6 too late in the process and it really shows in the lack of integration with the other specs. Even without all the Weld bugs.<br /><br />I increasingly wonder if anybody actually uses most of the features of these servers. Certainly nobody could've used CDI in production if they wanted to until Weld 1.1.1 and Glassfish 3.1. Even now, I'm having to update to Glassfish 3.1.1 prereleases to work around *more* CDI bugs.<br /><br />As for JBoss: JBoss AS 6.0.0 has been out for months, and passed release testing. Despite that, <a href="https://issues.jboss.org/browse/JBAS-8776" rel="nofollow">it still rejects its own xml schema descriptors for jboss-web.xml</a>. <i>You have to patch it just to use the examples from the documentation without errors!</i>. In JBoss 7, which has just been released, I can't get it to map a datasource name referenced in web.xml via jboss-web.xml .<br /><br />I guess this is the long way of saying: I share your pain. Java EE is rushing ahead with features and severely neglecting testing, stability, and documentation, leaving things an ugly, buggy mess for those of us who're trying to do real-world work with them.<br /><br />It also seems like such a huge waste of effort to have three major servers being developed, each of which is incomplete and buggy, instead of consolidating effort.Craig Ringerhttps://www.blogger.com/profile/02343803844223399065noreply@blogger.comtag:blogger.com,1999:blog-7836204352369514180.post-9677315076735830312011-06-10T12:34:49.736+02:002011-06-10T12:34:49.736+02:00Great servers comparison! Thanks for the effort.
...Great servers comparison! Thanks for the effort.<br /><br />JBoss is somehow my favourite JEE server. I'm currently working with version 6 and yes, I know the pain you described, all the trouble one has to go through.<br /><br />What annoys me most is that even after you get all the configuration right, it still runs out of memory if you redeploy a sufficient amount of times (which is around 5 in my case; I didn't tweak heap settings to be honest).<br /><br />JBoss 5 had its own problems and was in a way abandoned, most people I know use either 4 or 6. Similar thing may happen to version 6 when 7 is mature.<br /><br />JBoss still remains my favourite - probably because I know it best, but I may try one of the other two servers.MichaĆ Huniewiczhttps://www.blogger.com/profile/03904658492365257143noreply@blogger.comtag:blogger.com,1999:blog-7836204352369514180.post-26236693880936432542011-06-09T23:39:39.363+02:002011-06-09T23:39:39.363+02:00Ah, if you don't have any descriptors in your ...Ah, if you don't have any descriptors in your project JBoss won't notice it. This sucks agreed. <br /><br />Solution: use as7 or use clean/full publish or deployed as compressed archive.Maxhttps://www.blogger.com/profile/12292281395523675930noreply@blogger.comtag:blogger.com,1999:blog-7836204352369514180.post-47522903439821746742011-06-09T23:36:04.064+02:002011-06-09T23:36:04.064+02:00I'm interested in seeing your app to know why ...I'm interested in seeing your app to know why it wasn't redeploying. <br /><br />But in any case, try out as7 instead of as6 - your experience will be very different.Maxhttps://www.blogger.com/profile/12292281395523675930noreply@blogger.com