Directory structure change in JBoss AS affecting seam

[saeediqbal1]

Hi,

I would like to point out that the directory structure of JBoss AS referenced in this small tutorial http://www.jboss.com/index.html?module=bb&op=viewtopic&t=94738 is this "server/default/deploy/tomcat/jbossweb-tomcat55.sar/jsf-libs "

in the JBoss AS5.xbeta i downloaded just now, deploy/ folder does not contain any folder called tomcat/ . Thereby we'r facing a few errors while doing a fresh install of JBoss AS with fresh Seam and a sample example application like registration deployed.

The error is :
2007-02-02 16:29:24,866 DEBUG [org.jboss.web.WebPermissionMapping] Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverriden=false,qualifiers=[]]}
2007-02-02 16:29:24,866 INFO [org.jboss.web.tomcat.tc6.deployers.TomcatDeployment] deploy, ctxPath=/seam-registration, warUrl=.../tmp/deploy/jboss-seam-registration60195-exp.war/
2007-02-02 16:29:24,882 DEBUG [org.jboss.web.tomcat.tc6.deployers.TomcatDeployment] Using session cookies default setting
2007-02-02 16:29:24,897 DEBUG [org.jboss.web.tomcat.tc6.WebAppLoader] injectionContainer enabled and processing beginning with Tomcat WebAppLoader
2007-02-02 16:29:24,960 ERROR [org.apache.tomcat.util.modeler.BaseModelMBean] Exception invoking method addChild
java.lang.RuntimeException: could not find listener class in classpath
at org.jboss.web.tomcat.tc6.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:339)


.
.
.
.
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException: org.apache.myfaces.webapp.StartupServletContextListener
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1355)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1201)
at org.jboss.web.tomcat.tc6.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:333)



I would appreciate any guidance in this matter so that I can learn the exciting stuff Seam has to offer and contribute to it if i can :)

[norman.richards]

You are correct - JBoss 5 is not the same as JBoss 4. If you are just wanting to do Seam and have no specific reason to be on JBoss 5, I'd recommend staying on JBoss 4 so that you won't run into any differences.

JBoss 5 uses Tomcat 6 and the JSF RI by default. It does not come with myfaces. It is very clear that your app is trying to use the myfaces StartupServletContextListener, which doesn't exist.

I believe JBoss 5 comes with a version of the Seam booking application that you can use as a guide if you really feel the need to be on JBoss 5 now.

[saeediqbal1]

Hi Norman

Thanks for the reply. Yes i was just playing around with seam examples. Your reply was informative.

From what I understand, since 5 onwards JBoss AS would use JSF RI and embedded tomcat6, I think i'll stick with it. Why not learn the stuff now when we'll have to learn it at the time of moving from 4->5. I work with EAServer mostly at work but I'm getting started with Seam (and maybe trying out JBoss AS) personally so the environment is new to me.

Thanks and I'll dig deeper into understanding how as5 works :)

-si

[norman.richards]

That's not a problem, but if you are new to JBoss I really think you'll find JBoss 4 a friendlier platform. I would say that the JBoss 5 beta is best left for experienced JBoss users. But, if you are up for the challenge, then I don't see any problem. Post back if you run into anything peculiar.

[saeediqbal1]

Sure I will inform you of anything i run into that i'm not sure of. Maybe using AS5 would help me find some kinks that could be ironed out for GA release.

Thanks much!