[
https://jira.jboss.org/jira/browse/JBAS-6716?page=com.atlassian.jira.plug...
]
Emanuel Muckenhuber commented on JBAS-6716:
-------------------------------------------
I see, so the problem was when there was no security config specified and you tried to add
one? This is fixed in r87066.
add back securityConfig config property to JMS destination resources
---------------------------------------------------------------------
Key: JBAS-6716
URL:
https://jira.jboss.org/jira/browse/JBAS-6716
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Charles Crouch
Assignee: Emanuel Muckenhuber
Priority: Blocker
Fix For: JBossAS-5.1.0.CR1
Attachments: MyQueueWithSecurityConfig-service.xml
e.g.
<c:map-property required="false" name="securityConfig"
description="The destination's security configuration">
<c:simple-property required="false"
name="tagName"/>
</c:map-property>
--
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