[
https://issues.jboss.org/browse/AS7-3571?page=com.atlassian.jira.plugin.s...
]
Pavel Slavicek commented on AS7-3571:
-------------------------------------
Hi Heiko,
destination can have multiple JNDI names, see xsd for messaging configuration:
{code}
...
<xs:complexType name="jmsQueueType">
<xs:sequence>
<xs:element name="entry" type="entryType"
maxOccurs="unbounded" minOccurs="1" />
<xs:element name="selector" maxOccurs="1"
minOccurs="0">
<xs:complexType>
<xs:attribute name="string" type="xs:string"
use="required" />
</xs:complexType>
</xs:element>
<xs:element name="durable" type="xs:boolean"
maxOccurs="1" minOccurs="0" />
</xs:sequence>
<xs:attribute name="name" type="xs:string"
use="required" />
</xs:complexType>
...
{code}
Console should allow setting multiple JNDI names for JMS
queues/topics
----------------------------------------------------------------------
Key: AS7-3571
URL:
https://issues.jboss.org/browse/AS7-3571
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Jan Martiska
Assignee: Heiko Braun
Priority: Optional
Fix For: 7.1.1.Final
The model and CLI allow setting multiple JNDI names for JMS resources. In the admin
console, only one name is possible. Also, it is currently not possible to change the name
after the resource is created.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira