July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9011) Deployment phases need cleaning up

by David Lloyd (JIRA)

Deployment phases need cleaning up ---------------------------------- Key: JBAS-9011 URL: https://issues.jboss.org/browse/JBAS-9011 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 Every deployment phase adds a level of latency to deployment; thus we need to minimize them. There are some phases which are redundant, and some which are wholly unused which need to be consolidated and cleaned up. The deployment phase numbering should be finalized at this time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8979) Rename "ejb3" subsystem to "ejb"

by David Lloyd (JIRA)

Rename "ejb3" subsystem to "ejb" -------------------------------- Key: JBAS-8979 URL: https://issues.jboss.org/browse/JBAS-8979 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Minor Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8578) JMXConnector should support "jmxconnector" alias used by jmx-remoting.sar

by Scott Marlow (JIRA)

JMXConnector should support "jmxconnector" alias used by jmx-remoting.sar ------------------------------------------------------------------------- Key: JBAS-8578 URL: https://jira.jboss.org/browse/JBAS-8578 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMX Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 6.0.0.Final, 7.0.0.M2 For users that might of previously used jmx-remoting.sar. Add /jmxrmi alias for AS6+AS7. They could also later change their application for AS6/AS7 to use the "service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi" URL. This should be a one line change (I hope :-): registry.rebind("jmxrmi", rmiServer.toStub()); registry.rebind("jmxconnector", rmiServer.toStub()); -- 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

13 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-6332) Injection from outside modules

by Carlo de Wolf (JIRA)

Injection from outside modules ------------------------------ Key: JBAS-6332 URL: https://jira.jboss.org/jira/browse/JBAS-6332 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.GA Reporter: Carlo de Wolf When a servlet is packaged standalone (outside ear) and an EJB is packaged standalone, the EJB can't be injected into the servlet without specifying a JNDI name somewhere. It would be nice to have the ability to inject beans from outside your own enterprise application. -- 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

13 years, 2 months

7
9
0 / 0

[JBoss JIRA] Created: (JBAS-9192) Unclean handling of socket close

by Brian Stansberry (JIRA)

Unclean handling of socket close -------------------------------- Key: JBAS-9192 URL: https://issues.jboss.org/browse/JBAS-9192 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Minor Fix For: 7.0.0.Beta3 This stuff appears in the DC logs quite a bit, particularly at shutdown: [Host Controller] 10:55:26,174 ERROR [org.jboss.as.management] (Read thread for /127.0.0.1:59552) java.net.SocketException: Connection reset I've marked this as minor as it's not worth much effort unless it continues following the switch from jboss-as-protocol to Remoting3. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (AS7-878) Add a properties file based authentication configuration for the domain management security realm.

by Darran Lofthouse (JIRA)

Add a properties file based authentication configuration for the domain management security realm. -------------------------------------------------------------------------------------------------- Key: AS7-878 URL: https://issues.jboss.org/browse/AS7-878 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-892) InitialContextFactoryBuilder should use Class.forName with null ClassLoader instead of context class loader.

by Darran Lofthouse (JIRA)

InitialContextFactoryBuilder should use Class.forName with null ClassLoader instead of context class loader. ------------------------------------------------------------------------------------------------------------ Key: AS7-892 URL: https://issues.jboss.org/browse/AS7-892 Project: Application Server 7 Issue Type: Task Components: Naming Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1053) Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface

by Darran Lofthouse (JIRA)

Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface ------------------------------------------------------------------------------------------------- Key: AS7-1053 URL: https://issues.jboss.org/browse/AS7-1053 Project: Application Server 7 Issue Type: Task Components: Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Alpha1 It is reported that the realm used for the endpoint needs to match the endpoint name - for this reason the realm appears as 'endpoint' The realm should actually match the name of the realm being used as this is to inform the user of the realm they are using. This may also need expanding to multiple realms in the future so users in different realms can all authenticate against the same resource. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (SECURITY-467) Callbackhandlers to get information from various sources (DB/LDAP)

by Anil Saldhana (JIRA)

Callbackhandlers to get information from various sources (DB/LDAP) ------------------------------------------------------------------ Key: SECURITY-467 URL: https://jira.jboss.org/jira/browse/SECURITY-467 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta2 -- 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

13 years, 2 months

6
9
0 / 0

[JBoss JIRA] Created: (JBAS-8202) Repository SPI

by Brian Stansberry (JIRA)

Repository SPI -------------- Key: JBAS-8202 URL: https://jira.jboss.org/browse/JBAS-8202 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M2 SPI to allow the DomainController (and Server???) to pull content from a location besides the local filesystem. This doesn't need to be finalized for M1, so scheduling for M2. -- 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

13 years, 2 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011