Seam 3.1.0.Beta3 released

[shane.bryzak]

We've released Seam 3.1.0.Beta3, you can find the announcement and release details here:

http://in.relation.to/Bloggers/JBossSeam310Beta3Released

Enjoy!

[tikus]

Hi

anything changed in seam-security jpaIdentityStoreConfiguration configuration? I cant get it
to work after upgrading to 3.1.0.Beta3? It was working with 3.0.0.Final ..

(MSC service thread 1-1) Preventing installation of default bean: org.jboss.seam.security.management.picketlink.JpaIdentityStoreConfiguration

How can i debug whats preventing this bean from being installed?

Thanks
Tom

[shane.bryzak]

That is very weird.. I can't think of what might be preventing it from being installed.  Are you able to replicate this with a minimal test case?

[tikus]

I just wonder if it cant have anything to do with old references to seam-solder. I filled bug
SEAMFACES-211 

[org.jboss.solder.core.CoreExtension] (MSC service thread 1-3) Preventing class org.jboss.seam.faces.exception.CatchExceptionHandler from being installed as required class org.jboss.seam.exception.control.extension.CatchExtension could not be found
15:08:38,710 INFO  [org.jboss.solder.core.CoreExtension] (MSC service thread 1-3) Preventing class org.jboss.seam.faces.security.SecurityPhaseListener from being installed as required class org.jboss.seam.security.extension.SecurityExtension could not be found

after fixing these references in seam-faces they are gone but jpaidentitystoreconfiguration is still blocked.

I thought i could try to deploy idm-console example from 3.1.0.Beta3, but its not configured for jpaidentitystore yet as the one from 3.0.0.Final

[shane.bryzak]

Those issues have already been fixed, but thanks for filing it.  I don't think they have anything to do with JpaIdentityStoreConfiguration.  What do you mean about the idm-console example not being configured?  The latest release deploys for me fine.

[tikus]

You are right it deploys fine. But its not configured in seam-beans.xml anymore. Its configured using annotations on security model entities right?

Preventing installation of jpaidentitystoreconfiguration is maybe caused by solder configuring it from seam-beans.xml where s:replaces prevents default bean to be installed.
Is that correct?

So there is definitely error somewhere on my side.

After updating to model entities from idm-console examples, deleting configuration from seam-beans.xml Preventing installation of jpaidentitystoreconfiguration is gone but this error occurs after authentication:

org.picketlink.idm.common.exception.IdentityException: Error creating IdentitySession - no PicketLink IdentityStore repositories have been configured.

[tikus]

I found the cause. My entities was packaged in separate jar file included in war. After moving all entities to war, its working again ....

[lightguard]

This sounds like a bug we should fix, would you please create a JIRA issue under Seam Security?

[shane.bryzak]

I'm not convinced it's a bug.  Did the jar file that contained the entity beans have a beans.xml file?

[tikus]

Bingo! It starts to make sense. Since the jpaidentitystore is configured using annotations cdi must actually process it right? Therefore beans.xml must be present in persistence archive jar.

I didnt have it, because configuration was in xml and it didnt work after moving to 3.1.0.Beta3.

Should xml configuration still work or annotations will be the only one option? (that i prefer)

Thanks for hint

[shane.bryzak]

Tomáš Tikovský wrote on Oct 09, 2011 12:37:


Bingo! It starts to make sense. Since the jpaidentitystore is configured using annotations cdi must actually process it right? Therefore beans.xml must be present in persistence archive jar.

Correct, the beans.xml is required because the entity beans need to be scanned by the security extension for the identity management annotations.

I didnt have it, because configuration was in xml and it didnt work after moving to 3.1.0.Beta3.

Should xml configuration still work or annotations will be the only one option? (that i prefer)

Thanks for hint

The XML configuration will still work, although annotation-based config will be the preferred option.

[stupserich.rudi.strasser.gmail.com]

Is the following WARNING something to worry about?

22:12:45,426 WARNING [ServiceLoader] Could not load service class org.jboss.seam.transaction.TransactionExtension
22:12:45,426 WARNING [ServiceLoader] Could not load service class org.jboss.seam.transaction.scope.TransactionScopeExtension

The warning comes when I deploy an application derived from the weld J2ee archetype.

[lightguard]

What server are you deploying on?

[stupserich.rudi.strasser.gmail.com]

JBOSS 6.1.0

[lightguard]

Try AS7 and see if you have the same problem. If you don't it could be a regression.