you can have JAX-RPC map the SOAP element to a DOM element How to carry out such a mapping ??
saurabh >>> [EMAIL PROTECTED] 5/27/2003 5:10:44 PM >>> The purpose of the JAX-RPC APIs is to provide an RMI-like programming experience. It supports three programming APIs: - stub: the client proxy is precompiled - service: the client proxy interface is predefined, but the implementation is generated using dynamic proxy - call: a dynamic invocation interface The first two look and feel very much like RMI. The third permits you to dynamically construct a SOAP call based on the WSDL. In all three circumstances, the JAX-RPC serialization subsystem generally performs the [de]serialization process for you. If you would prefer to manipulate the XML manually, you have two choices: - you can have JAX-RPC map the SOAP element to a DOM element - you can use the low-level API -- SAAJ -- which gives you direct access to the SOAP envelope As for EJB support, it's defined in the Web Services for J2EE (JSR-109) specification. Anne ----- Original Message ----- From: "Saurabh Arora" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 27, 2003 7:17 AM Subject: Re: message style and no support for EJB? > Message style seems to be a very effective for webservice development, > if you want to handle the processing of parameter. > > IS it part of JAX-RPC Spec. i cannot find the reference. Is their a > compatible support in JAX-RPC spec. > > Can somebody guide me for the same. > > saurabh arora > > >>> [EMAIL PROTECTED] 5/12/2003 10:40:38 PM >>> > > > > > Hi All > I was trying to deploy a message style web service and in the > deploy.wsdd > we had > > <service name="ejbdoctest" provider="java:MSG" style="message"> > <wsdlFile>c:/anamitra/ejbdoctest.wsdl</wsdlFile> > <parameter name="allowedMethods" value="processData"/> > <parameter name="wsdlPortType" value="WSTest"/> > <parameter name="scope" value="Request"/> > <parameter name="wsdlServicePort" value="WSTest"/> > <parameter name="wsdlTargetNamespace" value="www.mro.com/mea"/> > <parameter name="wsdlServiceElement" value="WSTestService"/> > <parameter name="className" value="test1.SimpleDocTest"/> > </service> > > And my class method is like > > public Document processData(Document doc) - inline with the MSG style > Webservices of Axis. > > This works perfectly . > But if we try to invoke an EJB [which has the same method processData] > - > thats where the java:MSG provider is failing. > > <service name="ejbdoctest" provider="java:MSG" style="message"> > <wsdlFile>c:/anamitra/ejbdoctest.wsdl</wsdlFile> > <parameter name="wsdlPortType" value="WSTest"/> > <parameter name="scope" value="Request"/> > <parameter name="wsdlServicePort" value="WSTest"/> > <parameter name="wsdlTargetNamespace" value="www.mro.com/mea"/> > <parameter name="wsdlServiceElement" value="WSTestService"/> > <parameter name="beanJndiName" value="testdoc"/> > <parameter name="homeInterfaceName" value="test1.TestHome"/> > <parameter name="remoteInterfaceName" value="test1.Test"/> > <parameter name="jndiURL" value="t3://localhost:7001"/> > <parameter name="allowedMethods" value="sayHello"/> > <parameter name="jndiContextClass" > value="weblogic.jndi.WLInitialContextFactory"/> > </service> > > So I changed it to a java:EJB provider - but in that case it expects > the > client to give a "Document" object and tries to serialize/deserialize > that. > This is a bit strange as either the java:MSG provider should be able > to > handle calling EJB's or EJB provider has to support that same thing as > the > MSG provider - ie bypass the java/XML data types binding. > > Any pointers appreciated. > thanks > Anamitra >
