please document library versions

[tynor]

I am running into a bug which from googling may be fixed in a newer hibernate or ejb3 release, but I can't be sure -- I can't tell from the jboss-seam-1.2.1-GA.zip file just what versions of various jars are bundled.

The Seam 2.0-BETA distribution does not appear to be any better documented. Before te next release, please update the lib/readme.txt to include details of each jar file's version and/or change their filenames (e.g., from hibernate-all.jar to hibernate-all.x.y.z.jar) so we can know what versions we're using.

If I'm just blind and not looking in the right place, my apologies, and please just point me to the docs.

[tynor]

Created JIRA task: http://jira.jboss.com/jira/browse/JBSEAM-1773

[tynor]

In the mean time, can someone tell me what versions of the following jars are bundled in Seam 1.2.1-GA and 2.0.0-BETA?

hibernate-all.jar
jboss-ejb3-all.jar
jsf-facelets.jar
and the javassist bundled into thirdparty-all.jar

none of those jar's MANIFEST.MF's specify versions.

Thanks!

I am running into a bug which from googling may be fixed in a newer hibernate or ejb3 release, but I can't be sure -- I can't tell from the jboss-seam-1.2.1-GA.zip file just what versions of various jars are bundled.

The Seam 2.0-BETA distribution does not appear to be any better documented. Before te next release, please update the lib/readme.txt to include details of each jar file's version and/or change their filenames (e.g., from hibernate-all.jar to hibernate-all.x.y.z.jar) so we can know what versions we're using.

If I'm just blind and not looking in the right place, my apologies, and please just point me to the docs.

[pmuir]

All of them are custom versions IIRC.

[asavitsky]

All of them are custom versions IIRC.

Are there any particular reasons to use custom versions?

Where's the source code for these versions?

[pmuir]

The above (except facelets) are out of JBoss Embedded (or Embeddable EJB3 for pre Seam2), which is in JBoss CVS/SVN. The facelets in 1.2.1.GA was, IIRC a CVS snapshot (but it could have been 1.1.12, not sure), the facelets in Seam2 is facelets 1.1.13.

Why? Well facelets is obvious (we needed fixes which weren't in a released version). And currently Seam depends on JBoss Embedded at build time (but not at runtime, you do need thirdparty-all for deploying to non JBoss AS app servers if they don't have all the deps needed, normally javassist). I am working on improving dep management currently, and the dependency on JBoss Embedded (apart from it's api) will go away.

[tynor]

As part of those dependency improvements, at the very least please be sure to document what versions of third party libraries are used, and if custom ones are required contain multiple "sub-jars", how to reconstruct them.

My original post on this thread was prompted by a bug related to EJB3 @ManyToOne, Hibernate LAZY loading and/or javassist. Google showed similar complaints and some recommendations to update to newer versions or hibernate or javassist. But since I have no idea what versions I'm currently using or in the case of customized ones, how to patch a standard version to create the customized packaging, I'm flying in the dark.

I've since "worked around" my bug by changing some LAZY joins to EAGER, but I would be much more comfortable to have been able to fix it by replacing the broken hibernate or javassist or ejb3 jars with properly fixed versions... Please don't assume that Seam users will never need to update dependency libraries to get fixes or new functionality independent of a new Seam release.

[pmuir]

Where are you deploying to?

[asavitsky]

Why? Well facelets is obvious (we needed fixes which weren't in a released version). And currently Seam depends on JBoss Embedded at build time (but not at runtime, you do need thirdparty-all for deploying to non JBoss AS app servers if they don't have all the deps needed, normally javassist). I am working on improving dep management currently, and the dependency on JBoss Embedded (apart from it's api) will go away.

Well, actually, it was the custom version of Hibernate, not Facelets, that puzzled me. After all, with Hibernate being owned by pretty much the same team as Seam itself (well, Gavin is there for sure), any needed custom changes could have been as easily incorporated right into a Hibernate release, now couldn't have they?

Now, if I don't use JBoss Embedded (I deploy on Tomcat without EJB3 support), do I still need to use the hibernate-all.jar, or can I use the latest GA versions of Hibernate, Annotations, EM and such?

[pmuir]

Well, actually, it was the custom version of Hibernate, not Facelets, that puzzled me. After all, with Hibernate being owned by pretty much the same team as Seam itself (well, Gavin is there for sure), any needed custom changes could have been as easily incorporated right into a Hibernate release, now couldn't have they?

I think its a released version of hibernate repackaged. Not sure which one, sorry.

Now, if I don't use JBoss Embedded (I deploy on Tomcat without EJB3 support), do I still need to use the hibernate-all.jar, or can I use the latest GA versions of Hibernate, Annotations, EM and such?

No, there is no need to deploy hibernate-all.jar ever with your Seam app (of course, if you use JBoss Embedded then you need it, but thats not deploying with seam). You can swap in the latest versions of Hibernate stuff. You could probably do this on JBoss AS as well.