I just had a superficial look into this topic for Seam. Acegi is complex ... for many of my colleagues an enigma. But we've been able to handle very requirement regarding Authentication/Authorization. What I like on Acegi is that the application code can be written at first without any tags or security considerations like specific roles etc.. Later on you can configure the usage of it and implement required authorization classes.
To hear that Seam Security Layer and JBoss rules are similar flexible to Acegi sound good. Currently we have some framework classes developed based on Acegi for integrating an application in our infrastructure.
CacheUp
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127263#4127263
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127263
Yes you can use Acegi instead of Seam security in a Seam application (I have done it - but now I'm using Seam security).
I used Acegi because Seam security didn't exist in Seam when I started to use Seam.
I will recommend Seam security because it's a lot easier to use in a Seam application :-)
BTW: Why do you think Acegi is more powerful? You can use JBoss Rules (can be very complex) in Seam security.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127259#4127259
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127259
Use @PersistenceContext if you are using EJB3 and if you need a new transaction (@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) ) - Seam ref:
anonymous wrote :
| If you are using EJB3 and mark your class or method @TransactionAttribute(REQUIRES_NEW) then the trans-
| action and persistence context shouldn't be propagated to method calls on this object. However as the Seam-
| managed persistence context is propagated to any component within the conversation, it will be propagated to
| methods marked REQUIRES_NEW. Therefore, if you mark a method REQUIRES_NEW then you should access the en-
| tity manager using @PersistenceContext.
|
otherwise use SMPC.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127255#4127255
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127255