While doing more research I found that Shane has following comment for Seam3 authorization functionality. However if Seam 3 is not going to be stable in few weeks we may not able to use Seam3. In that how Seam2.2 can provide same feature.
Unified authorization architecture - in Seam, authorization checks are performed in a singular manner. The Identity.hasPermission() method allows for a permission check to be carried out for the current user against multiple PermissionResolver implementations. We have implementations for Drools (rule-based) and for persistent permissions (ACL-based). A single permission check will invoke all registered PermissionResolver implementations to determine whether a user has the necessary privileges to execute a secured operation.
At this time then intention to use JBoss however it may be possible we end using WAS. In that scenario Seam framework is equally efficient?
However if Seam 3 is not going to be stable in few weeks we may not able to use Seam3
Just wondering if you are aware that a relevant part of the JEE 6 infrastructure is not final 'in a few weeks'?
As Seam 3 is based on Weld / CDI (which is final) and ships in separate modules, I would not expect too many problems there. Also: With CDI-SPI your are able to hack yourself into Javee EE 6, which can be an option for almost everything...
The real issue might be your infrastructure / dependend libraries:
Speaking of today, JBoss AS 6 has some major issues open and Richfaces 4 isn't final before the end of the year.
Right now I'm on a stack with some Seam 3 modules, a JBoss AS Nightly Build and Primefaces.
Most problems arise around JBoss AS and ... Eclipse
Thanks Jan. Based on information you have provided it makes sense not to take risk of using Seam3 when containers are not ready.
At present we are moving with WAS. I am not sure about the version at this time but we are going to use Hibernate. When I tried to find out deployment specification I found following chaper http://docs.jboss.org/seam/2.2.1.CR1/reference/en-US/html/websphere.html which talks about deploying with EJBs however I don't see any specification for deployment with Hibernate. Thogh there is a sample in 2.2.1 about deploying hibernate with WAS6.