[jbosstools-dev] Re: Build Status

Ok, found out why: Below is a copy of a compare of two identical projects (except one is called test2w the other testw). Notice the "16 folders and files only on right" section. The second project does not have all files - especially not the components.properties which causes the exception because @jndiPattern@ cannot be resolved. I then tried running Project > Clean and now the publisher is stuck at 75%. Rules-Based Comparison of <C:\jbdevstudiocr1withpatch\jboss-eap\jboss-as\server\default\deploy\test2w.war> to <C:\jbdevstudiocr1withpatch\jboss-eap\jboss-as\server\default\deploy\testw.war> 53 files in 19 folders 41 files match exactly ---------------------- img\cal-next.png img\cal-prev.png img\dtpick.gif layout\display.xhtml layout\edit.xhtml layout\loginout.xhtml layout\menu.xhtml META-INF\MANIFEST.MF stylesheet\theme.css WEB-INF\lib\ajax4jsf-1.1.1.jar WEB-INF\lib\antlr-2.7.6.jar WEB-INF\lib\antlr-3.0ea8.jar WEB-INF\lib\commons-beanutils-1.7.0.jar WEB-INF\lib\commons-collections-3.1.jar WEB-INF\lib\commons-digester-1.6.jar WEB-INF\lib\commons-jci-core-1.0-406301.jar WEB-INF\lib\commons-jci-janino-2.4.3.jar WEB-INF\lib\drools-compiler-3.0.5.jar WEB-INF\lib\drools-core-3.0.5.jar WEB-INF\lib\el-ri.jar WEB-INF\lib\janino-2.4.3.jar WEB-INF\lib\jboss-seam.jar WEB-INF\lib\jboss-seam-debug.jar WEB-INF\lib\jboss-seam-ioc.jar WEB-INF\lib\jboss-seam-mail.jar WEB-INF\lib\jboss-seam-pdf.jar WEB-INF\lib\jboss-seam-remoting.jar WEB-INF\lib\jboss-seam-ui.jar WEB-INF\lib\jbpm-3.1.4.jar WEB-INF\lib\jsf-facelets.jar WEB-INF\lib\oscache-2.3.2.jar WEB-INF\lib\richfaces-3.0.1.jar WEB-INF\lib\stringtemplate-2.3b6.jar WEB-INF\faces-config.xml WEB-INF\pages.xml WEB-INF\web.xml error.xhtml home.xhtml index.html login.page.xml login.xhtml 3 files don't match ------------------- layout\template.xhtml WEB-INF\components.xml WEB-INF\jboss-web.xml 3 folders and files only on left -------------------------------- WEB-INF\classes\org\domain\test2w\ WEB-INF\classes\org\domain\test2w\session\ WEB-INF\classes\org\domain\test2w\session\Authenticator.java 16 folders and files only on right ---------------------------------- WEB-INF\classes\META-INF\ WEB-INF\classes\META-INF\persistence.xml WEB-INF\classes\org\domain\testw\ WEB-INF\classes\org\domain\testw\session\ WEB-INF\classes\org\domain\testw\session\Authenticator.java WEB-INF\classes\components.properties WEB-INF\classes\import.sql WEB-INF\classes\messages_en.properties WEB-INF\classes\seam.properties WEB-INF\classes\security.drl WEB-INF\dev\ WEB-INF\dev\org\ WEB-INF\dev\org\domain\ WEB-INF\dev\org\domain\testw\ WEB-INF\dev\org\domain\testw\session\ WEB-INF\dev\org\domain\testw\session\Authenticator.class > apparently JDK6 makes the actual published content broken since even with JDK5 it does not work. > > If I do the actual project creation and deploy with JDK5 then it works - except i'm seeing that the -ds.xml is deployed, but the actual war is not > before I actually run it. > > ...and now I redid it with JDK5 and I have the same problem - this time with a war. > > The first project runs fine, the second does not. > > Something is definitly broken! > > /max > >> wait...might be caused by me running jdk 6 ... >> >> /max >> >>> 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 >>>> >>>> >>> >>> >>> >>> >> >> >> >> > > > >