Replace jmx-invoker-service.xml with jmx-remoting.sar
-----------------------------------------------------
Key: JBAS-3928
URL: http://jira.jboss.com/jira/browse/JBAS-3928
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: JMX, Remoting
Reporter: Scott M Stark
Assigned To: Scott M Stark
We need to complete the org.jboss.mx.remoting.service.JMXConnectorServerService jmx invoker to be at least as complete as the RMIAdaptor so we can replace the jmx-invoker-service.xml with the jmx-remoting.sar.
--
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
Abiltity to change priority of messages in a queue/durable sub
--------------------------------------------------------------
Key: JBMESSAGING-439
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-439
Project: JBoss Messaging
Issue Type: Feature Request
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Minor
Fix For: 1.0.2
A "nice to have" would be to allow the priority of messages in a destination to be changed by an administrator - this should be available via the normal management interfaces.
--
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
Improve message counter functionality
-------------------------------------
Key: JBMESSAGING-732
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-732
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.2.0.Beta2
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Minor
Fix For: 1.2.1
MessageCounter functionality can be improved by returning counters and history as XML as well as HTML, or in some other "machine friendly" format.
Also the history should be made "rolling", so only a moving window of data is retained to prevent a large buildup
--
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
Use Buddy Replication for clustered SFSBs
-----------------------------------------
Key: EJBTHREE-856
URL: http://jira.jboss.com/jira/browse/EJBTHREE-856
Project: EJB 3.0
Issue Type: Feature Request
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: EJB 3.0 RC11 - FD
Optimize the replicated SFSB cache for use with Buddy Replication. Basically means checking cache calls to ensure unwanted data gravitations do not occur.
--
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
SecurityDeployer: XACML Policy Registration
-------------------------------------------
Key: JBAS-4370
URL: http://jira.jboss.com/jira/browse/JBAS-4370
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: JBossAS-5.0.0.Beta3
Move the XACML Policy registration from the component modules to the security deployer.
--
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
EJB3 deployer must have an option for dynamic queue / topic creation
--------------------------------------------------------------------
Key: EJBTHREE-932
URL: http://jira.jboss.com/jira/browse/EJBTHREE-932
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Carlo de Wolf
Fix For: EJB 3.0 RC11 - FD
Currently when the MDB container can't find a queue it will always connect to ServerPeer and asks it to create one.
Scott:
Whether or not the ejb container creates destinations has to be a manageable, metadata driven policy. This is ultimately overridable by the managment layer/policy service as whether or not a given environment allows for dynamic creation of destinations is an admin policy decision. It has nothing to do with whether ejb3 and jbm exist in the same environment.
--
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
Update tc6-cluster.aop to match the current configuration
---------------------------------------------------------
Key: JBAS-3858
URL: http://jira.jboss.com/jira/browse/JBAS-3858
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Ben Wang
Fix For: JBossAS-5.0.0.Beta1
The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in tc6-cluster.aop. We need to sync up. We want to maintain support for the old Tomcat-specific interface markers as well.
--
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
XACML EJB Layer: Role Reference Checks
--------------------------------------
Key: SECURITY-50
URL: http://jira.jboss.com/jira/browse/SECURITY-50
Project: JBoss Security and Identity Management
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JBossSX
Affects Versions: 2.0.0.BETA
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: 2.0.1
Provide a mechanism to do EJBContext.isCallerInRole checks when xacml is enabled.
--
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
Validate Jacc Policy Module handles all run-as scenarios
--------------------------------------------------------
Key: SECURITY-29
URL: http://jira.jboss.com/jira/browse/SECURITY-29
Project: JBoss Security and Identity Management
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JBossSX
Affects Versions: 2.0.0.BETA
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: 2.0
With the roles being added to the security context via the mapping framework (for example), there may be cases where in run-as scenarios may not be adequately tested with the new Jacc authorization stuff.
--
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
Container Task:JBoss 4.2.x related Tasks for Security 2.0
---------------------------------------------------------
Key: SECURITY-27
URL: http://jira.jboss.com/jira/browse/SECURITY-27
Project: JBoss Security
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JBossSX
Affects Versions: 2.0
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: 2.0
Container task for all 4.2.x related tasks that need to be performed for the 5.x releases of JBAS.
--
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