>Hi Damon,
>
>In OXF, we are doing a lookup of the name you provide (typically 
>"java:comp/env/ejb/...", according to the JNDI naming policies 
>http://tinyurl.com/3g2zm). Setting up this EJB on a remote server is 
>done at the application server level. I have done this in the past 
>with WebLogic, but I don't have the necessary configuration files for 
>Tomcat/JBoss. Just let me know if you get this to work; I will be glad 
>to add a blurb about this in the documentation based on your feedback, 
>if this is fine with you of course.

Hi Alex,

Further updates on remote RMI calls into JBoss from Tomcat.. Seems like it can't be 
done in Tomcat 4.1 without adding a -nonaming property to Tomcat on startup which 
disables Tomcats own JNDI server. Not something I want to mess with right now.. All 
roads on the Jboss forums lead back to needing to set this property. :-( 
  http://www.jboss.org/index.html?module=bb&op=viewtopic&t=49890

Without -nonaming enabled the JNDI lookup is mistakenly looking for my EJB in Tomcat 
jndi, not JBOSS jndi. The error reported is. 
  class javax.naming.NamingException: Cannot create resource instance 

I have moved to Tomcat 5.0 in the hope the it has better support for remote EJB calls 
and initially seem to have got past this NamingException! I am now running into a 
NullPointerException that appears to be coming from the delegation processor but may 
just be hiding another underlying Tomcat configuration problem.

Time: 16:08:26��Priority: ERROR��Thread: http-8080-Processor25��NDC: null Category: 
org.orbeon.oxf.servlet.ProcessorService Location: 
org.orbeon.oxf.servlet.ProcessorService.service(ProcessorService.java:180) Message:
Exception with no location data
Throwable:
java.lang.NullPointerException
  at 
org.orbeon.oxf.processor.DelegationProcessor$2.endElement(DelegationProcessor.java:201)
  at org.dom4j.io.SAXWriter.endElement(SAXWriter.java:631)
  at org.dom4j.io.SAXWriter.write(SAXWriter.java:585)
  at org.dom4j.io.SAXWriter.writeContent(SAXWriter.java:479)
  at org.dom4j.io.SAXWriter.write(SAXWriter.java:180)
  at org.orbeon.oxf.processor.DebugProcessor$1.readImpl(DebugProcessor.java:50)
  at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:823)
  at 
org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:941)
  
I might wait until OXF 2.5 and test this again.

Regards,
Damon.
_______________________________________________
oxf-users mailing list
[EMAIL PROTECTED]
http://mail.orbeon.com/mailman/listinfo/oxf-users

Reply via email to