May 2011 - jboss-jira - Jboss List Archives

[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

14 years, 8 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

14 years, 8 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

14 years, 8 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

14 years, 8 months

2
4
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

14 years, 8 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

14 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-864) Support expressions in interface and socket related configs

by Brian Stansberry (JIRA)

Support expressions in interface and socket related configs ----------------------------------------------------------- Key: AS7-864 URL: https://issues.jboss.org/browse/AS7-864 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.CR1 Make it possible to fairly easily control socket bindings from the command line. So, we need expression support for: 1) Static interface criteria values (i.e. <inet-address value="${x}"/> and <loopback-address value="${x}"/> 2) The port-offset on a socket-binding-group 3) The multicast address and port on a socket-binding 4) *Perhaps* the default-interface on a socket-binding-group 5) *Perhaps* the interface on a socket-binding 6) The address and port in host.xml's <domain-controller><remote...> element 7) The port in the <management-interface> child elements 8) *Perhaps* the interface in the <management-interface> child elements -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-894) subsystem logging : boolean don't have a default or runtime value

by Heiko Rupp (JIRA)

subsystem logging : boolean don't have a default or runtime value ----------------------------------------------------------------- Key: AS7-894 URL: https://issues.jboss.org/browse/AS7-894 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Rupp [standalone@localhost:9999 subsystem=logging] ./periodic-rotating-file-handler=FILE:read-resource-description "append" => { "type" => BOOLEAN, "description" => "Specify whether to append to the target file.", "access-type" => "read-only", "storage" => "configuration" }, and [standalone@localhost:9999 subsystem=logging] ./periodic-rotating-file-handler=FILE:read-resource { "outcome" => "success", "result" => { "autoflush" => true, "encoding" => undefined, "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n", "level" => "INFO", "file" => { "path" => "server.log", "relative-to" => "jboss.server.log.dir" }, "suffix" => ".yyyy-MM-dd" }, Probably the same for other kinds of appenders. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-7656) jboss_init_redhat.sh needs to be more robust

by Henrik Aronsen (JIRA)

jboss_init_redhat.sh needs to be more robust -------------------------------------------- Key: JBAS-7656 URL: https://jira.jboss.org/jira/browse/JBAS-7656 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Other Reporter: Henrik Aronsen Fix For: JBossAS-6.0.0.M2, JBossAS-6.0.0.M3, JBossAS-6.0.0.CR1, JBossAS-6.0.0.GA I have tried to address the shortcomings of the current JBoss init script for RHEL5: - Uses PID file - Supports chkconfig - Supports start, stop, force-stop, reload, force-reload, status - Supports custom user and password on shutdown - Supports custom jndi host/port on shutdown - Does not allow second instance to start when one is already running - Does not rely on other files such as run.sh and run.conf - Verifies successful startup - The init script does not have to be edited, use the standard location for configuration (/etc/default/jboss) instead - Runs out of the box when no configuration is provided - Should support most Linuces All feedback is welcome -- I'm sure I forgot something in the provided script The init script is currently maintained at http://code.google.com/p/jboss-rpm/source/browse/#svn/trunk/src/main/etc (This issue was copied from JBPAPP-3194 as suggested by Fernando Nasser) -- 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

14 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-9102) Wildcard operations that span multiple processes

by Brian Stansberry (JIRA)

Wildcard operations that span multiple processes ------------------------------------------------ Key: JBAS-9102 URL: https://issues.jboss.org/browse/JBAS-9102 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.Beta2 Handle host=* and host=y,server=* type operations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011