Re: problem with the extension / restriction base elements

[pierre betz]

still no ideas ? sorry to post again.. but I'm totally blocked now and can't
go on in my project because of that...


Thanks
Pierre

RE: MTOM Sample Error ?

[Şükrü Uzel]

File location is valid. I sure.

But I have this error.

I use Java 1.6

 

Bu I don't understand ?

 

  _  

From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 13, 2008 6:14 PM
To: axis-user@ws.apache.org
Subject: Re: MTOM Sample Error ?

 

Since you r getting a NPE, also check whether the file path you gave is
correct...

thanks,
Thilina

2008/8/13 Charitha Kankanamge <[EMAIL PROTECTED]>

Hi,

Which Axis2 version are you using?

regards
Charitha

Şükrü Uzel wrote:

I have error when mtom run client in axis2 sample ( MTOM ).

 
Error :

 
Exception in thread "main" org.apache.axis2.AxisFault

   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)

   at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:90)

   at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAx
isOperation.java:353)

   at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperatio
n.java:416)

   at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisO
peration.java:228)

   at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)

   at
org.apache.ws.axis2.mtomsample.MTOMSampleMTOMSampleSOAP11Port_httpStub.attac
hment(Unknown Source)

   at sample.mtom.client.Client.transferFile(Unknown Source)

   at sample.mtom.client.Client.main(Unknown Source)

Caused by: java.lang.NullPointerException

   at
org.apache.axiom.attachments.Attachments.getSOAPPartContentType(Attachments.
java:438)

   at
org.apache.axis2.builder.MIMEBuilder.processDocument(MIMEBuilder.java:40)

   at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUti
ls.java:164)

   at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:112)

   at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:88)

 
what is problem ?

 
 



Internal Virus Database is out-of-date.
Checked by AVG. Version: 7.5.524 / Virus Database: 270.4.7/1543 - Release
Date: 7/9/2008 6:32 PM
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Thilina Gunarathne - http://thilinag.blogspot.com

Re: Axis 2 backward compatibility

[Samisa Abeysinghe]

Cиземин Александр wrote:

 Hi!
 
 I've got a question about axis 1-2 compatibility.

 I'm trying to use web service, which provides rpc/encoded schema and probably 
works on axis 1.4.
 If I rebuild wsdl schema to document/literal and create client with axis2, 
will it be working with web service?
  


If you mean to say that you are going to change the schema expected by 
service, it should work.


Samisa...

 
 Thanks to all
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  



--
Samisa Abeysinghe

http://people.apache.org/~samisa/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Transport specification for web services

[Samisa Abeysinghe]

Kumar, Lokesh wrote:


Hi Martin,

Thanks for the response. I am aware that Axis2 supports multiple 
transport frameworks. My question is – can we deploy web services on 
the same Axis2 engine that communicate with client using different 
transport network. For example, say web service A communicates using 
default HTTP and web service B communicates using TCP and both these 
web services are deployed on the same server. Is this scenario possible ?




TCP and HTTP needs separate listeners. Now, if your server can handle 
both HTTP and TCP listeners simultaneously this could be done. But the 
usual norm is that, HTTP endpoint would be different form TCP endpoint. 
They should simply listen on different ports.


Samisa...

I was thinking if it was possible to specify in the services.xml file 
for each web service but I couldn’t locate any parameter that 
specifies that.


Regards,

-Lokesh



