Hi,

I'm trying to federate an external CosNaming service into the JBoss
3.2.1 JNDI namespace and I'm having a problem that the external context
does not list in the JNDIView.

I have deployed a file "cosnaming-service.xml" along with a file
"ate.tao.properties" as below

<!-- Bind the remote TAO Naming Service -->
  <mbean code="org.jboss.naming.ExternalContext"
name=":service=ExternalContext,jndiName=external/cosnaming">
    <attribute name="JndiName">external/cosnaming</attribute>
    <attribute name="Properties">ate.tao.properties</attribute>
    <attribute name="InitialContext">javax.naming.InitialContext</attribute>
    <attribute name="RemoteAccess">false</attribute>
  </mbean>

# ate.tao.properties
java.naming.factory.initial=com.sun.jndi.cosnaming.CNCtxFactory
java.naming.provider.url=corbaloc://nero:35002/NameService

In the JNDI view I can see "external/cosnaming" - it looks different
from the other entries though as it has no sub contexts and lists itself
as a "proxy" as below: 

     +- external (class: org.jnp.interfaces.NamingContext)
  |   +- cosnaming (proxy: $Proxy30 implements interface javax.naming.Context)

I would expect to see the contexts bound into my external corba naming
service and listed as for the other non-external contexts.

Any help would be a appreciated - I've been banging my head against the
keyboard on this one.

Cheers,
Alex.




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to