[ http://jira.jboss.com/jira/browse/EJBTHREE-498?page=all ]
Bill Burke updated EJBTHREE-498:
--------------------------------
Fix Version/s: EJB 3.0 RC10 - FD
(was: EJB 3.0 RC9 - FD)
> Review duplicate security constructs
> ------------------------------------
>
> Key: EJBTHREE-498
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-498
> Project: EJB 3.0
> Issue Type: Task
> Components: Security
> Reporter: Scott M Stark
> Assigned To: Scott M Stark
> Fix For: EJB 3.0 RC10 - FD
>
>
> Both ejb3 and aspects/aop have duplicate implementations of JBossSX security constructs that should belong to that project rather than replicated elsewhere. I need to review these and move them into the security project where approriate.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/EJBTHREE-141?page=all ]
Bill Burke updated EJBTHREE-141:
--------------------------------
Fix Version/s: (was: EJB 3.0 RC9 - FD)
EJB 3.0 RC10 - FD
> Stateful session PostConstruct missing transaction, security contexts
> ---------------------------------------------------------------------
>
> Key: EJBTHREE-141
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-141
> Project: EJB 3.0
> Issue Type: Bug
> Components: EJB3 Extensions
> Environment: jboss-head
> Reporter: Jeff Schnitzer
> Assigned To: Bill Burke
> Fix For: EJB 3.0 RC10 - FD
>
>
> While PostConstruct for stateless beans does not run in a transaction or security context, stateful beans are different. From section 5.1.4.1 "Semantics of the Life Cycle Callback Methods for Stateful Session Beans" of the ejb3-edr2 spec:
> "The PostConstruct method is invoked in the transaction context and security contexts of the first business method on the bean."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/EJBTHREE-585?page=all ]
Bill Burke updated EJBTHREE-585:
--------------------------------
Fix Version/s: EJB 3.0 RC10 - FD
(was: EJB 3.0 RC9 - FD)
> ejb3 fine-grained sfsb replication support
> ------------------------------------------
>
> Key: EJBTHREE-585
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-585
> Project: EJB 3.0
> Issue Type: Feature Request
> Components: Clustering
> Reporter: Ben Wang
> Assigned To: Ben Wang
> Fix For: EJB 3.0 RC10 - FD
>
>
> This is the parent issue to track the overal fine-grained implementation using PojoCache
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/EJBTHREE-305?page=all ]
Bill Burke updated EJBTHREE-305:
--------------------------------
Fix Version/s: EJB 3.0 RC10 - FD
(was: EJB 3.0 RC9 - FD)
> Port EJB 2.1 tests to EJB 3.0 where appropriate
> -----------------------------------------------
>
> Key: EJBTHREE-305
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-305
> Project: EJB 3.0
> Issue Type: Task
> Affects Versions: EJB 3.0 RC4 - PFD
> Reporter: Bill Burke
> Assigned To: William DeCoste
> Fix For: EJB 3.0 RC10 - FD
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira