Hide Forgot
Date of First Response: 2008-09-16 21:24:34 project_key: SOA Platform JIRA for project JIRA: JBNADM-3500
Link: Added: This issue depends JBMANCON-418
Charles commented that this is due to the console only expecting: '...deployment descriptors which exist as ordinary files on the filesystem, not contained within archives...' We'll need this changed in the console for ESB archives.
Jarek is seeing the same exception with an exploded ESB archive: https://jira.jboss.org/jira/browse/JBMANCON-418?focusedCommentId=12429431#action_12429431
https://jira.jboss.org/jira/browse/JBMANCON-418?focusedCommentId=12429620#action_12429620 The ONLY queue name that can be accessed by the embedded console is: "jboss.messaging.destination"
Update to point at underlying JBNADM issue (moved from JBMANCON). Len, you wouldn't have been able to tell this was a JBNADM issue, so I've got no problem with you continuing to raise issues like this in JBMANCON. The only ones that should go straight to JBNADM are those that you find when testing full JBoss ON, e.g. JON Server with distinct JON Agent installs. Hope the distinction makes sense, please ping me on #jboss-on if anything is unclear Thanks Charles
"The ONLY queue name that can be accessed by the embedded console is: "jboss.messaging.destination" " This is not strictly accurate. See the comment below for more details, we can discover all queues/topics, but we can only currently see configuration on the JBossMessaging ones. https://jira.jboss.org/jira/browse/JBNADM-3500?focusedCommentId=12429746#action_12429746
The NPE is not seen in the JON 6470 build - an error message is displayed instead.