M, the application is
responsible for constructing the message.
In other words, use JAX-RPC when your application wants to work with Java
objects; and use JAXM when your application wants to work with XML.
Regards,
Anne
-----Original Message-
From: Rahul Jain [mailto:[EMAIL PROTECTED]
Sent: Thurs
that pulls the XML string from the SOAP
message
and invokes your EJB. If you were exposing an ordinary Java object
interface
then you wouldn't need a wrapper. You could simply invoke the service using
the EJB provider. JSR 109 (WSEE) defines standards for exposing EJB
stateless session bea
onal to the method used to construct the
message.
Anne
-Original Message-
From: Rahul Jain [mailto:[EMAIL PROTECTED]
Sent: Monday, June 14, 2004 2:28 PM
To: [EMAIL PROTECTED]
Subject: RE: Exposing an EJB as a doc-literal web service
Hi Anne,
Attached is the WSDL file.
Your hunch was right. A
Hi,
Sorry...here is the attachd WSDL for the non-wrapped doc-literal service.
Rahul.
From: "Rahul Jain" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Exposing an EJB as a doc-literal web service
Date: Mon, 14 Jun 2004 11:28:16 -0700
Hi Anne,
gnore any
subsequent elements. That first child element should be a wrapper element
that contains all your parameters.
Anne
-Original Message-
From: Rahul Jain [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 08, 2004 8:20 PM
To: [EMAIL PROTECTED]
Subject: RE: Exposing an EJB as a doc-literal web s
der can expose the EJB as a
doc-literal
web service. In the simplest case, all you have to do is change one line
in
your deploy.wsdd:
From
to
If you want to use straight up doc-lit and not wrapped style, just set
style="document" instead.
-Wei
-Original Message-
From: Rahul J
Hi,
Can somebody plz gudie me how I would expose an EJB as a doc-literal web
service? The build-in Axis EJB Provider exposes it as a RPC service only.
Thanks.
Rahul.
_
Looking to buy a house? Get informed with the Home Buying Guide f
