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 Chris Averia <ch...@yahoo.com> on 2005/07/01 12:45:39 UTC
Help on Arrays
Hello,
I have attached the WSDL file that I compiled using wsdl2Java. This file contains a Soap call definition that expects arrays as return values.
However, I always encounter that the size of the return arrays are always 1. Can somebody point me to the right direction? BTW, Im using Axis1.2 final.
Here is the actual Soap Response:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
.<soapenv:Body>
..<LogGetEventsResponse xmlns="http://foo.com/foo1.0/">
...<accountId>83</accountId>
...<eventDt>2005-05-27T03:08:26</eventDt>
...<eventCode>109</eventCode>
...<eventSrc>4</eventSrc>
...<status>1</status>
...<adminUserId>99</adminUserId>
...<accountId>83</accountId>
...<eventDt>2005-05-27T03:07:59</eventDt>
...<eventCode>105</eventCode>
...<eventSrc>4</eventSrc>
...<status>1</status>
...<adminUserId>99</adminUserId>
...<accountId>83</accountId>
...<eventDt>2005-05-27T03:07:58</eventDt>
...<eventCode>102</eventCode>
...<eventSrc>4</eventSrc>
...<status>1</status>
...<adminUserId>99</adminUserId>
...<accountId>83</accountId>
...<eventDt>2005-05-
27T03:07:58</eventDt>...<eventCode>104</eventCode>
...<eventSrc>4</eventSrc>
...<status>1</status>
...<adminUserId>99</adminUserId>
...<accountId>83</accountId>
...<eventDt>2005-05-27T03:07:58</eventDt>
...<eventCode>103</eventCode>
...<eventSrc>4</eventSrc>
...<status>1</status>
...<adminUserId>99</adminUserId>
...<result>1</result>
..</LogGetEventsResponse>
.</soapenv:Body>
</soapenv:Envelope>
---------------------------------
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
Re: Help on Arrays
Posted by Anne Thomas Manes <at...@gmail.com>.
My first suggestion (defining the repeating field on the <sequence>)
is the proper way to describe the SOAP response you are receiving. But
perhaps WSDL2Java doesn't support this structure. I don't know how to
tell Axis how to deal with a set of repeating elements that aren't
defined as a single element. That's why I suggested that you define a
bean (event) to represent the repeating fields. But that would require
a change in your service. The challenge you have is that two of the
fields in your response are not repeating fields. Java doesn't really
work this way.
Anne
On 7/3/05, Chris Averia <ch...@yahoo.com> wrote:
> Hi Anne,
>
> I tried your 2 suggestions.
>
> For Suggestion No. 1, WSDL2Java generated a class called
> LogGetEventsResponse. Included are all the elements defined such as acctId,
> eventDt, eventCd...but all of the variables are all single instance. How
> can I make this as an array?
>
> For suggestion No.2, WSDL2Java generated a class called Event as well as an
> EventArrayHolder. However, it is expecting an element called "event" in the
> Soap response so that it could dederailize it properly to the array.
>
> How can I modify the WSDL file to properly deserailize the Soap response
> that I have included below?
>
> Thanks a lot.
>
>
> Anne Thomas Manes <at...@gmail.com> wrote:
> Your schema defines each element in the response as an array, but your
> response is not returning the array elements as arrays. Instead it is
> returning groups of elements as arrays. I suggest that you modify the
> schema to reflect the expected response. Something like this:
>
> <s:element name="LogGetEventsResponse">
> <s:complexType>
> <s:sequence>
> <s:sequence minOccurs="1" maxOccurs="200">
> <s:element name="accountId" type="s:unsignedInt" />
> <s:element name="eventDt" type="s:dateTime" />
> <s:element name="eventCode" type="s:unsignedInt" />
> <s:element name="eventSrc" type="s:unsignedInt" />
> <s:element name="status" type="s:unsignedInt" />
> <s:element name="errorSrcPeriod" type="s:unsignedInt" />
> <s:element name="errorSeverity" type="s:unsignedInt" />
> <s:element name="adminUserId" type="s:unsignedInt" />
> <s:element name="serverId" type="s:unsignedInt" />
> <s:element name="sessionId" type="s:unsignedInt" />
> <s:element name="InEndDt" type="s:dateTime" />
> <s:element name="OutStartDt" type="s:dateTime" />
> <s:element name="OutEndDt" type="s:dateTime" />
> <s:element name="MsgIn" type="s:unsignedInt" />
> <s:element name="MsgOut" type="s:unsignedInt" />
> <s:element name="BytesIn" type="s:unsignedInt" />
> <s:element name="BytesOut" type="s:unsignedInt" />
> <s:element name="CmdsIn" type="s:unsignedInt" />
> <s:element name="CmdsOut" type="s:unsignedInt" />
> <s:element name="AdnCount" type="s:unsignedInt" />
> <s:element name="transactionId" type="s:string" />
> <s:element name="extSessionInfo" type="s:string" />
> </s:sequence>
> <s:element minOccurs="1" maxOccurs="1" name="result" type="s:int"
> />
> <s:element minOccurs="0" maxOccurs="1" name="resultCause"
> type="s:string" />
> </s:sequence>
> </s:complexType>
> </s:element>
>
> Or you might want to create an element (and a matching bean) called
> event, and use this element to specify the array, such as:
>
> <s:element name="event">
> <s:complexType>
> <s:sequence>
> <s:element name="accountId" type="s:unsignedInt" />
> <s:element name="eventDt" type="s:dateTime" />
> <s:element name="eventCode" type="s:unsignedInt" />
> <s:element name="eventSrc" type="s:unsignedInt" />
> <s:element name="status" type="s:unsignedInt" />
> <s:element name="errorSrcPeriod" type="s:unsignedInt" />
> <s:element name="errorSeverity" type="s:unsignedInt" />
> <s:element name="adminUserId" type="s:unsignedInt" />
> <s:element name="serverId" type="s:unsignedInt" />
> <s:element name="sessionId" type="s:unsignedInt" />
> <s:element name="InEndDt" type="s:dateTime" />
> <s:element name="OutStartDt" type="s:dateTime" />
> <s:element name="OutEndDt" type="s:dateTime" />
> <s:element name="MsgIn" type="s:unsignedInt" />
> <s:element name="MsgOut" type="s:unsignedInt" />
> <s:element name="BytesIn" type="s:unsignedInt" />
> <s:element name="BytesOut" type="s:unsignedInt" />
> <s:element name="CmdsIn" type="s:unsignedInt" />
> <s:element name="CmdsOut" type="s:unsignedInt" />
> <s:element name="AdnCount" type="s:unsignedInt" />
> <s:element name="transactionId" type="s:string" />
> <s:element name="extSessionInfo" type="s:string" />
> </s:sequence>
> &nb sp; </s:complexType>
>
> </s:element>
> <s:element name="LogGetEventsResponse">
> <s:complexType>
> <s:sequence>
> <s:element minOccurs="1" maxOccurs="200" ref="event" />
> <s:element minOccurs="1" maxOccurs="1" name="result" type="s:int"
> />
> <s:element minOccurs="0" maxOccurs="1" name="resultCause"
> type="s:string" />
> </s:sequence>
> </s:complexType>
> </s:element>
>
> Anne
>
> On 7/1/05, Chris Averia <ch...@yahoo.com> wrote:
> >
> > Hello,
> >
> > I have attached the WSDL file that I compiled using wsdl2Java. This
> file
> > contains a Soap call definition that expects arrays as return values.
> >
> > However, I always encounter that the size of the return arrays are
> always 1.
> > Can somebody point me to the right direction? BTW, Im using Axis1.2
> final.
> >
> > Here is the actual Soap Response:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <soapenv:Envelope
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> >
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> > .<soapenv:Body>
> > ..<LogGetEventsRe sponse xmlns="http://foo.com/foo1.0/">
>
> > ...<accountId>83</accountId>
> > ...<eventDt>2005-05-27T03:08:26</eventDt>
> > ...<eventCode>109</eventCode>
> > ...<eventSrc>4</eventSrc>
> > ...<status>1</status>
> > ...<adminUserId>99</adminUserId>
> > ...<accountId>83</accountId>
> > ...<eventDt>2005-05-27T03:07:59</eventDt>
> > ...<eventCode>105</eventCode>
> > ...<eventSrc>4</eventSrc>
> > ...<status>1</status>
> > ...<adminUserId>99</adminUserId>
> > ...<accountId>83</accountId>
> > ...<eventDt>2005-05-27T03:07:58</eventDt>
> > ...<eventCode>102</eventCode>
> > ...<eventSrc>4</eventSrc>
> > ...<status>1</status>
> > ...<adminUserId>99</adminUserId>
> > ...<accountId>83</accountId>
> > ...<eventDt>2005-05-
> > 27T03:07:58</event Dt>...<eventCode>104</eventCode>
> > ...<eventSrc>4</eventSrc>
> > ...<status>1</status>
> > ...<adminUserId>99</adminUserId>
> > ...<accountId>83</accountId>
> > ...<eventDt>2005-05-27T03:07:58</eventDt>
> > ...<eventCode>103</eventCode>
> > ...<eventSrc>4</eventSrc>
> > ...<status>1</status>
> > ...<adminUserId>99</adminUserId>
> > ...<result>1</result>
> > ..</LogGetEventsResponse>
> > .</soapenv:Body>
> > </soapenv:Envelope>
>
>
> __________________________________________________
> Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
dynamic invocation and parameters
Posted by Ravi Krishnamurthy <ra...@savvion.com>.
Hello:
There are 3 modes for a parameter in a webservice operation -
ParameterMode.IN, ParameterMode.OUT, ParameterMode.INOUT in addition to
the return parameter.
Can get the parameter list from the BindingEntry as below:
Parameters parameters = (Parameters) bEntry.getParameters().get(oper);
Since the webservice that needs to be invoked can be off simple as well
as complex types, I guess I need to do call.addParameter is necessary.
Question:
1. When the call.addParameter is done, does the parameter sequence
matters. Should I add IN, INOUT and OUT parameters in that order?
2. when the instruction call.invoke(object[]) is called, does the values
passed need to be in the same sequence as the input and inout parameters.
3. Does a webservice call will have both return value and outputValues (
call.invoke and call.getOutputValues)
Is there an example I can look into.
I'm little bit confused and would appreciate your help.
Thanks,
Ravi
Re: Help on Arrays
Posted by Chris Averia <ch...@yahoo.com>.
Hi Anne,
I tried your 2 suggestions.
For Suggestion No. 1, WSDL2Java generated a class called LogGetEventsResponse. Included are all the elements defined such as acctId, eventDt, eventCd...but all of the variables are all single instance. How can I make this as an array?
For suggestion No.2, WSDL2Java generated a class called Event as well as an EventArrayHolder. However, it is expecting an element called "event" in the Soap response so that it could dederailize it properly to the array.
How can I modify the WSDL file to properly deserailize the Soap response that I have included below?
Thanks a lot.
Anne Thomas Manes <at...@gmail.com> wrote:
Your schema defines each element in the response as an array, but your
response is not returning the array elements as arrays. Instead it is
returning groups of elements as arrays. I suggest that you modify the
schema to reflect the expected response. Something like this:
<s:element name="LogGetEventsResponse">
<s:complexType>
<s:sequence>
<s:sequence minOccurs="1" maxOccurs="200">
<s:element name="accountId" type="s:unsignedInt" />
<s:element name="eventDt" type="s:dateTime" />
<s:element name="eventCode" type="s:unsignedInt" />
<s:element name="eventSrc" type="s:unsignedInt" />
<s:element name="status" type="s:unsignedInt" />
<s:element name="errorSrcPeriod" type="s:unsignedInt" />
<s:element name="errorSeverity" type="s:unsignedInt" />
<s:element name="adminUserId" type="s:unsignedInt" />
<s:element name="serverId" type="s:unsignedInt" />
<s:element name="sessionId" type="s:unsignedInt" />
<s:element name="InEndDt" type="s:dateTime" />
<s:element name="OutStartDt" type="s:dateTime" />
<s:element name="OutEndDt" type="s:dateTime" />
<s:element name="MsgIn" type="s:unsignedInt" />
<s:element name="MsgOut" type="s:unsignedInt" />
<s:element name="BytesIn" type="s:unsignedInt" />
<s:element name="BytesOut" type="s:unsignedInt" />
<s:element name="CmdsIn" type="s:unsignedInt" />
<s:element name="CmdsOut" type="s:unsignedInt" />
<s:element name="AdnCount" type="s:unsignedInt" />
<s:element name="transactionId" type="s:string" />
<s:element name="extSessionInfo" type="s:string" />
</s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="result" type="s:int"
/>
<s:element minOccurs="0" maxOccurs="1" name="resultCause"
type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
Or you might want to create an element (and a matching bean) called
event, and use this element to specify the array, such as:
<s:element name="event">
<s:complexType>
<s:sequence>
<s:element name="accountId" type="s:unsignedInt" />
<s:element name="eventDt" type="s:dateTime" />
<s:element name="eventCode" type="s:unsignedInt" />
<s:element name="eventSrc" type="s:unsignedInt" />
<s:element name="status" type="s:unsignedInt" />
<s:element name="errorSrcPeriod" type="s:unsignedInt" />
<s:element name="errorSeverity" type="s:unsignedInt" />
<s:element name="adminUserId" type="s:unsignedInt" />
<s:element name="serverId" type="s:unsignedInt" />
<s:element name="sessionId" type="s:unsignedInt" />
<s:element name="InEndDt" type="s:dateTime" />
<s:element name="OutStartDt" type="s:dateTime" />
<s:element name="OutEndDt" type="s:dateTime" />
<s:element name="MsgIn" type="s:unsignedInt" />
<s:element name="MsgOut" type="s:unsignedInt" />
<s:element name="BytesIn" type="s:unsignedInt" />
<s:element name="BytesOut" type="s:unsignedInt" />
<s:element name="CmdsIn" type="s:unsignedInt" />
<s:element name="CmdsOut" type="s:unsignedInt" />
<s:element name="AdnCount" type="s:unsignedInt" />
<s:element name="transactionId" type="s:string" />
<s:element name="extSessionInfo" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="LogGetEventsResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="200" ref="event" />
<s:element minOccurs="1" maxOccurs="1" name="result" type="s:int"
/>
<s:element minOccurs="0" maxOccurs="1" name="resultCause"
type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
Anne
On 7/1/05, Chris Averia <ch...@yahoo.com> wrote:
>
> Hello,
>
> I have attached the WSDL file that I compiled using wsdl2Java. This
file
> contains a Soap call definition that expects arrays as return values.
>
> However, I always encounter that the size of the return arrays are
always 1.
> Can somebody point me to the right direction? BTW, Im using Axis1.2
final.
>
> Here is the actual Soap Response:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> .<soapenv:Body>
> ..<LogGetEventsResponse xmlns="http://foo.com/foo1.0/">
> ...<accountId>83</accountId>
> ...<eventDt>2005-05-27T03:08:26</eventDt>
> ...<eventCode>109</eventCode>
> ...<eventSrc>4</eventSrc>
> ...<status>1</status>
> ...<adminUserId>99</adminUserId>
> ...<accountId>83</accountId>
> ...<eventDt>2005-05-27T03:07:59</eventDt>
> ...<eventCode>105</eventCode>
> ...<eventSrc>4</eventSrc>
> ...<status>1</status>
> ...<adminUserId>99</adminUserId>
> ...<accountId>83</accountId>
> ...<eventDt>2005-05-27T03:07:58</eventDt>
> ...<eventCode>102</eventCode>
> ...<eventSrc>4</eventSrc>
> ...<status>1</status>
> ...<adminUserId>99</adminUserId>
> ...<accountId>83</accountId>
> ...<eventDt>2005-05-
> 27T03:07:58</event Dt>...<eventCode>104</eventCode>
> ...<eventSrc>4</eventSrc>
> ...<status>1</status>
> ...<adminUserId>99</adminUserId>
> ...<accountId>83</accountId>
> ...<eventDt>2005-05-27T03:07:58</eventDt>
> ...<eventCode>103</eventCode>
> ...<eventSrc>4</eventSrc>
> ...<status>1</status>
> ...<adminUserId>99</adminUserId>
> ...<result>1</result>
> ..</LogGetEventsResponse>
> .</soapenv:Body>
> </soapenv:Envelope>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Help on Arrays
Posted by Anne Thomas Manes <at...@gmail.com>.
Your schema defines each element in the response as an array, but your
response is not returning the array elements as arrays. Instead it is
returning groups of elements as arrays. I suggest that you modify the
schema to reflect the expected response. Something like this:
<s:element name="LogGetEventsResponse">
<s:complexType>
<s:sequence>
<s:sequence minOccurs="1" maxOccurs="200">
<s:element name="accountId" type="s:unsignedInt" />
<s:element name="eventDt" type="s:dateTime" />
<s:element name="eventCode" type="s:unsignedInt" />
<s:element name="eventSrc" type="s:unsignedInt" />
<s:element name="status" type="s:unsignedInt" />
<s:element name="errorSrcPeriod" type="s:unsignedInt" />
<s:element name="errorSeverity" type="s:unsignedInt" />
<s:element name="adminUserId" type="s:unsignedInt" />
<s:element name="serverId" type="s:unsignedInt" />
<s:element name="sessionId" type="s:unsignedInt" />
<s:element name="InEndDt" type="s:dateTime" />
<s:element name="OutStartDt" type="s:dateTime" />
<s:element name="OutEndDt" type="s:dateTime" />
<s:element name="MsgIn" type="s:unsignedInt" />
<s:element name="MsgOut" type="s:unsignedInt" />
<s:element name="BytesIn" type="s:unsignedInt" />
<s:element name="BytesOut" type="s:unsignedInt" />
<s:element name="CmdsIn" type="s:unsignedInt" />
<s:element name="CmdsOut" type="s:unsignedInt" />
<s:element name="AdnCount" type="s:unsignedInt" />
<s:element name="transactionId" type="s:string" />
<s:element name="extSessionInfo" type="s:string" />
</s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="result" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="resultCause"
type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
Or you might want to create an element (and a matching bean) called
event, and use this element to specify the array, such as:
<s:element name="event">
<s:complexType>
<s:sequence>
<s:element name="accountId" type="s:unsignedInt" />
<s:element name="eventDt" type="s:dateTime" />
<s:element name="eventCode" type="s:unsignedInt" />
<s:element name="eventSrc" type="s:unsignedInt" />
<s:element name="status" type="s:unsignedInt" />
<s:element name="errorSrcPeriod" type="s:unsignedInt" />
<s:element name="errorSeverity" type="s:unsignedInt" />
<s:element name="adminUserId" type="s:unsignedInt" />
<s:element name="serverId" type="s:unsignedInt" />
<s:element name="sessionId" type="s:unsignedInt" />
<s:element name="InEndDt" type="s:dateTime" />
<s:element name="OutStartDt" type="s:dateTime" />
<s:element name="OutEndDt" type="s:dateTime" />
<s:element name="MsgIn" type="s:unsignedInt" />
<s:element name="MsgOut" type="s:unsignedInt" />
<s:element name="BytesIn" type="s:unsignedInt" />
<s:element name="BytesOut" type="s:unsignedInt" />
<s:element name="CmdsIn" type="s:unsignedInt" />
<s:element name="CmdsOut" type="s:unsignedInt" />
<s:element name="AdnCount" type="s:unsignedInt" />
<s:element name="transactionId" type="s:string" />
<s:element name="extSessionInfo" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="LogGetEventsResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="200" ref="event" />
<s:element minOccurs="1" maxOccurs="1" name="result" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="resultCause"
type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
Anne
On 7/1/05, Chris Averia <ch...@yahoo.com> wrote:
>
> Hello,
>
> I have attached the WSDL file that I compiled using wsdl2Java. This file
> contains a Soap call definition that expects arrays as return values.
>
> However, I always encounter that the size of the return arrays are always 1.
> Can somebody point me to the right direction? BTW, Im using Axis1.2 final.
>
> Here is the actual Soap Response:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> .<soapenv:Body>
> ..<LogGetEventsResponse xmlns="http://foo.com/foo1.0/">
> ...<accountId>83</accountId>
> ...<eventDt>2005-05-27T03:08:26</eventDt>
> ...<eventCode>109</eventCode>
> ...<eventSrc>4</eventSrc>
> ...<status>1</status>
> ...<adminUserId>99</adminUserId>
> ...<accountId>83</accountId>
> ...<eventDt>2005-05-27T03:07:59</eventDt>
> ...<eventCode>105</eventCode>
> ...<eventSrc>4</eventSrc>
> ...<status>1</status>
> ...<adminUserId>99</adminUserId>
> ...<accountId>83</accountId>
> ...<eventDt>2005-05-27T03:07:58</eventDt>
> ...<eventCode>102</eventCode>
> ...<eventSrc>4</eventSrc>
> ...<status>1</status>
> ...<adminUserId>99</adminUserId>
> ...<accountId>83</accountId>
> ...<eventDt>2005-05-
> 27T03:07:58</event Dt>...<eventCode>104</eventCode>
> ...<eventSrc>4</eventSrc>
> ...<status>1</status>
> ...<adminUserId>99</adminUserId>
> ...<accountId>83</accountId>
> ...<eventDt>2005-05-27T03:07:58</eventDt>
> ...<eventCode>103</eventCode>
> ...<eventSrc>4</eventSrc>
> ...<status>1</status>
> ...<adminUserId>99</adminUserId>
> ...<result>1</result>
> ..</LogGetEventsResponse>
> .</soapenv:Body>
> </soapenv:Envelope>
>
>
> ________________________________
> Do you Yahoo!?
> Read only the mail you want - Yahoo! Mail SpamGuard.
>
>
>