You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Linus Kamb <li...@iris.washington.edu> on 2005/07/16 00:53:47 UTC

wsdl2java not producing array wrappers

I am trying to pass arrays of things using wrapper elements (ArrayOf<foo>).

However, I cannot get java2wsdl (called via the axis-wsdl2java ant task) to generate the
wrapper element for arrays of xsd:strings or org.w3c.dom.Element (apachesoap:Element) 
objects.  It produces wrappers for other complex elements.

Any thoughts?

Thanks,
Linus

[Axis2] Implementing Services

Posted by A Yang <ay...@yahoo.ca>.
Hi there,

Axis 1 supports the following interfaces for me to implement:  

public Element [] method(Element [] bodies);
public SOAPBodyElement [] method (SOAPBodyElement [] bodies);
public Document method(Document body);
public void method(SOAPEnvelope req, SOAPEnvelope resp); 

But the only analagous interface I could find for Axis 2 is:

public OMElement doSomething(OMElement element)?
 
If I wanted the entire SOAP envelope and payload, what is the best way
to obtain it?

Also, from what I can see, it's the endpoint that determines the
operation to be called. Is that correct?

I find that when I use the Call.invokeBlocking(opname, payload) method,
the opname parameter is actually ignored - is this correct?
 
Thanks!

Andy


	

	
		
__________________________________________________________ 
Find your next car at http://autos.yahoo.ca

Re: soap:headers and explicit service context

Posted by Davanum Srinivas <da...@gmail.com>.
run wsdl2java on test\wsdl\header\header.wsdl and look at the generated code.

-- dims

On 8/23/05, Hans Planting (CWEU-USERS/CWNL)
<ha...@nl.compuware.com> wrote:
> Ok, but if I for example use 'getHeader' in org.apache.axis.client.Stub,
> I get a SOAPHeaderElement - is there a way to deserialize this to a java
> object (using BeanDeserializer etc) without having to write code to
> parse the contents of the elements?
> 
> Hans
> 
> 
> 
> Davanum Srinivas wrote:
> 
> >If you set up the wsdl correctly, then the generated code has the
> >addition java objects for the stuff in soap headers.
> >
> >-- dims
> >
> >On 8/23/05, Hans Planting (CWEU-USERS/CWNL)
> ><ha...@nl.compuware.com> wrote:
> >
> >
> >>Hi there,
> >>
> >>Is there support planned for explicit soap headers as described in
> >>JAX-RPC 1.1 chapter 11.2.2?
> >>With explicit soap headers I'd expect Axis to append additional
> >>parameters for soap:headers following the service endpoint defined
> >>paramers in the remote method signature. Also no custom
> >>parsing/deserialization would need to be implemented.
> >>Currently in order to process soap:headers you need to implement a
> >>handler or use the setHeader and getHeader methods in
> >>org.apache.axis.client.Stub and in both cases implement code to
> >>parse/deserialize the soap elements; Axis does not deserialize the
> >>contents of soap:headers to Java objects (correct me if I'm wrong - is
> >>there a way to do this?).
> >>
> >>Thanx!
> >>
> >>Hans
> >>
> >>
> >>
> >
> >
> >
> >
> 
> 


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform

Re: soap:headers and explicit service context

Posted by "Hans Planting (CWEU-USERS/CWNL)" <ha...@nl.compuware.com>.
Ok, but if I for example use 'getHeader' in org.apache.axis.client.Stub, 
I get a SOAPHeaderElement - is there a way to deserialize this to a java 
object (using BeanDeserializer etc) without having to write code to 
parse the contents of the elements?

Hans



Davanum Srinivas wrote:

>If you set up the wsdl correctly, then the generated code has the
>addition java objects for the stuff in soap headers.
>
>-- dims
>
>On 8/23/05, Hans Planting (CWEU-USERS/CWNL)
><ha...@nl.compuware.com> wrote:
>  
>
>>Hi there,
>>
>>Is there support planned for explicit soap headers as described in
>>JAX-RPC 1.1 chapter 11.2.2?
>>With explicit soap headers I'd expect Axis to append additional
>>parameters for soap:headers following the service endpoint defined
>>paramers in the remote method signature. Also no custom
>>parsing/deserialization would need to be implemented.
>>Currently in order to process soap:headers you need to implement a
>>handler or use the setHeader and getHeader methods in
>>org.apache.axis.client.Stub and in both cases implement code to
>>parse/deserialize the soap elements; Axis does not deserialize the
>>contents of soap:headers to Java objects (correct me if I'm wrong - is
>>there a way to do this?).
>>
>>Thanx!
>>
>>Hans
>>
>>    
>>
>
>
>  
>

Re: soap:headers and explicit service context

Posted by Davanum Srinivas <da...@gmail.com>.
If you set up the wsdl correctly, then the generated code has the
addition java objects for the stuff in soap headers.

-- dims

On 8/23/05, Hans Planting (CWEU-USERS/CWNL)
<ha...@nl.compuware.com> wrote:
> Hi there,
> 
> Is there support planned for explicit soap headers as described in
> JAX-RPC 1.1 chapter 11.2.2?
> With explicit soap headers I'd expect Axis to append additional
> parameters for soap:headers following the service endpoint defined
> paramers in the remote method signature. Also no custom
> parsing/deserialization would need to be implemented.
> Currently in order to process soap:headers you need to implement a
> handler or use the setHeader and getHeader methods in
> org.apache.axis.client.Stub and in both cases implement code to
> parse/deserialize the soap elements; Axis does not deserialize the
> contents of soap:headers to Java objects (correct me if I'm wrong - is
> there a way to do this?).
> 
> Thanx!
> 
> Hans
> 


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform

soap:headers and explicit service context

Posted by "Hans Planting (CWEU-USERS/CWNL)" <ha...@nl.compuware.com>.
Hi there,

Is there support planned for explicit soap headers as described in 
JAX-RPC 1.1 chapter 11.2.2?
With explicit soap headers I'd expect Axis to append additional 
parameters for soap:headers following the service endpoint defined 
paramers in the remote method signature. Also no custom 
parsing/deserialization would need to be implemented.
Currently in order to process soap:headers you need to implement a 
handler or use the setHeader and getHeader methods in 
org.apache.axis.client.Stub and in both cases implement code to 
parse/deserialize the soap elements; Axis does not deserialize the 
contents of soap:headers to Java objects (correct me if I'm wrong - is 
there a way to do this?).

Thanx!

Hans