Identity on Seam 2.1.0 SNAPSHOT

[larshuber]

Since I'm using the snapshot this exception occures by starting seam test environment.

FAILED CONFIGURATION: @BeforeSuite startSeam
java.lang.RuntimeException: Could not create Component: org.jboss.seam.security.identity
     at org.jboss.seam.init.Initialization.addComponent(Initialization.java:995)
     at org.jboss.seam.init.Initialization.installComponents(Initialization.java:911)
     at org.jboss.seam.init.Initialization.init(Initialization.java:589)
     at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:896)
     at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58)
Caused by: java.lang.IllegalArgumentException: no such setter method: org.jboss.seam.security.Identity.securityRules
     at org.jboss.seam.util.Reflections.getSetterMethod(Reflections.java:236)
     at org.jboss.seam.Component.initInitializers(Component.java:482)
     at org.jboss.seam.Component.<init>(Component.java:268)
     at org.jboss.seam.Component.<init>(Component.java:219)
     at org.jboss.seam.init.Initialization.addComponent(Initialization.java:979)
     ... 19 more
... Removed 15 stack frames

Where I have to change the implementation of the Identity in an existing project (2.0.1.GA). I saw that the implementation class name changed from RuleBasedIdentity to RuleBasedPermissionResolver ?

greets, Lars

[christian.bauer]

There is a major redesign going on in the security module. Do not use nightly snapshots if you don't want to move with that. We do not have the time to write code and support everyone on trunk development.

[larshuber]

this was done due to this topic:
DependentTesting

With trunk is  2.1.0.A1 meant and not a nightly build?

[christian.bauer]

Trunk is subversion trunk. Nightly snapshots are taken from the trunk. Do not use trunk code if you don't want to contribute code.

[shane.bryzak]

Look in the examples or seam-gen for the new configuration.  Basically you need to move the security rules from identity into the new rule-based permission resolver:

   <security:rule-based-permission-resolver security-rules="#{securityRules}"/>