It’s in JBoss’ own interest to implement the J2EE standard
Now that JBoss 4 is about to be released, discussions about JBoss’ j2EE certification are also popping up again (here, here).
For me, it doesn’t really matter whether JBoss is certified or not. When I design and write Java applications I will follow the J2EE specifications. Hopefully whatever I do will work in JBoss, and if it doesn’t I’ll complain, file a bug report and create a workaround, as I do everytime I find a problem with some software I have to use. But I’ll stick to the standards, as this will allow me to write portable applications.
As it stands now, JBoss complies enough with the J2EE standard that it can be used in projects. The JBoss project would only hurt itself by not prividing all the standards, as developers would look elsewhere for a better application server.
June 2nd, 2003 at 2:10 pm
I disagree. 1/2 year ago I found a bug and it’s still there… More with JBoss 3.2.1 they have added one more… The good is: My code is portable, so from time to time I’m checking if it works on JBoss… no… no… no…
P.S. I like JBoss, but what should I do with RMI/IIOP which is brocken?