Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#166 Issue with Hierarchical topics

v0.7.7-beta-1
open
Tim Anderson
jndi (13)
7
2008-05-01
2008-04-30
kashabm
No

I am trying to create hierarchical topics and I have the following in the configuration file:

<AdministeredTopic name="Topic1.Topic2" />
<AdministeredTopic name="Topic1.Topic2.Topic3" />

The creation of these topics seems to be fine. However, when "Topic1.Topic2.Topic3" is looked up in the JNDI context as follows, there is an exception thrown:

Topic topic = (Topic) context.lookup( "Topic1.Topic2.Topic3" );

The exception stackTrace is as follows:

javax.naming.NotContextException: Topic1/Topic2
at org.codehaus.spice.jndikit.AbstractLocalContext.lookupSubContext(AbstractLocalContext.java:380)
at org.codehaus.spice.jndikit.AbstractLocalContext.lookup(AbstractLocalContext.java:311)
at org.codehaus.spice.jndikit.rmi.server.RMINamingProviderImpl.lookup(RMINamingProviderImpl.java:158)
at org.exolab.jms.server.net.RemoteNamingProvider.lookup(RemoteNamingProvider.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:572)
at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:530)
at org.exolab.jms.common.threads.ThreadPool$NotifyingRunnable.run(ThreadPool.java:211)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)

If "Topic1/Topic2" is not created by having only
<AdministeredTopic name="Topic1.Topic2.Topic3" /> in the config file, everything works fine.

I am not sure if this is an expected behavior but I was expecting to create hierarchical chain of topics and subscribe to specific topics in the chain.

Thanks,

K

Discussion

  • kashabm
    kashabm
    2008-04-30

    • priority: 5 --> 7
     
  • kashabm
    kashabm
    2008-04-30

    Logged In: YES
    user_id=1927704
    Originator: YES

    Correction:

    The hierarchical topic is actually looked up as follows

    Topic topic = (Topic) context.lookup( "Topic1/Topic2/Topic3" );

    However, the hierarchical topic is specified as <AdministeredTopic name="Topic1.Topic2.Topic3" /> in the config file.

    Thanks,

    K

     
  • kashabm
    kashabm
    2008-05-01

    • assigned_to: nobody --> tanderson