*From:* Martin Gainty [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, August 12, 2008 5:55 PM
*To:* axis-user@ws.apache.org
*Subject:* RE: Transport specification for web services

AXIS supports a number of different transports
If you want to implement AXIS via JMS take a look at IBM's JMS Tutorial
http://www.ibm.com/developerworks/webservices/library/ws-jms/

Anyone ?
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official 
business of Sender. This transmission is of a confidential nature and 
Sender does not endorse distribution to any party other than intended 
recipient. Sender does not necessarily endorse content contained 
within this transmission.




Subject: Transport specification for web services
Date: Tue, 12 Aug 2008 16:43:28 -0700
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org

Hi,

I need to specify transport specification for some web services. The 
default for the axis2 is HTTP and I want to keep it like that. But I 
do want some of my web services to connect to their client with TCP. 
Is it possible to specify transport mechanism different from other 
services on the same axis2 deployment.


Thanks & Regards,

-Lokesh



Get more from your digital life. Find out how. 






--
Samisa Abeysinghe

http://people.apache.org/~samisa/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: How to add a SOAP header in an axis2 custom client-side handler?

[Martin Gainty]

didn't see your config params
axis2.xml
?

services.xml
  

Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


Subject: How to add a SOAP header in an axis2 custom client-side handler?
Date: Wed, 13 Aug 2008 18:26:36 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
















I am trying to figure out how to add a SOAP header in my
client-side handler.

I have the following axis1 code, but need an axis2 equivalent:

 

   /***

* Processes the header of a request message.  This method
will add the 

* session header to the outgoing request.

* 

* @param context the message context associated with the
request

**/

   private void invokeRequest( MessageContext context ) throws
AxisFault

   { 

  Message msg = context.getRequestMessage();

  if (msg == null)

 throw new AxisFault( "Message not in
context." );



  SOAPEnvelope env = msg.getSOAPEnvelope();

 

  SessionHeaderType sessionHeader =
WebServiceClientHelper.getThreadSessionHeader( );

 

  SOAPHeaderElement header = new
SOAPHeaderElement(HEADER_NS,

   HEADER_NAME,

  
sessionHeader);

  env.addHeader(header);

   }

 

The SessionHeaderType class was generated from a wsdl and
contains session credentials.

 

Any pointers to appropriate documentation on how to manipulate
headers, or sample code, would be appreciated.







_
Your PC, mobile phone, and online services work together like never before.
http://clk.atdmt.com/MRT/go/108587394/direct/01/

How to add a SOAP header in an axis2 custom client-side handler?

[Franklin, Allen]

I am trying to figure out how to add a SOAP header in my client-side
handler.

I have the following axis1 code, but need an axis2 equivalent:

 

 
/***

* Processes the header of a request message.  This method will add
the 

* session header to the outgoing request.

* 

* @param context the message context associated with the request

 
**/

   private void invokeRequest( MessageContext context ) throws AxisFault

   { 

  Message msg = context.getRequestMessage();

  if (msg == null)

 throw new AxisFault( "Message not in context." );



  SOAPEnvelope env = msg.getSOAPEnvelope();

 

  SessionHeaderType sessionHeader =
WebServiceClientHelper.getThreadSessionHeader( );

 

  SOAPHeaderElement header = new SOAPHeaderElement(HEADER_NS,

   HEADER_NAME,

   sessionHeader);

  env.addHeader(header);

   }

 

The SessionHeaderType class was generated from a wsdl and contains
session credentials.

 

Any pointers to appropriate documentation on how to manipulate headers,
or sample code, would be appreciated.

RE: Transport specification for web services

[Kumar, Lokesh]

Hi Martin,

 

Thanks for the response. I am aware that Axis2 supports multiple
transport frameworks. My question is - can we deploy web services on the
same Axis2 engine that communicate with client using different transport
network. For example, say web service A communicates using default HTTP
and web service B communicates using TCP and both these web services are
deployed on the same server. Is this scenario possible ?

 

I was thinking if it was possible to specify in the services.xml file
for each web service but I couldn't locate any parameter that specifies
that.

 

Regards,

-Lokesh

 



From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 12, 2008 5:55 PM
To: axis-user@ws.apache.org
Subject: RE: Transport specification for web services

 

AXIS supports a number of different transports 
If you want to implement AXIS via JMS take a look at IBM's JMS Tutorial
http://www.ibm.com/developerworks/webservices/library/ws-jms/

Anyone ?
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 





Subject: Transport specification for web services
Date: Tue, 12 Aug 2008 16:43:28 -0700
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org

Hi,

 

I need to specify transport specification for some web services. The
default for the axis2 is HTTP and I want to keep it like that. But I do
want some of my web services to connect to their client with TCP. Is it
possible to specify transport mechanism different from other services on
the same axis2 deployment.

 

Thanks & Regards,

-Lokesh

 



Get more from your digital life. Find out how.

Re: How can I configure AXIS2 so that it does not ignore whitespace in element

[Eran Chinthaka]

Hi,

The element.getText() method trims all the whitespaces and I considered that
as a convenient method when I was implementing that.

If you want to get full information, call element.getChildren() and then the
returned list should contain an OMText which has all the information u need.

On Tue, Aug 12, 2008 at 9:01 AM, Deepak Vishwakarma
<[EMAIL PROTECTED]>wrote:

> I have no idea how to do that. If you can put some light on how to achieve
> it at the AXIOM level, that would be perfectly fine.
>
> Thanks,
> Deepak.
>
>
> --- On Tue, 12/8/08, Samisa Abeysinghe <[EMAIL PROTECTED]>
> wrote:
>
> > From: Samisa Abeysinghe <[EMAIL PROTECTED]>
> > Subject: Re: How can I configure AXIS2 so that it does not ignore
> whitespace in element
> > To: axis-user@ws.apache.org
> > Date: Tuesday, 12 August, 2008, 6:23 PM
>  > Could this be done at the AXIOM level, using an option?
> >
> > Samisa...
> >
> > Deepak Vishwakarma wrote:
> > > Hi,
> > >
> > >  I am trying to verify a signed SOAP request. But,
> > somehow the digest created for Soap Body doesn't match
> > the one present in the SOAP request for the SOAP Body. While
> > signing the ignorable whitespace characters are taken into
> > consideration. But, when the request is received at the
> > server it doesn't contain the ignorable whitespace
> > characters.
> > >
> > >  For example when the content of a MessageElement
> > containing text like
> > >  Value is accessed the
> > leading space is not returned.
> > >
> > >  It seems that Axis2 is automatically ignoring
> > whitespace characters present in the Body of the SOAP
> > Request.
> > >
> > >  Is there anyway to access the full content of the
> > element or to configure
> > > AXIS2 so that such whitespace values are always
> > returned in the element values?
> > >
> > > Thanks & Regards,
> > > Deepak.
> > >
> > >
> > >
> > >   Unlimited freedom, unlimited storage. Get it
> > now, on
> > http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/
> > >
> > >
> > -
> > > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> > >
> > >
> > >
> >
> >
> > --
> > Samisa Abeysinghe
> >
> > http://people.apache.org/~samisa/
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
>
>
>  Did you know? You can CHAT without downloading messenger. Go to
> http://in.webmessenger.yahoo.com/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
With Mettha,
Eran Chinthaka


Health is the greatest gift; contentment is the greatest wealth; trusting is
the best relationship; nirvana is the highest joy. - Dhammapada

Re: Adding header elements to a response

[David Ojeda]

I have managed to solve this using the toOM method in the MessageReceiverInOut 
generated by the wsdl.

On Wednesday 13 August 2008 03:59:42 pm David Ojeda wrote:
> I forgot to mention that I am using Axis 2 1.4
>
> On Wednesday 13 August 2008 03:56:38 pm David Ojeda wrote:
> > Hello all,
> >
> > I've never used the soap header in a WS client or server, but now I need
> > to add a simple true/false element to a soap response.
> > How can I do this?
> > I managed to declare this in the wsdl using soap:header, but there is
> > nothing in the Skeleton that lets me add a header element.
> >
> > Could you please help me?
> >
> > Here is my WSDL:
> >
> > 
> >  > name="WSIterautoID"
> > targetNamespace="http://www.openuri.org/ws/iterauto/WSIterautoID/";
> > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > xmlns:tns="http://www.openuri.org/ws/iterauto/WSIterautoID/";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> > xmlns:xsd1="http://www.openuri.org/ws/dummy";>
> > 
> >  > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > 
> > targetNamespace="http://www.openuri.org/ws/iterauto/WSIterautoID/";>
> > 
> > 
> > 
> >  > name="iterautoID"
> > type="xsd:string">
> > 
> > 
> > 
> > 
> > 
> > 
> >  > name="code"
> > type="xsd:string">
> > 
> >  > name="msg"
> > type="xsd:string">
> > 
> >  > name="trace"
> > type="xsd:string">
> > 
> >  > name="from"
> > type="xsd:string">
> > 
> > 
> > 
> >  > name="getIterautoIDFault"
> > type="tns:WSIterautoIDException">
> > 
> >
> >  > name="hasMoreElementsHeader"
> > type="xsd:boolean">
> > 
> > 
> > http://www.w3.org/2001/XMLSchema";>
> >  > namespace="http://www.openuri.org/ws/dummy";
> > schemaLocation="../xsd/DummyInput.xsd">
> > 
> > 
> >  > name="input" element="xsd1:EmptyRequest">
> > 
> > 
> >  > name="id" element="tns:getIterautoIDResponse">
> > 
> > 
> > 
> >  > name="fault" element="tns:getIterautoIDFault">
> > 
> > 
> > 
> >  > name="hasMoreElementsHeader" 
> > element="tns:hasMoreElementsHeader">
> > 
> > 
> > 
> > 
> >  > message="tns:getIterautoIDRequest">
> >  > message="tns:getIterautoIDResponse">
> >  > name="WSIterautoIDException"
> > message="tns:IterautoIDFault">
> > 
> > 
> > 
> >  > name="WSIterautoIDSOAP"
> > type="tns:WSIterautoID">
> >  > style="document"
> > transport="http://schemas.xmlsoap.org/soap/http"; />
> > 
> >  >
> > soapAction="http://www.openuri.org/ws/iterauto/WSIterautoID/getIterautoID
> >" /> 
> > 
> > 
> > 
> >  > part="hasMoreElementsHeader"
> > message="tns:hasMoreElementsHeader"/>
> > 
> > 
> > 
> >  > name="WSIterautoIDException"
> > use="literal"/>
> > 
> > 
> > 
> > 
> >  > name="WSIterautoID"
> >   

Re: Adding header elements to a response

[David Ojeda]

I forgot to mention that I am using Axis 2 1.4

On Wednesday 13 August 2008 03:56:38 pm David Ojeda wrote:
> Hello all,
>
> I've never used the soap header in a WS client or server, but now I need to
> add a simple true/false element to a soap response.
> How can I do this?
> I managed to declare this in the wsdl using soap:header, but there is
> nothing in the Skeleton that lets me add a header element.
>
> Could you please help me?
>
> Here is my WSDL:
>
> 
>name="WSIterautoID"
>   targetNamespace="http://www.openuri.org/ws/iterauto/WSIterautoID/";
>   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>   xmlns:tns="http://www.openuri.org/ws/iterauto/WSIterautoID/";
>   xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xsd1="http://www.openuri.org/ws/dummy";>
>   
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>   
> targetNamespace="http://www.openuri.org/ws/iterauto/WSIterautoID/";>
>   
>   
>   
>  name="iterautoID"
>   type="xsd:string">
>   
>   
>   
>   
>   
>   
>  name="code"
>   type="xsd:string">
>   
>  name="msg"
>   type="xsd:string">
>   
>  name="trace"
>   type="xsd:string">
>   
>  name="from"
>   type="xsd:string">
>   
>   
>   
>  name="getIterautoIDFault"
>   type="tns:WSIterautoIDException">
>   
>
>  name="hasMoreElementsHeader"
>   type="xsd:boolean">
>   
>   
>   http://www.w3.org/2001/XMLSchema";>
>  namespace="http://www.openuri.org/ws/dummy";
>   schemaLocation="../xsd/DummyInput.xsd">
>   
>   
>  name="input" element="xsd1:EmptyRequest">
>   
>   
>  name="id" element="tns:getIterautoIDResponse">
>   
>   
>   
>  name="fault" element="tns:getIterautoIDFault">
>   
>   
>   
>  name="hasMoreElementsHeader" 
> element="tns:hasMoreElementsHeader">
>   
>   
>   
>   
>message="tns:getIterautoIDRequest">
>message="tns:getIterautoIDResponse">
>  name="WSIterautoIDException"
>   message="tns:IterautoIDFault">
>   
>   
>   
>  name="WSIterautoIDSOAP"
>   type="tns:WSIterautoID">
>  style="document"
>   transport="http://schemas.xmlsoap.org/soap/http"; />
>   
>   
> soapAction="http://www.openuri.org/ws/iterauto/WSIterautoID/getIterautoID";
> /> 
>   
>   
>   
>part="hasMoreElementsHeader"
> message="tns:hasMoreElementsHeader"/>
>   
>   
>   
>  name="WSIterautoIDException"
>   use="literal"/>
>   
>   
>   
>   
>  name="WSIterautoID"
>   binding="tns:WSIterautoIDSOAP">
>  
> location="http://10.21.17.196:8080/WebServices/services/WSIterautoID";
> /> 
>   
> 



-- 
Ing. David Ojeda
Integra 

Adding header elements to a response

[David Ojeda]

Hello all,

I've never used the soap header in a WS client or server, but now I need to add 
a simple true/false element to a soap response.
How can I do this?
I managed to declare this in the wsdl using soap:header, but there is nothing 
in 
the Skeleton that lets me add a header element. 

Could you please help me?

Here is my WSDL:


http://www.openuri.org/ws/iterauto/WSIterautoID/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:tns="http://www.openuri.org/ws/iterauto/WSIterautoID/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
xmlns:xsd1="http://www.openuri.org/ws/dummy";>

http://www.w3.org/2001/XMLSchema";

targetNamespace="http://www.openuri.org/ws/iterauto/WSIterautoID/";>


























http://www.w3.org/2001/XMLSchema";>
http://www.openuri.org/ws/dummy";
schemaLocation="../xsd/DummyInput.xsd">

























http://schemas.xmlsoap.org/soap/http"; />

http://www.openuri.org/ws/iterauto/WSIterautoID/getIterautoID"; />














http://10.21.17.196:8080/WebServices/services/WSIterautoID"; />





-- 
Ing. David Ojeda
Integra Consultores
Caracas, Venezuela

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Client handler tutorial

[Franklin, Allen]

Below is a summary of configuring Axis2 for a client-side handler.

I haven't actually tried it yet, so please let me know if something is
wrong.

 

 

Summary of configuring an axis2 v1.4 SOAP client for a custom
client-side handler.

This handler can, for example, add username, password and session id to
the SOAP header:

 

1) Build a jar file with a .mar extension on the classpath/repository
that contains:

   module.xml -contains a) module name, b) name of class that implements
