Multiple Wars in EAR in seam 2.10SP1 doesn't work

[antoine.antoine.abside.com]

I know that multiple War in EAR is a very asked question but with migration to 2.10 it's very urgent to get guidelines on the topic.

I've got 2 application with multiple wars in EAR they worked rather fine in Seam 2.0X and JBoss 4.2.2 (with phase listener warning and some components sharing between wars).

I tried yesterday to update one of these application to seam 2.10sp1 and it was a total mess. The components.xml of the first war declared in application.xml  is used for all wars (their components.xml file) are ignored.

I guess it is linked with class loading isolation in JBoss but I'm a bit confused on the subject. Could someone give me leads to investigate this issue : It doesn't have to be long but something to start with.

Thanks a lot

[antoine.antoine.abside.com]

Am I the only one to need to run two or more wars in the same EAR ? Or is it impossible with Seam 2.1 ?

[erikjfreed]

For what it is worth, I also need to deploy multiple WAR instances within a single EAR instance. In scanning the web I can't actually see anything definitive about what actually is supposed to work or not work and how it would work if it could work. Anyone found anything that addresses this pretty non extraordinary use case?

[e-mail]

[jbalunas.jbalunas.jboss.org]

There is a jira specifically for this issue, and is scheduled for the upcoming Seam 2.1.1.CR2 release. 

Your best bet is to vote on the issue here JBSEAM-3119. That will help if bubble to the top :-)

-Jay

[karl.traunmueller]

Same issue here: two Seam WARs in one EAR, components.xml is picked up from wrong application, #{identity.login} tries to call warong authenticator component

Seam 2.1.0.SP1, JBoss EAP 4.3.0.GA CP01

regards,
Karl

[austin]

I encountered a similar problem. If there are page-navigation files (i.e. login.page.xml) with the same name in each war, the latter-loaded war will follow the earlier-loaded war's navigation rule. This problem was not existed in Seam 2.0.2 but happened in 2.1.0.GA with Jboss 4.2.3.GA.

Regards,
Austin

[aozoren]

Having multiple wars in one ear problem has been around for at least a year if not more yet it is ignored for some reason. Why, I don't know.. There might be a fundamental flaw in Seam or JBoss that does not allow this to happen and instead of acknowledging the failure to solve this issue they merrily keep on integrate yet another ui framework as if it is more important than multiple wars issue.. I don't know the numbers of people desperately wanting wicket integration compared to number of people who hit the multiple wars issue so it might make sense to keep wicket people happy if they have the numbers.

[cpopetz]

The they in they merrily keep on integrate (sic) yet another ui framework is just me at this point, and I'm a volunteer (not a Jboss employee), donating my time to the wicket integration because I think it's worthwhile.

Which brings up the point that if you feel like the multiple WAR problem is something worth fixing, you do have the option of downloading the source and getting to work.

[aozoren]

It would be nice if we could give back something besides market share but unfortunately we lack the resources to delve into Seam and possibly JBoss code base.