5 Replies Latest reply on Feb 2, 2007 11:17 AM by denis.diggin

Classpath question with Seam & Tomahawk

georgesberscheid Jan 24, 2007 11:36 AM

Hi,

looking at the examples that come with Seam and at what seam-gen does, it seems to be common practice to put all EJB3's and Seam components into a JAR file, all the JSF and view stuff into a WAR file and package both in an EAR.

The issues example uses Tomahawk which goes into .war/WEB-INF/lib. What do I do if one of my Seam components, a stateless session bean that's in the JAR file needs to hold the TreeModel for a Tomahawk Tree2 component?

Do I need to move the Tomahawk and Facelets libs to the EAR root (and add it to application.xml or jboss-app.xml as java modules) or do I rather put them into server/default/deploy/jbossweb-tomcat55.sar/jsf-libs?

Should I not use any EJB3 components with references to JSF classes and make them normal Seam JAVA_BEAN components that go into .war/WEB-INF/classes?

Any help on this would be greatly appreciated.

Thanks,
Georges

1. Re: Classpath question with Seam & Tomahawk

hstang Jan 24, 2007 12:09 PM (in response to georgesberscheid)

"georgesberscheid" wrote:

Do I need to move the Tomahawk and Facelets libs to the EAR root (and add it to application.xml or jboss-app.xml as java modules)

I would try that. Not sure if you need to move facelets out though.
Actions
2. Re: Classpath question with Seam & Tomahawk

georgesberscheid Jan 24, 2007 1:41 PM (in response to georgesberscheid)
Well, if I leave the facelets classes where they are, I get a ClassNotFoundException when I try to render a page (deployment works ok). However, declaring the facelets JAR as java module as well, gives me the following exception:

org.apache.myfaces.trinidadinternal.facelets.TrinidadComponentHandler must be an instance of com.sun.facelets.tag.TagHandler com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.createClass(TagLibraryConfig.java:281) com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.endElement(TagLibraryConfig.java:206)

However, TrinidadComponentHandler does extend TagHandler, so there must be another classpath problem somewhere.
I don't think I understand quite well how that works...
Actions
3. Re: Classpath question with Seam & Tomahawk

georgesberscheid Jan 24, 2007 1:49 PM (in response to georgesberscheid)

I should probably add that this is using Trinidad instead of Tomahawk, but the concept is the same...
Actions
4. Re: Classpath question with Seam & Tomahawk

georgesberscheid Jan 24, 2007 2:37 PM (in response to georgesberscheid)

Argh, the EAR file that I had deployed still had the Facelets libs in .war/WEB-INF/lib. So it was in the classpath twice... that's never good.
Actions
5. Re: Classpath question with Seam & Tomahawk

denis.diggin Feb 2, 2007 11:17 AM (in response to georgesberscheid)

facelets in web-inf/lib
trinidad impl jar in web-inf/lib
trinidad api jar in the ear root

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010099#4010099
Actions

Go to original post