Module and c) name of class that extends AbstractHandler.

   Class that implements org.apache.axis2.modules.Module.

   class that extends AbstractHandler (the real work of your handler
goes here). 

 

2) axis2.xml -edit to include your new phase, also add a reference to
your module: http://ws.apache.org/axis2/1_2/modules.html. Note that this link address
server-side handlers.

 

3) services.xml -reference the module that contains the handler chain.
Not needed for a client-side handler?

 

4) Choose a method for passing the configuration to the axis2 engine,
either programatically via ConfigurationContext,

   or passing -D JVM parameters (-Daxis2.repo=C:\Axis2\repository,
-Daxis2.xml=C:\Axis2\conf\axis2.xml).

   See http://wso2.org/library/585 for programatic configuration.

 

From: Wally Dennis [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 13, 2008 11:08 AM
To: axis-user@ws.apache.org
Subject: Re: Client handler tutorial

 


One way to specify the conf and repo for stand-alone clients is to use
-D JVM parameters as shown here: 

-Daxis2.repo=C:\Axis2\repository 
-Daxis2.xml=C:\Axis2\conf\axis2.xml 

Wally 





"Detelin Yordanov" <[EMAIL PROTECTED]> 

08/13/2008 10:26 AM 

Please respond to
axis-user@ws.apache.org

To

axis-user@ws.apache.org 

cc


Subject

Re: Client handler tutorial

 






Hi,
  When using Axis2 client (e.g. ServiceClient) you do not need any
servlet container, it just uses Apache HttpClient to
send and receive the request (if using HTTP). Underneath the
ServiceClient will setup normal Axis2 runtime (as the one on server
side) to process messages.
The ServiceClient has constructors to specify an Axis2
ConfigurationContext which points to the "client-side" Axis2
configuration file, 
if no ConfigurationContext is given it will use (I think) a default
axis2.xml from the Axis2 kernel jar.

So if you need to define any handlers or whatsoever, you can create
your axis2-conf for the client side, add your handlers, then create a
ConfigurationContext and finally a ServiceClient.

Regards,
   Detelin

On Wed, Aug 13, 2008 at 4:19 PM, Franklin, Allen
<[EMAIL PROTECTED]> wrote: 
Where I work we start with a hand-built wsdl and then run WSDL2Java to
generate the client and server stubs and skeleton code. 

When I say 'client side handler' I am talking about a class that that
implements AbstractHandler that (I think) I need to write 

to add a username, password and session id to the SOAP header. 

  

I'm still having trouble understanding if I need to deploy a servlet
container (eg Tomcat) just to run an axis2 client? 

  

From: Martin Gainty [mailto:[EMAIL PROTECTED]
 ] 
Sent: Wednesday, August 13, 2008 9:00 AM 


To: axis-user@ws.apache.org  
Subject: RE: Client handler tutorial 

  

typical scenario is 
with the typical HTTP transport scenario you would build the server
classes and deploy using the admin tool
then use compiled WSDL2Java generated client stub to test

I guess I would need to know which 'client side handler' you are
referring to for specifics..
JMS/SMTP/Other 
?
Martin
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 



Subject: RE: Client handler tutorial
Date: Wed, 13 Aug 2008 08:53:17 -0400
From: [EMAIL PROTECTED]  
To: axis-user@ws.apache.org   

Do I need to deploy my axis2 client into a servlet container to be able
to use client-side handlers? 

Currently my client does not need a servlet container, it runs
stand-alone. 

  

From: Martin Gainty [mailto:[EMAIL PROTECTED]
 ] 
Sent: Tuesday, August 12, 2008 6:46 PM
To: axis-user@ws.apache.org  
Subject: RE: Client handler tutorial 

  

yuo can deploy the client mar from the admin utility try
http://localhost:8080/axis2/axis2-admin/
 

HTH
Martin
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmis

AxisServlet parameter order mismatch

[don t]

Hi, I am calling an Axis 1.4 service through the browser with 4 URL
parameters like this:

http://localhost:8012/axis/services/LocationService?method=getLocationsByCoordinates®ion=Hawaii&delta=2&latitude=20&longitude=-160


The operation and parameters are defined in Document/Literal Wrapped style
WSDL like this:

















>From above HTTP request Axis generates a request SOAP envelope like this:

http://schemas.xmlsoap.org/soap/envelope/";>


Hawaii
-156
1
20





However looking at the logs seems the parameter ordering was changed when
invoking service:

region = Hawaii
latitude = -156.0
longitude = 20.0
delta = 1.0


After some debugging it seems the problem is in Axis RPCHandler.java

http://svn.apache.org/viewvc/webservices/axis/trunk/java/src/org/apache/axis/message/RPCHandler.java?view=markup

The parameter descriptor lookup by QName returns null:

// Try by name first
if (isResponse) {
paramDesc = operation.getOutputParamByQName(qname);
} else {
paramDesc = operation.getInputParamByQName(qname);
}

so Axis then tries to lookup parameter descriptor by position: 

// If that didn't work, try position
// FIXME : Do we need to be in EITHER named OR positional
// mode?  I.e. will it screw us up to find something
// by position if we've already looked something up
// by name?  I think so...
if (paramDesc == null) {
if (isResponse) {
paramDesc = operation.getReturnParamDesc();
}
else {
paramDesc =
operation.getParameter(rpcElem.getParams().size() - 1);
}
}

The problem is lookup by position results in botched parameter ordering when
invoking the service. My question is how can I specify operation parameters
in WSDL or WSDD such that the parameter QName lookup will not return null,
or parameter position ordering is preserved when inovked through
AxisServlet?
-- 
View this message in context: 
http://www.nabble.com/AxisServlet-parameter-order-mismatch-tp18967041p18967041.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: MTOM Sample Error ?

[Thilina Gunarathne]

Since you r getting a NPE, also check whether the file path you gave is
correct...

thanks,
Thilina

2008/8/13 Charitha Kankanamge <[EMAIL PROTECTED]>

> Hi,
>
> Which Axis2 version are you using?
>
> regards
> Charitha
>
> Şükrü Uzel wrote:
>
>  I have error when mtom run client in axis2 sample ( MTOM ).
>>
>>
>> Error :
>>
>>
>> Exception in thread "main" org.apache.axis2.AxisFault
>>
>>at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>>
>>at
>> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:90)
>>
>>at
>> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
>>
>>at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
>>
>>at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
>>
>>at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
>>
>>at
>> org.apache.ws.axis2.mtomsample.MTOMSampleMTOMSampleSOAP11Port_httpStub.attachment(Unknown
>> Source)
>>
>>at sample.mtom.client.Client.transferFile(Unknown Source)
>>
>>at sample.mtom.client.Client.main(Unknown Source)
>>
>> Caused by: java.lang.NullPointerException
>>
>>at
>> org.apache.axiom.attachments.Attachments.getSOAPPartContentType(Attachments.java:438)
>>
>>at
>> org.apache.axis2.builder.MIMEBuilder.processDocument(MIMEBuilder.java:40)
>>
>>at
>> org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:164)
>>
>>at
>> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
>>
>>at
>> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
>>
>>
>> what is problem ?
>>
>>
>>
>> 
>>
>> Internal Virus Database is out-of-date.
>> Checked by AVG. Version: 7.5.524 / Virus Database: 270.4.7/1543 - Release
>> Date: 7/9/2008 6:32 PM
>>
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Thilina Gunarathne - http://thilinag.blogspot.com

