Skip to main content

Glassfish features (esp. Java EE 5/EJB3)

2 replies [Last post]
bmesserer
Offline
Joined: 2004-11-26

I'm not sure, maybe its just me who didn't find it but could anyone involved/responsible for glassfish please post a "feature matrix" or sort of a change log for the published builds?
I'm currently working (testing) Java EE 5 and - at first - couldn't find anything whether glassfish supports the draft-features or to what degree. Only by going through these forums have I found that it at least supports a subset of JavaEE5 or... well, whatever. I won't just use "trial and error" to check whether the (as said, Java EE 5, especially EJB3) features I use in my app are supported or not (you know, when working with a new platform its difficult to distinguish my own faults from glassfish's); believing some postings in this forum, the Java EE 5 implementation is quite complete and implements "the latest draft" (whichever this may be) - maybe I could already test (?).
Please, I (and I guess lots of others) would really like to know which features are implemented/supported, at least a basic changelog on the website (as opposed to "in CVS") would be really nice.

kind regards,

Messi

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
bitmaster
Offline
Joined: 2003-06-16

The https://glassfish.dev.java.net/source/browse/glassfish/appserv-tests/ module in CVS may be an excellent place to start answering your question. Those tests assert some level of conformance (to whatever level, I grant you, but it would be a baseline).

As you can see from the forums and dev mailing list, glassfish is in dire need of documentation. I would encourage you to share your findings (even if your findings are "the appserv-tests are not going far enough") so we all can start to build up knowledge of the product.

-- /v\atthew

bmesserer
Offline
Joined: 2004-11-26

Okay, understand that... but wouldn't it be good if the developers provided some "starting point" on what (features of Java EE 5) they already implemented/are working on? At least _they_ should know what they did/still need to do (?). From this "feature list" it would be ok to proceed as suggested, but finding out what works by unit test, from zero, seems to me like a waste of effort (since we'd need to discover everything from zero that the developers already know). I'm well aware that this approach would result in great coverage by unit-tests but on the other hand this would mean I'd have to commit quite some time to glassfish before I can test on it... sure, I'd like to but sadly I'm paid to write _our_ application, not glassfish. If it already works more or less I may be allowed to invest some time into project glassfish but from zero?
Understand my problem?

kind regards,

Messi