seam-persistence jars in ear not visible to SMPC producer inside a war

[yangju.richard.yang.pearson.com]

We used to have only war deployment and it worked OK. We have a producer in a jar which is put inside the war (a jar of web-inf/lib):
@SeamManaged
@Produces
@PersistenceUnit
@ConversationScoped
EntityManagerFactory producerField;

In the beans.xml of the jar we have this turned on
<interceptors>          <class>org.jboss.seam.persistence.transaction.TransactionInterceptor</class>
</interceptors>

Now, we are trying to deploy ear instead of war, because of jboss weld issue which does not allow multiple wars to be deployed in the same jvm (conflicting jndi names for weld managed beans).
Inside the ear's lib directory:
seam-persistence-impl-3.0.0.Beta4.jar
seam-persistence-api-3.0.0.Beta4.jar
and some dependencies jar such as solder.jar.
The war is inside the ear and the war does not have these jars.

However, at deployment time, jboss complains that it could not find org.jboss.seam.persistence.transaction.TransactionInterceptor class.

I thought the jars inside the ear are visible to the war. I have the correct application.xml.

Is this a bug? Or do I have to put seam persistence jars in both ear and war?

Thanks.

[benkirby]

I also have this issue, using JBoss AS6 and Seam 3.0.0.final, only instead of WARs in my EARs, I have JARs.

They have the same specification in their beans.xml though, and I'm getting the same issue.

Did you determine the cause or find a workaround?

Thanks,
Ben

[yangju.richard.yang.pearson.com]

We found that the seam interceptor can only be defined once (i.e. not in multiple deployment untis like jars). So we only have the seam transaction interceptor as well as our own interceptors in one beans.xml only, and that beans.xml is included in One jar inside ear's lib. That seems solve the

This might be because of the fact that jboss 5 and 6 uses different classloaders for ear and war?

http://community.jboss.org/wiki/UseJBossWebClassLoaderInJBoss5problem.

But since you don't have war, I don't know the cause for your problem.

Now we are moving to jboss 7 and this problem might be gone or might be worse. We will see.