Re: mtom file size

[Thilina Gunarathne]

hmm... I don't know why they are providing it only for form posts...  May be
tomcat does not track the size of others..

I'm sorry.. I don't have any ideas...

~Thilina

On Tue, Aug 12, 2008 at 9:58 PM, Shehan Simen <[EMAIL PROTECTED]> wrote:

>  Hi Thilina,
>
> The maxPostSize attribute is working in tomcat only for the Post requests
> coming via the Forms.
>
> I searched a lot in google to try to find a solution. But seems no
> solution.
>
>
>
> Thanks.
>
>
>
> Regards,
>
> Simen
>
>
>
> *From:* Thilina Gunarathne [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, 13 August 2008 2:46 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: mtom file size
>
>
>
> Hi,
>
>  There is a similar parameter setting in the tomcat service.xml as
> maxPostSize="" , this will restrict the size of incoming POST
> request. But this does not work for axis web service requests, but that
> configuration is quite easier and no need to waste time on clustering and
> stuff.
>
>  Restricting the message size using the app server (eg: tomcat) would be
> the approach most of the users might be using... I'm surprised to hear that
> Tomcat does not restrict the incoming POST request size for Axis2 web
> service requests.. For tomcat, it would be just another request..  Does this
> happen only with a particular scenerio (eg: with http chunking? ).
>
> thanks,
> Thilina
>
>
>
> Hope in future, we will be able to get such configurable solution.
>
>
>
> Thank you.
>
> Regards,
>
> Simen
>
>
>
> *From:* Martin Gainty [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, 13 August 2008 12:03 PM
>
>
> *To:* axis-user@ws.apache.org
>
> *Subject:* RE: mtom file size
>
>
>
> your SOAP response can be a URL to the file ..and hand the URL to FTP
> server for bulk of the heavy lifting
> another idea is to compress the file which will conserve bandwidth
>
> the question is which server has the necessary bandwidth to handle the
> transmission?
> if you're bogging down your webapp server you might want consider
> clustering
> http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html
>
> Most prod servers run with 4GB RAM
> so you'll want to increment your stack and heap params to accomodate more
> RAM
>
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/index.jsp?topic=/com.ibm.java.doc.diagnostics.60/diag/appendixes/defaults.html
>
> heavy resource-intensive operations should be handled by threads to prevent
> bogging down the JVM proc
>
> you may also want to consider Chunked-encoding ..
>
> Anyone else?
> Martin
> __
> Disclaimer and confidentiality note
> Everything in this e-mail and any attachments relates to the official
> business of Sender. This transmission is of a confidential nature and Sender
> does not endorse distribution to any party other than intended recipient.
> Sender does not necessarily endorse content contained within this
> transmission.
>  --
>
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Date: Wed, 13 Aug 2008 09:12:40 +1000
> Subject: RE: mtom file size
>
> Hi Thilina,
>
> It is a big threat to the web service. L
>
> I don't want to crash my web server by receiving large files.
>
> We cannot request from the clients to send small files and people are
> always willing to blame us by crashing the web server.
>
> There may be some settings in the tomcat configurations to limit the size
> of incoming request. Any suggestions?
>
>
>
> Thank you.
>
>
>
> Regards,
>
> simen
>
>
>
> *From:* Thilina Gunarathne [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, 13 August 2008 1:35 AM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: mtom file size
>
>
>
> I would say it's possible..
>
> thanks,
> Thilina
>
> On Tue, Aug 12, 2008 at 6:01 AM, Samisa Abeysinghe <
> [EMAIL PROTECTED]> wrote:
>
> Thilina Gunarathne wrote:
>
> I'm not sure whether Axis2 MTOM policy implementation supports such a
> scenerio.. Other than that, I cannot think of any..
>
>
>
> Does this mean that someone can send several large attachments concurrently
> and take down the server by making it go out of resources?
>
> Thanks,
> Samisa...
>
>
> thanks,
> Thilina
>
>
>
> On Mon, Aug 11, 2008 at 5:38 PM, Shehan Simen <[EMAIL PROTECTED] [EMAIL PROTECTED]>> wrote:
>
>Hi,
>
>I want to specify the maximum file size when using MTOM.
>
>The client should not send to the service files bigger than 5mb
>and I am using MTOM with axis2 1.4 (deployed in tomcat)
>
>How to restrict the file size?
>
>
>Please let me know.
>
>
>Thanks.
>
>
>
>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>
>
>
> --
> Samisa Abeysinghe
>
> http://people.apache.org/~samisa/ 
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>
>
>  --

Re: Client handler tutorial

[Wally Dennis]

One way to specify the conf and repo for stand-alone clients is to use -D 
JVM parameters as shown here:

-Daxis2.repo=C:\Axis2\repository 
-Daxis2.xml=C:\Axis2\conf\axis2.xml

Wally





"Detelin Yordanov" <[EMAIL PROTECTED]> 

08/13/2008 10:26 AM
Please respond to
axis-user@ws.apache.org



To
axis-user@ws.apache.org
cc

Subject
Re: Client handler tutorial






Hi,
   When using Axis2 client (e.g. ServiceClient) you do not need any 
servlet container, it just uses Apache HttpClient to
send and receive the request (if using HTTP). Underneath the ServiceClient 
will setup normal Axis2 runtime (as the one on server side) to process 
messages.
The ServiceClient has constructors to specify an Axis2 
ConfigurationContext which points to the "client-side" Axis2 configuration 
file, 
if no ConfigurationContext is given it will use (I think) a default 
axis2.xml from the Axis2 kernel jar.

So if you need to define any handlers or whatsoever, you can create  your 
axis2-conf for the client side, add your handlers, then create a 
ConfigurationContext and finally a ServiceClient.

Regards,
Detelin

On Wed, Aug 13, 2008 at 4:19 PM, Franklin, Allen <
[EMAIL PROTECTED]> wrote:
Where I work we start with a hand-built wsdl and then run WSDL2Java to 
generate the client and server stubs and skeleton code.
When I say 'client side handler' I am talking about a class that that 
implements AbstractHandler that (I think) I need to write 
to add a username, password and session id to the SOAP header.
 
I'm still having trouble understanding if I need to deploy a servlet 
container (eg Tomcat) just to run an axis2 client?
 
From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 13, 2008 9:00 AM

To: axis-user@ws.apache.org
Subject: RE: Client handler tutorial
 
typical scenario is 
with the typical HTTP transport scenario you would build the server 
classes and deploy using the admin tool
then use compiled WSDL2Java generated client stub to test

I guess I would need to know which 'client side handler' you are referring 
to for specifics..
JMS/SMTP/Other 
?
Martin
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official 
business of Sender. This transmission is of a confidential nature and 
Sender does not endorse distribution to any party other than intended 
recipient. Sender does not necessarily endorse content contained within 
this transmission. 


Subject: RE: Client handler tutorial
Date: Wed, 13 Aug 2008 08:53:17 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Do I need to deploy my axis2 client into a servlet container to be able to 
use client-side handlers?
Currently my client does not need a servlet container, it runs 
stand-alone.
 
From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 12, 2008 6:46 PM
To: axis-user@ws.apache.org
Subject: RE: Client handler tutorial
 
yuo can deploy the client mar from the admin utility try
http://localhost:8080/axis2/axis2-admin/

HTH
Martin
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official 
business of Sender. This transmission is of a confidential nature and 
Sender does not endorse distribution to any party other than intended 
recipient. Sender does not necessarily endorse content contained within 
this transmission. 

Subject: Re: Client handler tutorial
Date: Tue, 12 Aug 2008 18:34:04 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
I am having trouble figuring out how to add client-side handlers in axis2.
I see the email reply, below, that there is no difference between client 
and server side.
But the configuration must be different since on the client side there is 
no web container to put the axis2.xml configuration information for the 
handler and also no place to put the .mar file. 
Client-side handler configuration remains a mystery to me.
Re: Client handler tutorial
Deepal Jayasinghe
Wed, 16 Apr 2008 22:57:25 -0700
Hi Chau,
Are you referring to Axis2 ?
if so there is no difference between client side and server side.
 
Thank you!
Deepal
Anybody knows the link to client handler tutorial? Thanks 
 

 
 

Reveal your inner athlete and share it with friends on Windows Live. Share 
now!
 

Your PC, mobile phone, and online services work together like never 
before. See how Windows® fits your life





The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this messag

RE: Please help - Embedded web service

[Marc.Horvath]

At
http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAx
isToYourOwnWebapp

 

Item 4 states: Run the Axis AdminClient against your own webapp, instead
of Axis, by changing the URL you invoke it with.

 

One thing that confuses me is how this url compares to the one used with
the -l option of the Java2Wsdl command.

Modifying the example you sent me to represent embedded Axis, would the
Java2Wsdl -l look like this:
http://localhost:8080/MyWebApp/services/WidgetPrice

and then what would the AdminClient command look like,
http://localhost:8080/MyWebApp/services or
http://localhost:8080/MyWebApp ? I tried both and got errors both times
such as: "bad envelope exception: html" 

 

Marc

 

 



From: Horvath, Marc [CLIMATE/RS/ATL] 
Sent: Wednesday, August 13, 2008 10:30 AM
To: 'Martin Gainty'
Subject: RE: Please help - Embedded web service

 

Maritn,

 

Thanks for the response. I'll look into those tutorials.

However, at first glance it looks like your examples are based on Axis
running seperately from a web app and I have already got that to work
without a problem

What I need is to have Axis embedded in my web app. The urls you
provided, http://localhost:8080/axis/services, indicate axis is running
indpendently. I want to deploy Axis and my web services bundled/embedded
in another web app. I've managed to embedd axis ok but am having
problems with the web services. That's why I asked for a detailed
example of deploying a web service with axis embedd in a web app.

 

Thanks again,

Marc

 

 



From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 12, 2008 6:17 PM
To: Horvath, Marc [CLIMATE/RS/ATL]
Subject: RE: Please help - Embedded web service

 

Hey Marc-
in other words take this project offline in a controlled environment ..I
hope you have a home office!!!

a good WSDL2Java tutorial is located at
http://ws.apache.org/axis/java/user-guide.html#WSDL2JavaBuildingStubsSke
letonsAndDataTypesFromWSDL
where the command to produce the required classes would be 
java org.apache.axis.wsdl.WSDL2Java (WSDL-file-URL)
which will produce

*   WidgetPriceSoapBindingImpl.java : Java file containing the
default server implementation of the WidgetPrice web service.
You will need to modify the *SoapBindingImpl file to add your
implementation (see
samples/userguide/example6/WidgetPriceSoapBindingImpl.java
 ). 
*   WidgetPrice.java: New interface file that contains the
appropriate java.rmi.Remote usages. 
*   WidgetPriceService.java: Java file containing the client side
service interface. 
*   WidgetPriceServiceLocator.java: Java file containing the client
side service implementation class. 
*   WidgetPriceSoapBindingSkeleton.java: Server side skeleton. 
*   WidgetPriceSoapBindingStub.java: Client side stub. 
*   deploy.wsdd: Deployment descriptor 
*   undeploy.wsdd: Undeployment descriptor 
build.xml (script to run) 

Notice the build.xml  contains this generate.service client


Notice the build.xml contains generate.client target

now run the ant generate.service to compile the service classes
and produce the required war or aar

now run ant generate.client to compile the client stub

Java2WSDL tutorial is located at
http://ws.apache.org/axis/java/user-guide.html#Java2WSDLBuildingWSDLFrom
Java

*   -o indicates the name of the output WSDL file 
*   -l indicates thelocation of the service 
*   -n is the target namespace of the WSDL file 
*   -p indicates a mapping from the package to a namespace. There
may be multiple mappings. 
*   the class specified contains the interface of the webservice. 

java org.apache.axis.wsdl.Java2WSDL -o wp.wsdl
-l"http://localhost:8080/axis/services/WidgetPrice";
-n "urn:Example6" -p"samples.userguide.example6" "urn:Example6"
samples.userguide.example6.WidgetPrice AdminClient is invoked by
deploying the Server's deployment descriptor as in this example using
the previously
generated deploy.wsdd

java org.apache.axis.client.AdminClient deploy.wsdd

Done processing

now run the client app ..
java samples.userguide.example3.Client
-lhttp://localhost:8080/axis/services/MyService "test me!" 

we are here to help you thru this..
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 



Subject: Please help - Embedded web service
Date: Tue, 12 Aug 2008 14:55:57 -0500
Fr

Re: spring Axis2 integration question

[Detelin Yordanov]

Hi,
   I'm also currently reading this tutorial and could shed some light on it,
at least my understanding so far.
The basic idea as it seems to me is to be able to access Spring beans
(defined within Spring's application context) from
normal Axis2 services.
The actual injection of the bean seems to be done by Axis2, e.g. if having
an Axis2 service that has a "myBean" field,
when its messsage receiver is invoked, Axis2 will populate that field with
the configured Spring bean by loading it from the Spring
application context.
The name of the Spring bean to inject is defined using the "SpringBeanName"
Axis2 parameter in Axis2 services.xml file.
The class that is responsible for looking up this Spring bean needs to be
able to access the Spring configuration context in some way.

If the Spring and Axis2 are running on a servlet container, this can be done
using the servlet context that is also kept in the Axis2
runtime. The following is a standart Spring code to retrieve the Spring
application context from a ServletContext:

ApplicationContext aCtx =
WebApplicationContextUtils.getWebApplicationContext(servletContext);

So if you know that both Spring and Axis2 reside on the same servlet
container, you should specify the following in the services.xml:

org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier


That way you tell Axis2 "try to obtain the Spring application context from
the ServletContext, I know it is there".

If you run Spring and Axis2 standalone without a servlet container, then
Axis2 cannot use this approach, so you need to define a bean
in Spring that will take hold of the Spring's application context:



 This bean just has a static field for the Application context. Spring will
populate the static field and later Axis2 will just be able to call the
static "getContext()" method to retrieve context and from there the desired
bean to inject.

In this case you need to define the following in the Axis2 services.xml:

org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier

This will tell Axis: "ApplicationContextHolder class is initialized by
Spring and contains a reference to Spring's context, get it from there"

Regards,
   Detelin

On Tue, Aug 12, 2008 at 9:24 PM, robert lazarski
<[EMAIL PROTECTED]>wrote:

> Also, use the "with a ServletContext" options for use with WEB-INF/lib .
>
> - R
>
> On Tue, Aug 12, 2008 at 3:23 PM, robert lazarski
> <[EMAIL PROTECTED]> wrote:
> > Putting all jars in WEB-INF/lib is easiest and recommended in most cases.
> >
> > - R
> >
> > On Tue, Aug 12, 2008 at 2:21 PM, scabbage <[EMAIL PROTECTED]> wrote:
> >>
> >> I've been struggling to understand how spring and Axis2 will work
> together. I
> >> have read the tutorial at http://ws.apache.org/axis2/1_4/spring.html#21.
> But
> >> still couldn't understand what it's talking about. As I'm new to
> webservice
> >> and Axis2, I hope you could kindly provide some pointers so that could
> use
> >> my Spring services in Axis2.
> >>
> >> So basically I have a standard hibernate+dao+Spring app packaged as a
> jar
> >> file. The tutorial was unclear about where I should put this jar file.
> It
> >> should be one of services, pojo or modules, am I right? As this is not a
> >> simple pojo, I assume I should put it in one of the other two folders.
> And
> >> then the tutorial goes ahead talking about "with/without a
> ServletContext",
> >> which I'm a bit lost. What does it mean by "with a ServletContext"?
> >>
> >> Can someone please explain how I could deploy this jar in Axis2?
> >>
> >> Thanks.
> >> --
> >> View this message in context:
> http://www.nabble.com/spring-Axis2-integration-question-tp18948823p18948823.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Trying to access .NET based Web Service from Java based Web Service client failed.

[Takashi Saruhashi]

Hello all, My name is Takashi

I faced some problem with communication between .NET based Web Service
and Java based Web Service Client.
My current environment is


OS: Windows XP Pro
Web Server: IIS v5.1
(Also ASP.NET server is working on Port 2526)
Java: jdk1.5.0_15
Axis2: axis2-1.14


I created simple Web Service like this in Visual Studio.

---
using System;
using System.Collections;
using System.ComponentModel;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Services;
using System.Web.Services.Protocols;
using System.Xml.Linq;

namespace WebService2
{
/// 
/// Summary description for Service1
/// 
[WebService(Namespace = "http://tempuri.org/";)]
[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
[ToolboxItem(false)]
// To allow this Web Service to be called from script, using ASP.NET
AJAX, uncomment the following line. 
// [System.Web.Script.Services.ScriptService]
public class Service1 : System.Web.Services.WebService
{

[WebMethod]
public string HelloWorld(string input)
{

return "Hello World " + input;
}
}
}
---

Then I tried to create Web Service Stub using axis2 toolkil wsdl2java.
After creating the stub, then I tried to access the service above, Then
I got this error.

---
Exception in thread "main" org.apache.axis2.AxisFault: The input stream
for an incoming message is null.
---

I also did SOAP monitoring. That shows

--- input ---
POST /Service1.asmx HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8;
action="http://tempuri.org/HelloWorld";
User-Agent: Axis2
Host: 127.0.0.1:
Transfer-Encoding: chunked

ff
http://www.w3.org/2003/05/soap-envelope";>http://tempuri.org/";>takashi

0
-

--- output ---
HTTP/1.1 400 Bad Request
Server: ASP.NET Development Server/9.0.0.0
Date: Wed, 13 Aug 2008 14:36:04 GMT
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Length: 0
Connection: Close
--

The output says it is bad request. 
Could anyone tell me how to handle this problem??


Best regards.
Takashi

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Client handler tutorial

[Detelin Yordanov]

Hi,
   When using Axis2 client (e.g. ServiceClient) you do not need any servlet
container, it just uses Apache HttpClient to
send and receive the request (if using HTTP). Underneath the ServiceClient
will setup normal Axis2 runtime (as the one on server side) to process
messages.
The ServiceClient has constructors to specify an Axis2 ConfigurationContext
which points to the "client-side" Axis2 configuration file,
if no ConfigurationContext is given it will use (I think) a default
axis2.xml from the Axis2 kernel jar.

So if you need to define any handlers or whatsoever, you can create  your
axis2-conf for the client side, add your handlers, then create a
ConfigurationContext and finally a ServiceClient.

Regards,
Detelin

On Wed, Aug 13, 2008 at 4:19 PM, Franklin, Allen <[EMAIL PROTECTED]
> wrote:

>  Where I work we start with a hand-built wsdl and then run WSDL2Java to
> generate the client and server stubs and skeleton code.
>
> When I say 'client side handler' I am talking about a class that that
> implements AbstractHandler that (I think) I need to write
>
> to add a username, password and session id to the SOAP header.
>
>
>
> I'm still having trouble understanding if I need to deploy a servlet
> container (eg Tomcat) just to run an axis2 client?
>
>
>
> *From:* Martin Gainty [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, August 13, 2008 9:00 AM
>
> *To:* axis-user@ws.apache.org
> *Subject:* RE: Client handler tutorial
>
>
>
> typical scenario is
> with the typical HTTP transport scenario you would build the server classes
> and deploy using the admin tool
> then use compiled WSDL2Java generated client stub to test
>
> I guess I would need to know which 'client side handler' you are referring
> to for specifics..
> JMS/SMTP/Other
> ?
> Martin
> __
> Disclaimer and confidentiality note
> Everything in this e-mail and any attachments relates to the official
> business of Sender. This transmission is of a confidential nature and Sender
> does not endorse distribution to any party other than intended recipient.
> Sender does not necessarily endorse content contained within this
> transmission.
>
>  --
>
> Subject: RE: Client handler tutorial
> Date: Wed, 13 Aug 2008 08:53:17 -0400
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
>
> Do I need to deploy my axis2 client into a servlet container to be able to
> use client-side handlers?
>
> Currently my client does not need a servlet container, it runs stand-alone.
>
>
>
> *From:* Martin Gainty [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, August 12, 2008 6:46 PM
> *To:* axis-user@ws.apache.org
> *Subject:* RE: Client handler tutorial
>
>
>
> yuo can deploy the client mar from the admin utility try
> http://localhost:8080/axis2/axis2-admin/
>
> HTH
> Martin
> __
> Disclaimer and confidentiality note
> Everything in this e-mail and any attachments relates to the official
> business of Sender. This transmission is of a confidential nature and Sender
> does not endorse distribution to any party other than intended recipient.
> Sender does not necessarily endorse content contained within this
> transmission.
>  --
>
> Subject: Re: Client handler tutorial
> Date: Tue, 12 Aug 2008 18:34:04 -0400
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
>
> I am having trouble figuring out how to add client-side handlers in axis2.
>
> I see the email reply, below, that there is no difference between client
> and server side.
>
> But the configuration must be different since on the client side there is
> no web container to put the axis2.xml configuration information for the
> handler and also no place to put the .mar file.
>
> Client-side handler configuration remains a mystery to me.
>
> *Re: Client handler tutorial*
>
> Deepal Jayasinghe
> Wed, 16 Apr 2008 22:57:25 -0700
>
> Hi Chau,
>
> Are you referring to Axis2 ?
>
> if so there is no difference between client side and server side.
>
>
>
> Thank you!
>
> Deepal
>
> Anybody knows the link to client handler tutorial? Thanks
>
>
>
> 
>
>
>
>
>  --
>
> Reveal your inner athlete and share it with friends on Windows Live. Share
> now!
>
>
>  --
>
> Your PC, mobile phone, and online services work together like never before.
> See how Windows(R) fits your 
> life
>

Re: Axis2 array wrappers

[Detelin Yordanov]

Hi,
  Afaik .Net web services do this array wrapping, unfortunately Axis2 does
not work that way.
However, if changing the code is not a problem you can try creating a custom
class "ArrayOfPhones" that contains a Phone[] field and use that instead.

Regards,
   Detelin

On Tue, Aug 12, 2008 at 10:16 PM, Dan Leahu <[EMAIL PROTECTED]> wrote:

> Hi,
>
>   I've an axis2 web service that has the following structure:
>
>  1. name
>  2. surname
>  3. Phone[] phone
>
>   The problem here is that when I want to see a response from this service
> it always gives me something like this:
>
> 
> 
> 
> 100
> 0421
> 
> 
> 200
> 1234
> 
> xaas
> xa1
> 
> 
>
>
> The problem with this is when I want to use this service from a VBA client.
> The code on the VBA side is generated correctly but when I run it it always
> takes only the first element in the array of Phone. I've tried with another
> web service(
> http://euro2008.dataaccess.eu/footballpoolwebservice.wso/AllGames) and
> this one works correctly since the response is like this:
>
> 
>   
>   1
>   Round 1
>   2008-06-07
>   18:00:00
>   
> 
>
> 
>   
>   
>   
>   1
>   Round 1
>   2008-06-07
>   18:00:00
>   
> 
>
> The idea is that somehow the guys that written the euro2008 web services,
> managed to return the arrays having a parent element, e.g. ArrayOfGamesInfo,
> Cards.
>
> Any idea how could I make Axis2 return arrays in this way - having a parent
> element that wraps them?
>
> Thanks a lot,
>
>   Dan.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

RE: Client handler tutorial

[Franklin, Allen]

Where I work we start with a hand-built wsdl and then run WSDL2Java to
generate the client and server stubs and skeleton code.

When I say 'client side handler' I am talking about a class that that
implements AbstractHandler that (I think) I need to write 

to add a username, password and session id to the SOAP header.

 

I'm still having trouble understanding if I need to deploy a servlet
container (eg Tomcat) just to run an axis2 client?

 

From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 13, 2008 9:00 AM
To: axis-user@ws.apache.org
Subject: RE: Client handler tutorial

 

typical scenario is 
with the typical HTTP transport scenario you would build the server
classes and deploy using the admin tool
then use compiled WSDL2Java generated client stub to test

I guess I would need to know which 'client side handler' you are
referring to for specifics..
JMS/SMTP/Other 
?
Martin
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 





Subject: RE: Client handler tutorial
Date: Wed, 13 Aug 2008 08:53:17 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org

Do I need to deploy my axis2 client into a servlet container to be able
to use client-side handlers?

Currently my client does not need a servlet container, it runs
stand-alone.

 

From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 12, 2008 6:46 PM
To: axis-user@ws.apache.org
Subject: RE: Client handler tutorial

 

yuo can deploy the client mar from the admin utility try
http://localhost:8080/axis2/axis2-admin/

HTH
Martin
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 



Subject: Re: Client handler tutorial
Date: Tue, 12 Aug 2008 18:34:04 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org

I am having trouble figuring out how to add client-side handlers in
axis2.

I see the email reply, below, that there is no difference between client
and server side.

But the configuration must be different since on the client side there
is no web container to put the axis2.xml configuration information for
the handler and also no place to put the .mar file. 

Client-side handler configuration remains a mystery to me.

Re: Client handler tutorial

Deepal Jayasinghe
Wed, 16 Apr 2008 22:57:25 -0700

Hi Chau,

Are you referring to Axis2 ?

if so there is no difference between client side and server side.

 

Thank you!

Deepal

Anybody knows the link to client handler tutorial? Thanks 

 



 

 



Reveal your inner athlete and share it with friends on Windows Live.
Share now!
 

 



Your PC, mobile phone, and online services work together like never
before. See how Windows(r) fits your life
 

Axis 2 backward compatibility

[Cиземин Александр]

 Hi!
 
 I've got a question about axis 1-2 compatibility.
 I'm trying to use web service, which provides rpc/encoded schema and probably 
works on axis 1.4.
 If I rebuild wsdl schema to document/literal and create client with axis2, 
will it be working with web service?
 
 Thanks to all
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Client handler tutorial

[Martin Gainty]

typical scenario is 
with the typical HTTP transport scenario you would build the server classes and 
deploy using the admin tool
then use compiled WSDL2Java generated client stub to test

I guess I would need to know which 'client side handler' you are referring to 
for specifics..
JMS/SMTP/Other 
?
Martin
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


Subject: RE: Client handler tutorial
Date: Wed, 13 Aug 2008 08:53:17 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org



















Do I need to deploy my axis2 client into a servlet container to
be able to use client-side handlers?

Currently my client does not need a servlet container, it runs
stand-alone.

 





From: Martin Gainty
[mailto:[EMAIL PROTECTED] 

Sent: Tuesday, August 12, 2008 6:46 PM

To: axis-user@ws.apache.org

Subject: RE: Client handler tutorial





 

yuo can deploy the client mar from the admin
utility try

http://localhost:8080/axis2/axis2-admin/



HTH

Martin

__ 

Disclaimer and confidentiality note 

Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission is of a confidential nature and Sender does not
endorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission. 











Subject: Re: Client handler tutorial

Date: Tue, 12 Aug 2008 18:34:04 -0400

From: [EMAIL PROTECTED]

To: axis-user@ws.apache.org



I
am having trouble figuring out how to add client-side handlers in axis2.

I
see the email reply, below, that there is no difference between client and
server side.

But
the configuration must be different since on the client side there is no web
container to put the axis2.xml configuration information for the handler and
also no place to put the .mar file. 

Client-side
handler configuration remains a mystery to me.

Re: Client handler
tutorial

Deepal Jayasinghe

Wed, 16 Apr 2008 22:57:25 -0700

Hi
Chau,

Are
you referring to Axis2 ?

if
so there is no difference between client side and server side.

 

Thank
you!

Deepal

Anybody
knows the link to client handler tutorial? Thanks 

 



 



 







Reveal
your inner athlete and share it with friends on Windows Live. Share now!







_
Your PC, mobile phone, and online services work together like never before.
http://clk.atdmt.com/MRT/go/108587394/direct/01/

RE: Client handler tutorial

[Franklin, Allen]

Do I need to deploy my axis2 client into a servlet container to be able
to use client-side handlers?

Currently my client does not need a servlet container, it runs
stand-alone.

 

From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 12, 2008 6:46 PM
To: axis-user@ws.apache.org
Subject: RE: Client handler tutorial

 

yuo can deploy the client mar from the admin utility try
http://localhost:8080/axis2/axis2-admin/

HTH
Martin
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 





Subject: Re: Client handler tutorial
Date: Tue, 12 Aug 2008 18:34:04 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org

I am having trouble figuring out how to add client-side handlers in
axis2.

I see the email reply, below, that there is no difference between client
and server side.

But the configuration must be different since on the client side there
is no web container to put the axis2.xml configuration information for
the handler and also no place to put the .mar file. 

Client-side handler configuration remains a mystery to me.

Re: Client handler tutorial

Deepal Jayasinghe
Wed, 16 Apr 2008 22:57:25 -0700

Hi Chau,

Are you referring to Axis2 ?

if so there is no difference between client side and server side.

 

Thank you!

Deepal

Anybody knows the link to client handler tutorial? Thanks 

 



 

 



Reveal your inner athlete and share it with friends on Windows Live.
Share now!
 

problem with the extension / restriction base elements

[pierre betz]

Ok, I don't really know if the problem is regarding axis2 or not.

I'm using a rpc/literal wsdl.

The send/request part of the web service, using soap, is working well.

The problem is, when I have a look at the response sent by axis2 (1.4), I
can see that some elements have a xsi:type  in the declaration, like :

 
http://schemas.xmlsoap.org/soap/envelope/";>
 
  http://url.com/2008/webservice/2008/User/operations/";>

   http://url.com/2008/schema/2008/UserTypes";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:type="ns2:UserListType">


 
 
 1


 
000774
 

   
  
 


As you can see, the UserId have no xsi:type , but the VslUser has .

In fact, I really need to delete the "xsi:type="   because the soap
response is retrieved by a php page which create an array using the soap
tags.
I can't modify the php files, and they are looking for a  tag, which
here is not present.. because of the "xsi:type=".

Is there any way to delete the "xsi:type=" tag ??

the User is defined in a schema by :












And I can modify the extension  or the way it is created.. because of the
number of similar cases in my files.



Does anyone have an idea of what can I do ?

As I understood, if the element is not a root element (like the UserType
because it extend the UserBase), the soap part will by described with the
xsi:type.


before, with axis 1.4, I did not have this problem, so I think it's because
of axis2 , but don't really know what to do..



Any ideas would be greateful.. :) thanks at least to have read this message
:)

Thanks
Pierre

Re: MTOM Sample Error ?

[Charitha Kankanamge]

Hi,

Which Axis2 version are you using?

regards
Charitha

Şükrü Uzel wrote:


I have error when mtom run client in axis2 sample ( MTOM ).

 


Error :

 


Exception in thread "main" org.apache.axis2.AxisFault

at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)

at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:90)


at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)


at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)


at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)


at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)


at 
org.apache.ws.axis2.mtomsample.MTOMSampleMTOMSampleSOAP11Port_httpStub.attachment(Unknown 
Source)


at sample.mtom.client.Client.transferFile(Unknown Source)

at sample.mtom.client.Client.main(Unknown Source)

Caused by: java.lang.NullPointerException

at 
org.apache.axiom.attachments.Attachments.getSOAPPartContentType(Attachments.java:438)


at 
org.apache.axis2.builder.MIMEBuilder.processDocument(MIMEBuilder.java:40)


at 
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:164)


