[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
[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
[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
[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