Seam 2.0 migration - jboss-seam-ui.jar problem

[stefans]

hi guys,

i'm fairly new to the world of JBoss Seam so bear with me, if I am missing something obvious here.

I'm currently in the process of migration an existing project including some custom JSF components with dependencies to jboss-seam-ui.jar which are packaged into their own jar.

In addition i am creating parts of the userinterfaces programmatically, so i have direct dependencies on the JSF RI, Seam and custom components from my Action beans

My problem is, how to package the jars. I discovered, that in the Seam 1.2.0.GA version of the project, the seam-ui jar was deployed twice - once in the war file and a second time in the ear file. This somehow worked in the old setup, but gives me quite a headache now, as the new version of the seam RendererBase class checks if the class given in the renderer and the actual compont match - which they do not - as they are loaded by different classloaders :/

i cannot simply remove one of the two versions of the jar, as removing either one causes deployment errors (ClassNotFound ... )

Is there any place where I can put the jboss-seam-ui.jar so it's classes are only loaded by one classloader, or is there any other way to get around my problem?

thanks in advance,
stefan

[nickarls]

Tried running seam-gen and dropping your component jar file into the war?

[stefans]

Hi,
I based the whole migrated project on a seam-gen generated project. Dropping my component jar file into the war - alongside the richfaces, facelets and jboss-seam* jars also resulsts in a NoClassDefFoundError as I also have direct dependencies between my action beans and my custom components - as mentioned above.

[stefans]

hi

some updates - i tried the following without any success:

a) put jboss-seam-ui.jar and my custom component jar into the JBoss jsf-lib folder alongside the Sun JSF RI

b) put them into the root ear directory alongside the jboss-seam.jar and register them as modules in the application.xml

unfortunately neither of the two approaches worked. I am getting really desperate here. any suggestions??

thx
Stefan

[keithnaas]

Simple approach that works for us: 

Put all the jars in the ear, and add Classpath entries for all ear jars in the MANIFEST.MF of the war. 

[stefans]

Thanks a lot. worked like a charm!!

[gzoller.greg.zoller.aviall.com]

I think I'm having similar issues.  Can some please post an example?  I added a MANIFEST.MF and attempted to set classpath entries there but didn't do something right.  All kinds of fireworks when JBoss starts up.

In my ear file I have foo.jar, foo.war, lib, and META-INF.
I moved all 3 richfaces-xxx.jar files into my ear's lib directory.
Then I went into foo.war and created a META-INF directory and put a MANIFEST.MF file in there containing:

Class-Path: ../../lib/richfaces-impl.jar ../../lib/richfaces-ui.jar ../../lib/richfaces-api.jar

It wasn't happy.

Any ideas?
Greg

[blabno]

Path must be relative to ear root.

Class-Path: lib/

or

Class-Path: lib/richfaces-impl.jar lib/richfaces-ui.jar lib/richfaces-api.jar

[spider05]

This solution does not work for me. Who would it work?