at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)


at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)


 


what is problem ?

 

 




Internal Virus Database is out-of-date.
Checked by AVG. 
Version: 7.5.524 / Virus Database: 270.4.7/1543 - Release Date: 7/9/2008 6:32 PM
 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

MTOM Sample Error ?

[Şükrü Uzel]

I have error when mtom run client in axis2 sample ( MTOM ).

 

Error :

 

Exception in thread "main" org.apache.axis2.AxisFault

at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)

at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:90)

at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAx
isOperation.java:353)

at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperatio
n.java:416)

at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisO
peration.java:228)

at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)

at
org.apache.ws.axis2.mtomsample.MTOMSampleMTOMSampleSOAP11Port_httpStub.attac
hment(Unknown Source)

at sample.mtom.client.Client.transferFile(Unknown Source)

at sample.mtom.client.Client.main(Unknown Source)

Caused by: java.lang.NullPointerException

at
org.apache.axiom.attachments.Attachments.getSOAPPartContentType(Attachments.
java:438)

at
org.apache.axis2.builder.MIMEBuilder.processDocument(MIMEBuilder.java:40)

at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUti
ls.java:164)

at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:112)

at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.j
ava:88)

 

what is problem ?

 

 

Re: formatting the soap response ?

[pierre betz]

ho.. and.. thinking about that ...

