JDKLogImpl category for Class is incorrect
------------------------------------------
Key: JGRP-1224
URL: https://jira.jboss.org/browse/JGRP-1224
Project: JGroups
Issue Type: Bug
Affects Versions: 2.10
Environment: All
Reporter: Robert Eden
Assignee: Bela Ban
Priority: Minor
The JDKLogImpl class initializes the category using Class.toString, but should instead be using getName(). The toString() produces values such as "class org.jgroups.conf.ConfiguratorFactory" when we just want the class name.
Fix is. Replace this:
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Correctly determine client class path
-------------------------------------
Key: JBAS-8153
URL: https://jira.jboss.org/browse/JBAS-8153
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: AppClient
Reporter: Carlo de Wolf
Assignee: jaikiran pai
Priority: Critical
Fix For: 6.0.0.M4
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
ClientLauncher does not mount archives
--------------------------------------
Key: JBAS-8152
URL: https://jira.jboss.org/browse/JBAS-8152
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: AppClient
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Priority: Critical
Fix For: 6.0.0.M4
With the introduction of VFS 3 mounting archives has become mandatory. The ClientLauncher does not mount the archives it tries to query during class loading, resulting in CNFEs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Fix setting of custom SecurityManager class
-------------------------------------------
Key: JBAS-8025
URL: https://jira.jboss.org/jira/browse/JBAS-8025
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: 6.0.0.M3
Reporter: Marcus Moyses
Assignee: Anil Saldhana
Fix For: 6.0.0.CR1
Setting the attribute SecurityManagerClassName in conf/jboss-service.xml to a custom name has no effect. JBoss is always using the default class.
Also setting the authenticationMgrClass property of JNDIBasedSecurityManagement bean has no effect either.
--
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
ClassCastException if JavassistTypeInfo super class info is a reflect one
-------------------------------------------------------------------------
Key: JBREFLECT-131
URL: https://jira.jboss.org/browse/JBREFLECT-131
Project: JBoss Reflection
Issue Type: Bug
Affects Versions: JBossReflection.2.2.0.Alpha7
Reporter: Kabir Khan
Assignee: Kabir Khan
Fix For: 2.2.0.Beta
See linked issues for a description of the problem
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Inheritance of TransactionAttribute results in wrong metadata
-------------------------------------------------------------
Key: JBMETA-292
URL: https://jira.jboss.org/browse/JBMETA-292
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ejb
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Fix For: jboss-metadata-ejb-2.0.0-alpha-17
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Assure version compatibility with earlier versions of Remoting
--------------------------------------------------------------
Key: JBREM-1232
URL: https://jira.jboss.org/browse/JBREM-1232
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.3 (Flounder)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Update remoting guide for "generalizeSocketException"
-----------------------------------------------------
Key: JBREM-1219
URL: https://jira.jboss.org/jira/browse/JBREM-1219
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Components: docs
Affects Versions: 2.5.2.SP2 (Flounder), 2.2.3.SP1
Reporter: Justin Bertram
Per https://jira.jboss.org/jira/browse/JBREM-1146 the remoting guide needs to be updated to document the "generalizeSocketException" parameter.
--
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
password_tool.bat is needed to mirror the password_tool.sh script in bin directory
----------------------------------------------------------------------------------
Key: JBAS-7943
URL: https://jira.jboss.org/jira/browse/JBAS-7943
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: JBossAS-6.0.0.M2, JBossAS-5.1.0.GA
Reporter: Anil Saldhana
Assignee: Anil Saldhana
Fix For: JBossAS-6.0.0.M4
We have the password_tool.sh in the bin directory. We need the windows version.
--
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