Oops, disregard that, looks like it is actually not defined in any of our pre-defined modules.

What is the full stack trace you get when you include the path in your jboss-deployment-structure.xml ? (and what does this file look like)


On Mon, 15 Feb 2016 at 09:44 Stuart Douglas <stuart.w.douglas@gmail.com> wrote:
You should be able to use this if you have a dependency on the sun.jdk module.


On Mon, 15 Feb 2016 at 09:41 Michael Musgrove <mmusgrov@redhat.com> wrote:
I am attempting to lookup a remote EJB from WildFly to WLS.

If I use COSNaming as required by [1] (by setting INITIAL_CONTEXT_FACTORY to "com.sun.jndi.cosnaming.CNCtxFactory") I get the following error on the WildFly end:
  "ClassNotFoundException: com.sun.jndi.cosnaming.CNCtxFactory"

If I use the default wildfly name service (new InitialContext().lookup("corbaname:iiop:localhost:7001/NameService#SessionBean")) I get the following error on the WLS end (presumably because I am not using CNCtxFactory):
  "A RuntimeException was generated by the RMI server: weblogic.corba.cos.naming.RootNamingContextImpl.resolve([Lorg.omg.CosNaming.NameComponent"

I did try adding the CosNaming dependency (<path name="com/sun/jndi/cosnaming"/>) to modules/system/layers/base/sun/jdk/main/module.xml or to jboss-deployment-structure.xml in my deployment but that approach did not work.


Michael Musgrove
Transactions Team
t: +44 191 243 0870

Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (US), Paul Hickey (Ireland), Matt Parson
(US), Charles Peters (US)

Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael O'Neill(Ireland)
wildfly-dev mailing list