I use rpc/literal..  :) so its not that  :( .. normally with rpc/literal it
should work.


please tell me if you need some informations like wsdl/schema files or other
things, if you have some time to help me.

thanks :)

Pierre





2008/8/13 pierre betz <[EMAIL PROTECTED]>

> thanks a lot for the quick response :)
> ... the problem is that I work on a complete extranet using web services...
>
> and.. it's really really too big to re-create all the files with axis2
> wsdl2java too long, too big...
>
> is there another way to make it work ?
>
> with axis 1.4 it was working well, without the "xsi:type" , using adb and
> all the stuff.
>
> I just passed from axi 1.4 to axis2  1.4 ... so I would like to not change
> the wsdl files..
>
> but if you say it's the only way
> Just want to be sure of that before restarting all the work :( :(
>
> anyway.. thanks :)
>
>
>
>
> 2008/8/13 Moez Benmbarka <[EMAIL PROTECTED]>
>
> Hi,
>>
>> I think the type attributes are due to the use of the WSDL RPC/Encoded
>> style in your web service.
>> To receive the response you want, you should use a wrapped
>> Document/Literal style.
>> Look at this tutorial for choosing an appropriate WSDL style :
>> http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/
>>
>> Regards,
>> Moez BM
>>
>>
>> pierre betz wrote:
>>
>>> Hi everybody, I have a little .. important question :
>>>
>>> here is the response i retrieve when I call my web service :
>>>
>>> 
>>> http://schemas.xmlsoap.org/soap/envelope/";>
>>>  
>>>  
>>>   >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>> xsi:type="ns2:VslUserListType">
>>>  
>>> PERSONNE000774
>>>
>>>
>>>   
>>>  
>>>  
>>> 
>>>
>>> As you can see, the field  as the xsi:type="ns2:VslUserType" in
>>> the braket...
>>>
>>> My question, really simply, is : how can I have just the response like
>>> taht : without the xsi:type everywhere ?
>>>
>>> 
>>> http://schemas.xmlsoap.org/soap/envelope/";>
>>>  
>>>  
>>>   
>>>  
>>> PERSONNE000774
>>>
>>>
>>>   
>>>  
>>>  
>>>
>>>
>>> ? any ideas ?
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>

Re: formatting the soap response ?

[pierre betz]

thanks a lot for the quick response :)
... the problem is that I work on a complete extranet using web services...

