Well I've been using Axis for a while now. The namespace issue can be
resolved by using the follow:

      call.setProperty(Call.NAMESPACE, "urn:TheNameSpace");

An entire SOAP call would then look something like following:

      Service  service = new Service();
      Call     call    = (Call) service.createCall();
      call.setTargetEndpointAddress("http://endpoint";);
      call.setOperationName("MyOperation");
      call.setProperty(Call.NAMESPACE, namespace);
      Object result = call.invoke(params);

I've needed to specify the namespace when calling an Apache SOAP server from
an Apache Axis client.

Guy.

> -----Original Message-----
> From: Eddie Post [mailto:[EMAIL PROTECTED]]
> Sent: 11 March 2002 10:39
> To: Orion-Interest
> Cc: [EMAIL PROTECTED]
> Subject: RE: Soap with Axis ?
> 
> 
> Hellu,
> 
> Thanks for your reaction.
> 
> I see two examples of interest on the Atlassian site:
> - One with SOAP and EJB. I am just starting to use SOAP and 
> the example is 
> for Apache Soap and not with Apache Axis. Axis needs some 
> other values and I 
> don't know how what/how to change the SOAP values in the example.
> 
> - Axis with Orion integration. In the example you have a part 
> called Test, 
> which is the most interesting. The test section goes very 
> fast, for example, 
> there is a deployment with a deploy.xml but no deploy.xml is given.
> If I take the Calculator example of Axis itself I get the error (with 
> Calculator.class in the Axis/WEB-INF/classes dir):
> -----------
> C:\Ed_soft\Develop\Manual\xml-axis-alpha3\samples\ed>java -cp .;./a
> xis.jar;./log4j-core.jar;./jaxp.jar;./crimson.jar org.apache.axis.c
> lient.AdminClient -lhttp://localhost:9000/axis/servlet/AxisServlet
> deploy.wsdd
> Processing file deploy.wsdd
> AxisFault
>   faultCode: ns1:Server.NoService
>   faultString: The AXIS engine could not find a target service to i
> nvoke!  targetService is http://xml.apache.org/axis/wsdd/
>   faultActor: null
>   faultDetail:
>         exceptionName: org.apache.axis.AxisFault
> -----------
> 
> If I try the above with for example Tomcat I do get the error:
> -----------
> C:\Ed_soft\Develop\Manual\xml-axis-alpha3\samples\ed>java -cp .;./a
> xis.jar;./log4j-core.jar;./jaxp.jar;./crimson.jar org.apache.axis.c
> lient.AdminClient -lhttp://localhost:8080/axis/servlet/AxisServlet
> deploy.wsdd
> Processing file deploy.wsdd
> AxisFault
>   faultCode: http://xml.apache.org/axis/:Server.userException
>   faultString: org.xml.sax.SAXException: Bad envelope namespace:
>   faultActor: null
>   faultDetail:
>         exceptionName: org.xml.sax.SAXException
>         stackTrace: org.xml.sax.SAXException: Bad envelope namespac
> e:
> -----------
> 
> 
> Please any help on what the above errors mean ?
> 
> Eddie :(
> 
> 
> >From: DeVincentiis Giustino <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Subject: RE: Soap with Axis ?
> >Date: Mon, 11 Mar 2002 08:50:31 +0100
> >
> >Hello,
> >
> >Could you please let me know what is your problem with the example on
> >Atlassian KB?
> >
> >Thank you,
> >Giustino De Vincentiis
> >
> > > -----Original Message-----
> > > From: Eddie [mailto:[EMAIL PROTECTED]]
> > > Sent: Saturday, March 09, 2002 8:05 PM
> > > To: Orion-Interest
> > > Subject: Soap with Axis ?
> > >
> > >
> > > Hellu,
> > >
> > > Does anyone has an example descriptor of a web service to
> > > connect a client
> > > to a EJB through SOAP (Axis of Apache) ?
> > >
> > > Most os the examples I find are not based on Ejb connections
> > > and on the
> > > Atlassian site I saw a example for Apache Soap but I can't
> > > get it to work
> > > with Orion.
> > >
> > > Eddie
> > >
> 
> 
> _________________________________________________________________
> Chat with friends online, try MSN Messenger: http://messenger.msn.com
> 
> 


DISCLAIMER - The preceding e-mail message (including any attachments)
contains information that may be confidential, may be protected by the
attorney-client or other applicable privileges, or may constitute non-public
information.  It is intended to be conveyed only to the designated
recipient(s) named above.  If you are not an intended recipient of this
message, or have otherwise received it in error, please notify the sender by
replying to this message and then delete all copies of it from your computer
system.  Any use, dissemination, distribution, or reproduction of this
message by unintended recipients is not authorized and may be unlawful. The
contents of this communication do not necessarily represent the views of
this company.

Reply via email to