Components.xml not isolated between wars in ear in Seam 2.1.0

[susnet.susanne.susnet.se]

When upgrading to Seam 2.1.0.SP1 from 2.0.2.GA Seam now seems to mix components.xml files between different wars deployed in an ear.

I have an ear, with multiple wars. If I put the code

<security:identity authenticate-method"=#{authenticator.authenticate}" />

in one of the components.xml that has login functionality, and the other components.xml in the other war has no such field in its components.xml I get the following error message:

ERROR [SeamLoginModule] No authentication method defined - please define authenticate-method for <security:identity/> in components.xml

If I then put the above security:identity code in this war's components.xml too (although this war does not have login functionality) then the other war's login works.

If I have yet another war with login functionality but another authenticate bean and method name. Then the first war module runs the other's authenticate method which then of course fails.

This worked perfectly in Seam 2.0.2. GA and I have  not changed anything else.

Is this a bug or do I have to make some configurations? Why can not Seam keep the components.xml in each war isolated?

[susnet.susanne.susnet.se]

It seems like a serious bug?
Anyone else having a deployed ear with multiple wars where one or more of the wars having login functionality, but different authenticate methods (or one war with login and another without)?
Also, maybe it could be more than seam security that does get mixed up between war's components.xml?

[antoine.antoine.abside.com]

I have exactly the same issue. If it's not a bug, please give us guidelines to have multiple wars in ear with Seam 2.1.X

[ctomc]

Hi,

how do you have your app deployed? Do you have classloading isolation enabled?

you can enable that in ear-deployer or in jboss-app.xml that is in your application.

you should have something like this in your jboss-app.xml

<loader-repository>
          seam.jboss.org:loader=BIN
   </loader-repository>

can you post your jboss-app.xml?

[susnet.susanne.susnet.se]

Yes I have classloading isolation enabled, looking like this:

<?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE jboss-app
    PUBLIC "-//JBoss//DTD J2EE Application 4.2//EN"
    "http://www.jboss.org/j2ee/dtd/jboss-app_4_2.dtd">
<jboss-app>  
     <loader-repository>  
          recepten:archive=recepten-ear.ear  
          <loader-repository-config>  
               java2ParentDelegation=false  
          </loader-repository-config>  
     </loader-repository>     
</jboss-app>

The Bug report is here: https://jira.jboss.org/jira/browse/JBSEAM-3744

[rafaelrato]

Does anybody got a workaround for this issue?

I have it running Seam 2.1.1.GA on JBoss AS 5.0.

[susnet.susanne.susnet.se]

No, there is a JIRA bug: https://jira.jboss.org/jira/browse/JBSEAM-3744

[rafaelrato]

Thanks for your response, Susanne.

I've checked your opened issue at Seam Jira before. So I was wondering if people who was facing the same problem than me found a workaround, changing the EAR structure or something like that.

Did you applied any alternative solution for the problem?

[susnet.susanne.susnet.se]

Well I have not really found any workaround, not any good one at least. I now use the same authentication method for all wars so I have changed that method so it works for both wars. I have put the same configuration for authentication in each compononets.xml for each war.

[fcorneli]

I'm fighting exactly the some problems. Anyone found a work-around here? It really seems that JBoss Seam's classloading is inherently sick.

[swd847]

I have attached a patch that should fix the issue to JBSEAM-2523

[lasansue.jeremy.girard.satives.fr]

Same problem for me

http://seamframework.org/Community/Seam212CR1ExtendingIdentityProblem

I will try this fix soon

Regards

[rend]

I'm experiencing this issue, but also:

Seam-3849
ClassLoader cannot find xhtml files when scanning page.xml files in an EAR with Multiple WARs

Perhaps the cause of that bug is similar?