and.. it's really really too big to re-create all the files with axis2
wsdl2java too long, too big...

is there another way to make it work ?

with axis 1.4 it was working well, without the "xsi:type" , using adb and
all the stuff.

I just passed from axi 1.4 to axis2  1.4 ... so I would like to not change
the wsdl files..

but if you say it's the only way
Just want to be sure of that before restarting all the work :( :(

anyway.. thanks :)




2008/8/13 Moez Benmbarka <[EMAIL PROTECTED]>

> Hi,
>
> I think the type attributes are due to the use of the WSDL RPC/Encoded
> style in your web service.
> To receive the response you want, you should use a wrapped Document/Literal
> style.
> Look at this tutorial for choosing an appropriate WSDL style :
> http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/
>
> Regards,
> Moez BM
>
>
> pierre betz wrote:
>
>> Hi everybody, I have a little .. important question :
>>
>> here is the response i retrieve when I call my web service :
>>
>> 
>> http://schemas.xmlsoap.org/soap/envelope/";>
>>  
>>  
>>   http://www.w3.org/2001/XMLSchema-instance";
>> xsi:type="ns2:VslUserListType">
>>  
>> PERSONNE000774
>>
>>
>>   
>>  
>>  
>> 
>>
>> As you can see, the field  as the xsi:type="ns2:VslUserType" in
>> the braket...
>>
>> My question, really simply, is : how can I have just the response like
>> taht : without the xsi:type everywhere ?
>>
>> 
>> http://schemas.xmlsoap.org/soap/envelope/";>
>>  
>>  
>>   
>>  
>> PERSONNE000774
>>
>>
>>   
>>  
>>  
>>
>>
>> ? any ideas ?
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: formatting the soap response ?

[Moez Benmbarka]

Hi,

I think the type attributes are due to the use of the WSDL RPC/Encoded 
style in your web service.
To receive the response you want, you should use a wrapped 
Document/Literal style.
Look at this tutorial for choosing an appropriate WSDL style : 
http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/


Regards,
Moez BM

pierre betz wrote:

Hi everybody, I have a little .. important question :

here is the response i retrieve when I call my web service :


xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>

 
  
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:type="ns2:VslUserListType">
 


 PERSONNE000774


   
  
 


As you can see, the field  as the xsi:type="ns2:VslUserType" 
in the braket...


My question, really simply, is : how can I have just the response like 
taht : without the xsi:type everywhere ?



xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>

 
  
   
 


 PERSONNE000774


   
  
 


? any ideas ?




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

formatting the soap response ?

[pierre betz]

Hi everybody, I have a little .. important question :

here is the response i retrieve when I call my web service :


http://schemas.xmlsoap.org/soap/envelope/";>
 
  
   http://www.w3.org/2001/XMLSchema-instance"; xsi:type="ns2:VslUserListType">


 PERSONNE000774


   
  
 


As you can see, the field  as the xsi:type="ns2:VslUserType" in the
braket...

My question, really simply, is : how can I have just the response like taht
: without the xsi:type everywhere ?


http://schemas.xmlsoap.org/soap/envelope/";>
 
  
   


 PERSONNE000774


   
  
 


? any ideas ?