I finally got this version down and now the jboss-seam.jar file seem to be deployed but
the seam application does not start.
I get:
15:02:53,465 ERROR [ContainerBase] Exception sending context initialized event to listener
instance of class org.jboss.seam.servlet.SeamListener
java.lang.RuntimeException: error while reading /WEB-INF/components.xml
at
org.jboss.seam.init.Initialization.initComponentsFromXmlDocument(Initialization.java:137)
at org.jboss.seam.init.Initialization.create(Initialization.java:87)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3854)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4352)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:732)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
When you tested that it deployed, did you guys also test that the app actually were able
to run ?
/max
Ok... so...
A full JBDS build was created. It worked about 50% of the time. I know
this sounds horrible, but, it did ;) The times it did *not* work was
because of a ClassCastException in eclipse in the very same class that's
been our problem the entire time.
I've come to the conclusion that their entire JEEDeployableFactory is
crap, a conclusion validated by the fact that theyv'e changed it
entirely in 3.0.
Either way, I added in further exception checks. I am confident that
this is the only thing standing in our way. A new build is being started
right now. It should be finished in an hour or three... and when it is,
it would be excellent if it could be tested extensively!
Good luck, and I'll be back online in 6 hours or so!
- Rob Stryker