July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1378) Make module directory configurable using .sh/.bat run scripts

by Rostislav Svoboda (JIRA)

Make module directory configurable using .sh/.bat run scripts ------------------------------------------------------------- Key: AS7-1378 URL: https://issues.jboss.org/browse/AS7-1378 Project: Application Server 7 Issue Type: Feature Request Reporter: Rostislav Svoboda Fix For: 7.1.0.Alpha1 Make module directory configurable using .sh/.bat run scripts, currently you can specify configuration location using '--server-config' or '--domain-config' + '--host-config' , location of modules directory should be configurable too. It's necessary to make changes on .bat/.sh files level to make module directory configurable. Currently it's hard-coded to use module directory under JBOSS_HOME directory {code} -mp \"$JBOSS_HOME/modules\" \ {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2262) When throwing an application exception in a method that is annotated with NOT_SUPPORTED it should not wrap the application Exception.

by Shaun Appleton (JIRA)

When throwing an application exception in a method that is annotated with NOT_SUPPORTED it should not wrap the application Exception. ------------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-2262 URL: https://issues.jboss.org/browse/EJBTHREE-2262 Project: EJB 3.0 Issue Type: Bug Reporter: Shaun Appleton When throwing an application exception in a method that is annotated with NOT_SUPPORTED it should not wrap the application Exception. What currently happen is that it is wrapped in an EJBException instead of being thrown un-wrapped. See Table 14 p361. of jsr-220 spec This has been tested on EAP 5.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-9231) Expose platform mxbeans via the domain model

by Brian Stansberry (JIRA)

Expose platform mxbeans via the domain model -------------------------------------------- Key: JBAS-9231 URL: https://issues.jboss.org/browse/JBAS-9231 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 Expose the java.lang.managment MXBeans. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (AS7-1317) Allow application exceptions to be defined when using the throws clause

by Carlo de Wolf (JIRA)

Allow application exceptions to be defined when using the throws clause ----------------------------------------------------------------------- Key: AS7-1317 URL: https://issues.jboss.org/browse/AS7-1317 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.0.Final Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-798) JMSTopicService and JMSQueueService made public for use outside of jboss-as-messaging

by Bob McWhirter (JIRA)

JMSTopicService and JMSQueueService made public for use outside of jboss-as-messaging ------------------------------------------------------------------------------------- Key: AS7-798 URL: https://issues.jboss.org/browse/AS7-798 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.0.0.Beta3 Reporter: Bob McWhirter Assignee: Jason Greene In TorqueBox, we allow applications to deploy queues with their application. JMSQueueService is perfect for it. But isn't public enough to consume. Likewise, JMSTopicService is slightly more public, but does involve some package-protected methods I might be interested in using. I'd love to have these services exposed enough to be externally useable. I understand the caveat of any queues/topics created this way being "unmanaged". I'm okay with that. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1405) Provide jms-topic DMR descriptions

by Heiko Braun (JIRA)

Provide jms-topic DMR descriptions ---------------------------------- Key: AS7-1405 URL: https://issues.jboss.org/browse/AS7-1405 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JMS Affects Versions: 7.0.0.Final Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.0.1.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1343) wsconsume.bat not working

by Mario Antollini (JIRA)

wsconsume.bat not working ------------------------- Key: AS7-1343 URL: https://issues.jboss.org/browse/AS7-1343 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.0.0.Final Environment: Windows 7 Reporter: Mario Antollini Assignee: Heiko Braun Fix For: Open To Community The file wsconsume.bat under the bin directory does not work. The problem is in this line: "-Djava.endorsed.dirs=file:%JBOSS_HOME%/modules/com/sun/xml/bin/main;file:%JBOSS_HOME%/modules/javax/xml/ws/api/main\" ^ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

7
10
0 / 0

[JBoss JIRA] Created: (JBBOOT-116) Implement a Graceful Shutdown API and Implementation

by Andrew Lee Rubinger (JIRA)

Implement a Graceful Shutdown API and Implementation ----------------------------------------------------- Key: JBBOOT-116 URL: https://jira.jboss.org/jira/browse/JBBOOT-116 Project: JBoss Bootstrap Issue Type: Feature Request Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger As identified by the Summer 2009 AS Meeting. Requirements: * Decoupled sufficiently from other Bootstrap mechanisms as to not leak out dependencies * 2-phase event-listener registration API * May be injected into MC Beans * 1st phase is a concurrent broadcast to all subsystems which have registered: "prepare for shutdown" * When all listeners have reported "ready", fire 2nd phase: "shutdown" -- 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
4
0 / 0

[JBoss JIRA] Created: (JBWEB-171) ClusteredSession.setAttribute() could report the attribute name and/or class FQN when not serializable

by James Livingston (JIRA)

ClusteredSession.setAttribute() could report the attribute name and/or class FQN when not serializable ------------------------------------------------------------------------------------------------------ Key: JBWEB-171 URL: https://jira.jboss.org/browse/JBWEB-171 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cluster Affects Versions: JBossWeb-2.1.3.GA Reporter: James Livingston Assignee: Remy Maucherat Priority: Minor org.jboss.web.tomcat.service.session.ClusteredSession.setAttribute() raises an exception with the clusteredSession.setAttribute.iae message if the attribute can't be replicated (i.e. isn't Serializable or a primitive). It would be nice if it mentioned the attribute name and/or the class FQN in the error message to aid in debugging. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBLOGGING-58) Support setting the logging provider explicitly

by Dan Allen (JIRA)

Support setting the logging provider explicitly ----------------------------------------------- Key: JBLOGGING-58 URL: https://issues.jboss.org/browse/JBLOGGING-58 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Dan Allen Assignee: David Lloyd Priority: Minor Fix For: 3.0.0.Beta5-jboss-logging Currently, JBoss Logging uses a classloading approach to look for a logging provider based on a hardcoded order of precedence. While this is sufficient for the default case, there should be a way to specify the logger explicitly, in the case that there is more than one concrete logging implementation on the classpath. The override should be part of the API, though a system property could also be supported. The API would take precedence. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
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 July 2011