Remove unused components
------------------------
Key: JBAS-7508
URL: https://jira.jboss.org/jira/browse/JBAS-7508
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Other
Reporter: Dimitris Andreadis
Assignee: Dimitris Andreadis
Priority: Critical
Fix For: JBossAS-6.0.0.M2
Create subtasks for dead-code or components that should be removed from the AS6 series.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Ejb3Deployer does not inject an EjbReferenceResolver into an Ejb3Deployment
---------------------------------------------------------------------------
Key: JBAS-7780
URL: https://jira.jboss.org/jira/browse/JBAS-7780
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-6.0.0.M2
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Web Service Memory Leak of org.jboss.ws.extensions.security.SimplePrincipal
----------------------------------------------------------------------------
Key: JBAS-7793
URL: https://jira.jboss.org/jira/browse/JBAS-7793
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: JBossAS-6.0.0.M2
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: JBossAS-6.0.0.M3
The JBossWS container integration is still using SecurityAssociation however it should be migrated to SecurityContextAssociation - the SecurityContextAssociations will be automatically cleared at the end of each request which will clear this memory leak.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
MappedReferenceMetaDataResolverDeployer.mapEjbs() sets incorrect ContainerDependencyMetaData.containerName
----------------------------------------------------------------------------------------------------------
Key: JBAS-7744
URL: https://jira.jboss.org/jira/browse/JBAS-7744
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Reporter: Brian Stansberry
Assignee: Carlo de Wolf
Fix For: JBossAS-6.0.0.M2
See discussion in comments on JBAS-7703.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Move twiddle under the top-level management module
--------------------------------------------------
Key: JBAS-7717
URL: https://jira.jboss.org/jira/browse/JBAS-7717
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build System
Reporter: Dimitris Andreadis
Assignee: Paul Gier
Fix For: JBossAS-6.0.0.M3
With the removal of the web-console (JBAS-7509), the top-level 'console' module is more or less obsolete. The remaining console/widdle' module should really be moved under the top-level 'management' module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Allow EJB 3.1 beans to be deployed from within a war
----------------------------------------------------
Key: JBAS-7526
URL: https://jira.jboss.org/jira/browse/JBAS-7526
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: EJB3, Web (Tomcat) service
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Fix For: JBossAS-6.0.0.M2
EJB 3.1 FR 20.4: Enterprise Beans Packaged within a .war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Remove EJB2 from the 'default' config
-------------------------------------
Key: JBAS-7562
URL: https://jira.jboss.org/jira/browse/JBAS-7562
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: EJB2
Reporter: Brian Stansberry
Fix For: JBossAS-6.0.0.M3
Perform a trimming exercise on 'default'. If it remains in 'all' this shouldn't break the testsuite (knock on wood).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Move log services deployer into earlier bootstrap phase
-------------------------------------------------------
Key: JBAS-7683
URL: https://jira.jboss.org/jira/browse/JBAS-7683
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Logging
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: JBossAS-6.0.0.M3
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Try to profile which unguarded log.debug statements are expensive
-----------------------------------------------------------------
Key: JBAS-7693
URL: https://jira.jboss.org/jira/browse/JBAS-7693
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Fix For: JBossAS-6.0.0.M3
See if there is a way other than manual inspection to identify non-spammy log.debug() statements that are expensive.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
AOP does not properly implement latest logging SPI
--------------------------------------------------
Key: JBAS-7437
URL: https://jira.jboss.org/jira/browse/JBAS-7437
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: AOP
Reporter: David Lloyd
Assignee: Kabir Khan
Fix For: JBossAS-6.0.0.M1
AOP can't instantiate the SystemOutLoggerPlugin because it does not implement the 2.2.0 logging SPI. This can result in errors like this:
Failed to initalize plugin: org.jboss.aop.util.logging.SystemOutLoggerPlugin@6719dc16, cause: java.lang.AbstractMethodError
in certain cases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira