You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Ivan Prochazka <ip...@borland.com> on 2001/09/06 15:17:37 UTC

EJB DeploymentDescriptor when connecting to Borland AppServer 4.5.1

Has anybody looked att integrating Soap with Borland AppServer 4.5.1 ??

I'm thinking specifically at following parameters in Soaps EJB DeploymentDescriptors

   <isd:option key="ContextProviderURL" value=??? />
   <isd:option key="FullContextFactoryName" value="com.inprise.j2ee.jndi.CtxFactory" />   ??

Gratfull for any Idea.

                              Ivan P.

Re: EJB DeploymentDescriptor when connecting to Borland AppServer 4.5.1

Posted by Colin Mondesir <cm...@borland.com>.
The following allows soap access to an entity bean called Attendee:

<?xml version="1.0"?>
<isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment"
             id="urn:attendeeprovider">
  <isd:provider type="org.apache.soap.providers.EntityEJBProvider"
                scope="Application"
                methods="create">
    <isd:java class="Attendee"/>
    <isd:option key="FullHomeInterfaceName" value="meetings.AttendeeHome" />
    <isd:option key="ContextProviderURL" value="iiop://<server name or IP>:14666" />
    <isd:option key="FullContextFactoryName" value="com.inprise.j2ee.jndi.CtxFactory" />
  </isd:provider>
 <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
</isd:service>

Start the naming service on a specific port:

vbroker.se.iiop_tp.scm.iiop_tp.listener.port=14666 (see naming service FAQ for more details)

  ----- Original Message ----- 
  From: Ivan Prochazka 
  To: soap-user@xml.apache.org 
  Sent: Thursday, September 06, 2001 2:17 PM
  Subject: EJB DeploymentDescriptor when connecting to Borland AppServer 4.5.1


  Has anybody looked att integrating Soap with Borland AppServer 4.5.1 ??
   
  I'm thinking specifically at following parameters in Soaps EJB DeploymentDescriptors
   
     <isd:option key="ContextProviderURL" value=??? />
     <isd:option key="FullContextFactoryName" value="com.inprise.j2ee.jndi.CtxFactory" />   ??
   
  Gratfull for any Idea.
   
                                Ivan P.

Re: EJB DeploymentDescriptor when connecting to Borland AppServer 4.5.1

Posted by Colin Mondesir <cm...@borland.com>.
The following allows soap access to an entity bean called Attendee:

<?xml version="1.0"?>
<isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment"
             id="urn:attendeeprovider">
  <isd:provider type="org.apache.soap.providers.EntityEJBProvider"
                scope="Application"
                methods="create">
    <isd:java class="Attendee"/>
    <isd:option key="FullHomeInterfaceName" value="meetings.AttendeeHome" />
    <isd:option key="ContextProviderURL" value="iiop://<server name or IP>:14666" />
    <isd:option key="FullContextFactoryName" value="com.inprise.j2ee.jndi.CtxFactory" />
  </isd:provider>
 <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
</isd:service>

Start the naming service on a specific port:

vbroker.se.iiop_tp.scm.iiop_tp.listener.port=14666 (see naming service FAQ for more details)

  ----- Original Message ----- 
  From: Ivan Prochazka 
  To: soap-user@xml.apache.org 
  Sent: Thursday, September 06, 2001 2:17 PM
  Subject: EJB DeploymentDescriptor when connecting to Borland AppServer 4.5.1


  Has anybody looked att integrating Soap with Borland AppServer 4.5.1 ??
   
  I'm thinking specifically at following parameters in Soaps EJB DeploymentDescriptors
   
     <isd:option key="ContextProviderURL" value=??? />
     <isd:option key="FullContextFactoryName" value="com.inprise.j2ee.jndi.CtxFactory" />   ??
   
  Gratfull for any Idea.
   
                                Ivan P.