6:41 p.m.
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Tim Fox
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
12:33 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Howard Gao reassigned JBMESSAGING-1667:
---------------------------------------
Assignee: Howard Gao (was: Tim Fox)
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
12:35 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1667:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP09
1.4.5.GA
Affects Version/s: 1.4.0.SP3.CP08
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
3:34 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Tim Fox updated JBMESSAGING-1667:
---------------------------------
Issue Type: Feature Request (was: Bug)
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
3:36 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1667:
--------------------------------------
Most messaging systems use the dot '.' not the slash to separate words in
hierarchical topics.
This is what I recommend you do, which will already work with JBM 1.x
<mbean code="..." name="...,name=app1.emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=app2.emails">
<attribute name="JNDIName">app2/emails</attribute>
<mbean code="..." name="...,name=app3.subapp2..emails">
<attribute name="JNDIName">app1/subapp2/emails</attribute>
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
3:53 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1667:
--------------------------------------
JBM, ActiveMQ, also any AMQP based system will use dots. JBM 2.0 uses dots too. (see
http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/...
)
Using slashes won't allow you to exploit wildcard routing in JBM 2.0 (or ActiveMQ or
many other systems for that matter).
I recommend for this task we keep the behaviour as is and explicitly disallow the forward
slash character in destination names. We can throw a warning on deploy and not deploy them
if they contain the forward slash character.
I am loathed to give special status to the forward slash character that would make it
create subcontextes automatically since this goes against the grain of normal conventions
for topic hierarchies.
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
3:59 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1667:
-----------------------------------------
I agree with Tim.
Howard
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
8:39 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Richard Kennard commented on JBMESSAGING-1667:
----------------------------------------------
Fair enough, I will use dots.
Many thanks for spending time discussing and looking into this issue for me.
Regards,
Richard.
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
7:42 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Howard Gao closed JBMESSAGING-1667.
-----------------------------------
Resolution: Rejected
close this as discussed.
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
7:56 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Tim Fox reopened JBMESSAGING-1667:
----------------------------------
The issue shouldn't be closed.
Like I mentioned in my earlier comment, we should explicit check that destination names do
not contain forward slashes, log a warning and reject deployment if so.
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
4:14 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1667:
-----------------------------------------
We can check the name in DestinationServiceSupport.startService(), if it contains forward
slash, throw an exception, that make the deployment fail.
if (name.contains("/"))
{
throw new IllegalStateException("The " + (isQueue() ?
"queue" : "topic") +
" " +
"name should not contain forward slash
" + name);
}
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
1:05 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.ji...
]
Howard Gao closed JBMESSAGING-1667.
-----------------------------------
Resolution: Done
done.
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
5:10 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/browse/JBMESSAGING-1667?page=com.atlassian.jira.pl...
]
Tim Fox commented on JBMESSAGING-1667:
--------------------------------------
It's not a bug
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
10:47 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/browse/JBMESSAGING-1667?page=com.atlassian.jira.pl...
]
Howard Gao commented on JBMESSAGING-1667:
-----------------------------------------
Hi Justin,
I see why it worked. It is because a temporary destination is never registered with JNDI,
so there is no JNDI bindings in the process of creating a temp destination. See
DestinationJNDIMapper.registerDestination().
I think you can create a new Jira if this needs to be fixed. Thanks.
Howard
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
11 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/browse/JBMESSAGING-1667?page=com.atlassian.jira.pl...
]
Richard Kennard commented on JBMESSAGING-1667:
----------------------------------------------
Nobody called Justin has commented on this issue? Did you enter this comment in the wrong
issue? :)
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
12:23 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1667) MBeans cannot have heirarchical names
[
https://jira.jboss.org/browse/JBMESSAGING-1667?page=com.atlassian.jira.pl...
]
Howard Gao commented on JBMESSAGING-1667:
-----------------------------------------
I'm sorry Richard, it is a response to Justin's private comments. I forgot to mark
it as a private one. :)
MBeans cannot have heirarchical names
-------------------------------------
Key: JBMESSAGING-1667
URL: https://jira.jboss.org/browse/JBMESSAGING-1667
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Destination Manager
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Environment: JBoss 5.1.0.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names,
for example:
<mbean code="..." name="...,name=app1/emails">
The forward slash in 'app1/emails' created a nested JNDI context of
'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying
that the top-level context 'app1' does not exist. This is true, but JBoss should
create it just-in-time.
A workaround proposed on the forums is to use the 'JNDIName' attribute:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
This works from a JNDI perspective, but the mbean itself is still named just
'emails' leaving the potential for name clashes:
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>
<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own
heirarchies to avoid the possibility of name clashes. It would be nice to have this in
JBoss 5.1.0.GA too.
--
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
5273
days inactive
5616
days old
15 comments
3 participants
participants (3)
-
Howard Gao (JIRA) -
Richard Kennard (JIRA)
-
Tim Fox (JIRA)