I have after many months of having a stab and failing to get 5.x.x running properly with my seam apps (and booking built from Seam release using Ant) to no avail.
The latest waste of a few hours finally got 5.1.GA to actually RUN!!! and I even get:
2009-08-08 08:56:32,828 DEBUG [org.jboss.classloader.spi.base.BaseClassLoader]
(main) Created BaseClassLoader@1e344422{vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/Sec.ear/}
with policy VFSClassLoaderPolicy@796523ab blah blah blah2009-08-08 08:56:33,250 DEBUG [org.jboss.classloader.spi.base.BaseClassLoader]
(main) Created BaseClassLoader@76f33280{vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/jboss-seam-booking.ear/}
with policy VFSClassLoaderPolicy@5878ae82{name=vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/jboss-seam-booking.ear/
domain=null blah blah blah
Trouble is I don't see any Seam during the server runup and I don't see anything on the url (/booking or /site)
So I have reverted back to 4.2.1.GA again as it simply works.
My worry after reading the other posts is that I will have the server doing auto-redeploys all over the place as it sees a file get changed in the server!!! PLEASE whilst making Seam and 5.1.GA work together make sure this is configurable by file type! I use hot-synch on MyEclipse so MyEclipse handles when a file changes and instantly, automatcailly and seamlessly updates JBoss so I don't have to do aything but have the server just work.... and I dont want something in the server to re-deploy the file AGAIN!
MyEclipse Hot-Synch does not do everything as changing, faces.config, application.xml, messages.xml, xxxx.xml or a java interface causes me to have to kill the server and re-start to see it take effect so having the config
files handled auotmagically by the server when those files are changed would be good.
