cvs commit: xml-axis-wsif/java/doc/wsdl_extensions ejb_extension.html

[owenb]

owenb       2002/12/16 03:33:37

  Modified:    java/doc/wsdl_extensions ejb_extension.html
  Log:
  Corrections to ejb:address information and to the example wsdl
  
  Revision  Changes    Path
  1.2       +2 -2      xml-axis-wsif/java/doc/wsdl_extensions/ejb_extension.html
  
  Index: ejb_extension.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/doc/wsdl_extensions/ejb_extension.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ejb_extension.html        10 Dec 2002 18:37:26 -0000      1.1
  +++ ejb_extension.html        16 Dec 2002 11:33:37 -0000      1.2
  @@ -66,7 +66,7 @@
   
   <li><b><tt>ejb:address</tt></b>
   <p>This element is an extension under the WSDL <em>port</em> element that allows 
specification of an EJB object as an endpoint for a service available via the EJB 
binding. The port whose address is specified this way must be associated with an EJB 
binding only.</p>
  -<p>The <emclassName</em> attribute specifies the fully qualified name of the java 
class to be used for service invocation. The optional <em>jndiName</em> attribute 
specifies the name under which this EJB can be looked up in a JNDI context.  The 
<em>initialContextFactory</em> and <em>jndiProviderURL</em> attributes complete the 
set if information required to perform a JNDI lookup for the EJB. The optional 
<em>classLoader</em> attribute specifies the class loader to be used for loading the 
service class, and the optional <em>archive</em> attribute is the location of a jar 
file that the client would need. It is upto the service provider to insure that all 
java methods used for mapping abstract operations must be publicly available through 
the specified interface in the EJB.</p>
  +<p>The <em>className</em> attribute specifies the fully qualified name of the home 
interface class of the EJB. The optional <em>jndiName</em> attribute specifies the 
name under which this EJB can be looked up in a JNDI context.  The 
<em>initialContextFactory</em> and <em>jndiProviderURL</em> attributes complete the 
set if information required to perform a JNDI lookup for the EJB. The optional 
<em>classLoader</em> attribute specifies the class loader to be used for loading the 
service class, and the optional <em>archive</em> attribute is the location of a jar 
file that the client would need. It is upto the service provider to insure that all 
java methods used for mapping abstract operations must be publicly available through 
the specified interface in the EJB.</p>
   </ul>
   
   <h4>Example:</h4>
  @@ -173,7 +173,7 @@
     &lt;!-- service decln --&gt;
     &lt;service name="AddressBookService"&gt;
       &lt;port name="EJBPort" binding="tns:EJBBinding"&gt;
  -      &lt;java:address className="addressbook.wsiftypes.AddressBook"
  +      &lt;ejb:address className="addressbook.wsiftypes.AddressBookHome"
                          jndiName="/services/addressbook"
                          
initialContextFactory="com.mycompany.server.MyappInitialContext"
                          
jndiProviderURL="ormi://myserver.mycompany.com/ejbsample"/&gt;