@Depends annotation does not work in EJB3 Embeddable release
------------------------------------------------------------
Key: EJBTHREE-727
URL: http://jira.jboss.com/jira/browse/EJBTHREE-727
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Magesh Kumar B
The ServiceOne, ServiceTwo and ServiceThree example given in the EJB3.0 documentation does not work when testing with the embeddable release
--
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
Special connective "or" constraint
----------------------------------
Key: JBRULES-500
URL: http://jira.jboss.com/jira/browse/JBRULES-500
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Reteoo, Rule Assemply/SPI
Reporter: Michael Neale
Assigned To: Mark Proctor
Would be nice to have some construct like
Person(address == null or age < 30)
which would kind of short circuit (ideally). Could be done as a special thing with alpha nodes, or another type of join node, or something else.
This is a common problem to have for users.
--
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
Unified Security Context
------------------------
Key: JBAS-3576
URL: http://jira.jboss.com/jira/browse/JBAS-3576
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: JBossAS-5.0.0.Beta
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: JBossAS-5.0.0.Beta
Currently the roles are an aspect of the Subject that is populated as part of the Jaas Authentication process (in the derivatives of the AbstractServerLoginModule). There is a need for the establishment of a security context to hold the roles, authoriation info etc.
--
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
Principal To Role mapping provider
----------------------------------
Key: SECURITY-11
URL: http://jira.jboss.com/jira/browse/SECURITY-11
Project: JBoss Security
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JBossSX
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: 2.0
We need a mechanism that will allow a user to configure a mapping of principal to roles that need to be added to the security context.
--
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
Package retroed deployer for JBoss 4 on jdk1.4
----------------------------------------------
Key: JBAOP-312
URL: http://jira.jboss.com/jira/browse/JBAOP-312
Project: JBoss AOP
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Kabir Khan
Assigned To: Kabir Khan
--
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
add support for authentication / permissions / ownership
---------------------------------------------------------
Key: JBRULES-399
URL: http://jira.jboss.com/jira/browse/JBRULES-399
Project: JBoss Rules
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Michael Neale
Assigned To: Michael Neale
For ben.
This authentication/permissions should be tied to the user context that JAAS established.
The only things that need to be programmatic are ideally ACLs on a resource. We may need however to show/hide functionality based on the users roles.
--
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
Rationalize the top-level mbean classes
---------------------------------------
Key: JBCACHE-856
URL: http://jira.jboss.com/jira/browse/JBCACHE-856
Project: JBoss Cache
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 2.0.0.GA
For the AS 5 beta I've added CacheJmxWrapper and PojoCacheJmxWrapper to meet the needs of the AS. There were existing classes in the jmx packages as well. Need to rationalize this; probably get rid of the old existing classes after any tests that use them are switched to the new ones.
--
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