I tried with 2.1.1.GA -> same problem
no idea ?
I have some more information about my problem.
When debugging my apps i can see in the following seam code
this behaviour :
For the webapp 1 : expected component is webapp1.ExtendedIdentityComponent and result componennt is webapp2.ExtendedIdentityComponent so it fail
For the webapp 2 : expected component is webapp2.ExtendedIdentityComponent and result componennt is webapp2.ExtendedIdentityComponent so it's ok
It seams that the seam component context is shared between all my ear's webapps so i can't define a custom identity component for each webapp.
The lastest added component wins so in my case extended identity component added by webapp2 in the only one for both webapps.
This was working with seam 2.0.2.SP1.
I hope those additional information could help me to find a solution.
When i remove the webapp2.ExtendedIdentityComponent it still does not work
In the org.jboss.seam.Component.getInstance(Component.java:2000) method
component beanClass is webapp1.ExtendedIdentityComponent and result class is org.jboss.seam.security.Identity
ExtendedIdentityComponent extends org.jboss.seam.security.Identity and isInstance fail .....
To my mind, this is a seam issue .
Does someone can confirm or infirm that ?
It sounds like a classpath issue to me, but that's just a guess. Maybe try deploying only 1 war at a time and see what happens.
Well done ....
With one War at a time it works fine.
So how could i report this seam issue, it used to works fine with seam 2.0.x
I just came across this post which sounds like the same exact issue. Sounds like a bug report has already been filed.