You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ephemeris Lappis (JIRA)" <ax...@ws.apache.org> on 2005/06/15 14:07:48 UTC
[jira] Created: (AXIS-2055) AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
---------------------------------------------------------------------------------
Key: AXIS-2055
URL: http://issues.apache.org/jira/browse/AXIS-2055
Project: Apache Axis
Type: Bug
Components: Serialization/Deserialization
Versions: 1.2
Environment: java full version "1.4.2_01-b06"
Reporter: Ephemeris Lappis
Attachments: axis3.wsdl, deploy.wsdd, http-request.txt, http-response.txt, server-error.txt
It seems an axis internal error occurs on the server side, using document/literal style, when processing an operation with the following signature :
public int testIntegerPairToInteger(int i1, int i2)
The wsdl and wsdd files that are attached seem ok for me, and the sent request too.
The error trace on the server side is also attached.
Just for information, the same operation is processed without any problem in both wrapped and document styles...
I've done another test with an operation like
CustomeType operation(CustomeType v1, CustomeType v2)
And it seems the problem is similar. No error is produced, but the server class only receives the first parameter, the second one is always null.
The http request seems ok :
POST /axis3/services/TestServicePort HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 127.0.0.1:81 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 689 <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<in13 xmlns="urn:axis-test3">
<booleanProperty>true</booleanProperty>
<doubleProperty>13.0</doubleProperty>
<integerProperty>11</integerProperty>
<longProperty>12</longProperty>
<stringProperty>a</stringProperty>
</in13>
<in14 xmlns="urn:axis-test3">
<booleanProperty>true</booleanProperty>
<doubleProperty>23.0</doubleProperty>
<integerProperty>21</integerProperty>
<longProperty>22</longProperty>
<stringProperty>b</stringProperty>
</in14>
</soapenv:Body>
</soapenv:Envelope>
And the wsdd extract too :
<operation name="testFlatBeanPairToFlatBean" qname="testFlatBeanPairToFlatBean" returnQName="retNS:testFlatBeanPairToFlatBeanReturn" xmlns:retNS="urn:axis-test3" returnType="rtns:FlatBean" xmlns:rtns="urn:axis-test3" soapAction="" >
<parameter qname="pns:in13" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
<parameter qname="pns:in14" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
</operation>
But the server class always receives null for the second parameter...
See the attachments...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-2055) AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
Posted by "Ephemeris Lappis (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2055?page=comments#action_12314420 ]
Ephemeris Lappis commented on AXIS-2055:
----------------------------------------
Sure the last comment is truth !
But, if i'm not mistaken, axis (or any web service stack) should take into account the web service style and adapt the interface to the required exchange mode.
If i'm mistaken, at least, the java2wsdl should fails and report an invalid interface...
> AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
> ---------------------------------------------------------------------------------
>
> Key: AXIS-2055
> URL: http://issues.apache.org/jira/browse/AXIS-2055
> Project: Apache Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: java full version "1.4.2_01-b06"
> Reporter: Ephemeris Lappis
> Attachments: axis3.wsdl, deploy.wsdd, http-request.txt, http-response.txt, second_parameter_is_null_by_rig.txt, server-error.txt
>
> It seems an axis internal error occurs on the server side, using document/literal style, when processing an operation with the following signature :
> public int testIntegerPairToInteger(int i1, int i2)
> The wsdl and wsdd files that are attached seem ok for me, and the sent request too.
> The error trace on the server side is also attached.
> Just for information, the same operation is processed without any problem in both wrapped and document styles...
> I've done another test with an operation like
> CustomeType operation(CustomeType v1, CustomeType v2)
> And it seems the problem is similar. No error is produced, but the server class only receives the first parameter, the second one is always null.
> The http request seems ok :
> POST /axis3/services/TestServicePort HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 127.0.0.1:81 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 689 <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <in13 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>13.0</doubleProperty>
> <integerProperty>11</integerProperty>
> <longProperty>12</longProperty>
> <stringProperty>a</stringProperty>
> </in13>
> <in14 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>23.0</doubleProperty>
> <integerProperty>21</integerProperty>
> <longProperty>22</longProperty>
> <stringProperty>b</stringProperty>
> </in14>
> </soapenv:Body>
> </soapenv:Envelope>
> And the wsdd extract too :
> <operation name="testFlatBeanPairToFlatBean" qname="testFlatBeanPairToFlatBean" returnQName="retNS:testFlatBeanPairToFlatBeanReturn" xmlns:retNS="urn:axis-test3" returnType="rtns:FlatBean" xmlns:rtns="urn:axis-test3" soapAction="" >
> <parameter qname="pns:in13" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> <parameter qname="pns:in14" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> </operation>
> But the server class always receives null for the second parameter...
> See the attachments...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-2055) AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
Posted by "Ephemeris Lappis (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2055?page=all ]
Ephemeris Lappis updated AXIS-2055:
-----------------------------------
Attachment: axis3.wsdl
deploy.wsdd
server-error.txt
> AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
> ---------------------------------------------------------------------------------
>
> Key: AXIS-2055
> URL: http://issues.apache.org/jira/browse/AXIS-2055
> Project: Apache Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: java full version "1.4.2_01-b06"
> Reporter: Ephemeris Lappis
> Attachments: axis3.wsdl, deploy.wsdd, http-request.txt, http-response.txt, server-error.txt
>
> It seems an axis internal error occurs on the server side, using document/literal style, when processing an operation with the following signature :
> public int testIntegerPairToInteger(int i1, int i2)
> The wsdl and wsdd files that are attached seem ok for me, and the sent request too.
> The error trace on the server side is also attached.
> Just for information, the same operation is processed without any problem in both wrapped and document styles...
> I've done another test with an operation like
> CustomeType operation(CustomeType v1, CustomeType v2)
> And it seems the problem is similar. No error is produced, but the server class only receives the first parameter, the second one is always null.
> The http request seems ok :
> POST /axis3/services/TestServicePort HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 127.0.0.1:81 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 689 <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <in13 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>13.0</doubleProperty>
> <integerProperty>11</integerProperty>
> <longProperty>12</longProperty>
> <stringProperty>a</stringProperty>
> </in13>
> <in14 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>23.0</doubleProperty>
> <integerProperty>21</integerProperty>
> <longProperty>22</longProperty>
> <stringProperty>b</stringProperty>
> </in14>
> </soapenv:Body>
> </soapenv:Envelope>
> And the wsdd extract too :
> <operation name="testFlatBeanPairToFlatBean" qname="testFlatBeanPairToFlatBean" returnQName="retNS:testFlatBeanPairToFlatBeanReturn" xmlns:retNS="urn:axis-test3" returnType="rtns:FlatBean" xmlns:rtns="urn:axis-test3" soapAction="" >
> <parameter qname="pns:in13" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> <parameter qname="pns:in14" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> </operation>
> But the server class always receives null for the second parameter...
> See the attachments...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Updated: (AXIS-2055) AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
Posted by Ahab Abouzour <ea...@yahoo.com>.
Where can I find more info about doc/lit,
wrapped,..etc styles. What specs is it in?
Thanks,
--- "Ronny Riedel (JIRA)" <ax...@ws.apache.org>
wrote:
> [
>
http://issues.apache.org/jira/browse/AXIS-2055?page=all
> ]
>
> Ronny Riedel updated AXIS-2055:
> -------------------------------
>
> Attachment: second_parameter_is_null_by_rig.txt
>
> > AXIS 1.2 (final) - document/literal - error
> processing operation with 2 arguments
> >
>
---------------------------------------------------------------------------------
> >
> > Key: AXIS-2055
> > URL:
> http://issues.apache.org/jira/browse/AXIS-2055
> > Project: Apache Axis
> > Type: Bug
> > Components: Serialization/Deserialization
> > Versions: 1.2
> > Environment: java full version "1.4.2_01-b06"
> > Reporter: Ephemeris Lappis
> > Attachments: axis3.wsdl, deploy.wsdd,
> http-request.txt, http-response.txt,
> second_parameter_is_null_by_rig.txt,
> server-error.txt
> >
> > It seems an axis internal error occurs on the
> server side, using document/literal style, when
> processing an operation with the following signature
> :
> > public int testIntegerPairToInteger(int i1, int
> i2)
> > The wsdl and wsdd files that are attached seem ok
> for me, and the sent request too.
> > The error trace on the server side is also
> attached.
> > Just for information, the same operation is
> processed without any problem in both wrapped and
> document styles...
> > I've done another test with an operation like
> > CustomeType operation(CustomeType v1, CustomeType
> v2)
> > And it seems the problem is similar. No error is
> produced, but the server class only receives the
> first parameter, the second one is always null.
> > The http request seems ok :
> > POST /axis3/services/TestServicePort HTTP/1.0
> Content-Type: text/xml; charset=utf-8 Accept:
> application/soap+xml, application/dime,
> multipart/related, text/* User-Agent: Axis/1.2 Host:
> 127.0.0.1:81 Cache-Control: no-cache Pragma:
> no-cache SOAPAction: "" Content-Length: 689 <?xml
> version="1.0" encoding="UTF-8"?>
> > <soapenv:Envelope
>
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> > <soapenv:Body>
> > <in13 xmlns="urn:axis-test3">
> >
> <booleanProperty>true</booleanProperty>
> > <doubleProperty>13.0</doubleProperty>
> > <integerProperty>11</integerProperty>
> > <longProperty>12</longProperty>
> > <stringProperty>a</stringProperty>
> > </in13>
> > <in14 xmlns="urn:axis-test3">
> >
> <booleanProperty>true</booleanProperty>
> > <doubleProperty>23.0</doubleProperty>
> > <integerProperty>21</integerProperty>
> > <longProperty>22</longProperty>
> > <stringProperty>b</stringProperty>
> > </in14>
> > </soapenv:Body>
> > </soapenv:Envelope>
> > And the wsdd extract too :
> > <operation name="testFlatBeanPairToFlatBean"
> qname="testFlatBeanPairToFlatBean"
> returnQName="retNS:testFlatBeanPairToFlatBeanReturn"
> xmlns:retNS="urn:axis-test3"
> returnType="rtns:FlatBean"
> xmlns:rtns="urn:axis-test3" soapAction="" >
> > <parameter qname="pns:in13"
> xmlns:pns="urn:axis-test3" type="tns:FlatBean"
> xmlns:tns="urn:axis-test3"/>
> > <parameter qname="pns:in14"
> xmlns:pns="urn:axis-test3" type="tns:FlatBean"
> xmlns:tns="urn:axis-test3"/>
> > </operation>
> > But the server class always receives null for the
> second parameter...
> > See the attachments...
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of
> the administrators:
>
>
http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[jira] Updated: (AXIS-2055) AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
Posted by "Ronny Riedel (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2055?page=all ]
Ronny Riedel updated AXIS-2055:
-------------------------------
Attachment: second_parameter_is_null_by_rig.txt
> AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
> ---------------------------------------------------------------------------------
>
> Key: AXIS-2055
> URL: http://issues.apache.org/jira/browse/AXIS-2055
> Project: Apache Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: java full version "1.4.2_01-b06"
> Reporter: Ephemeris Lappis
> Attachments: axis3.wsdl, deploy.wsdd, http-request.txt, http-response.txt, second_parameter_is_null_by_rig.txt, server-error.txt
>
> It seems an axis internal error occurs on the server side, using document/literal style, when processing an operation with the following signature :
> public int testIntegerPairToInteger(int i1, int i2)
> The wsdl and wsdd files that are attached seem ok for me, and the sent request too.
> The error trace on the server side is also attached.
> Just for information, the same operation is processed without any problem in both wrapped and document styles...
> I've done another test with an operation like
> CustomeType operation(CustomeType v1, CustomeType v2)
> And it seems the problem is similar. No error is produced, but the server class only receives the first parameter, the second one is always null.
> The http request seems ok :
> POST /axis3/services/TestServicePort HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 127.0.0.1:81 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 689 <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <in13 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>13.0</doubleProperty>
> <integerProperty>11</integerProperty>
> <longProperty>12</longProperty>
> <stringProperty>a</stringProperty>
> </in13>
> <in14 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>23.0</doubleProperty>
> <integerProperty>21</integerProperty>
> <longProperty>22</longProperty>
> <stringProperty>b</stringProperty>
> </in14>
> </soapenv:Body>
> </soapenv:Envelope>
> And the wsdd extract too :
> <operation name="testFlatBeanPairToFlatBean" qname="testFlatBeanPairToFlatBean" returnQName="retNS:testFlatBeanPairToFlatBeanReturn" xmlns:retNS="urn:axis-test3" returnType="rtns:FlatBean" xmlns:rtns="urn:axis-test3" soapAction="" >
> <parameter qname="pns:in13" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> <parameter qname="pns:in14" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> </operation>
> But the server class always receives null for the second parameter...
> See the attachments...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-2055) AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
Posted by "Ronny Riedel (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2055?page=comments#action_12314403 ]
Ronny Riedel commented on AXIS-2055:
------------------------------------
Hello, me again. I thinke, we (Ephemeris Lappis and me) do the mistake. I have a wonderfull book about Apache Axis. It describes the "document/literal" Message Style, too. There stands written that a <message> definition in the wsdl-file may contain only one <part> with this message-style.
example:
<wsdl:message name="addSong">
<wsdl:part name="title" type="xsd:string" />
<wsdl:part name="interpret" type="xsd:string" />
</wsdl:messge>
is WRONG for message-style "document/literal". read correctly must as follows:
<wsdl:types>
<schema [...]>
<complexType name="song">
<sequence>
<element name="title" type="xsd:string"/>
<element name="interpret" type="xsd:string"/>
</sequence>
</complexType>
</schema [...]>
</wsdl:types>
<wsdl:message name="addSong">
<wsdl:part name="song" element="impl:song" />
</wsdl:messge>
how you can see, the <message> defintion contains only one <part>.
So that other developer immediately notice the error in the WSDL-document, Axis should supply an appropriate error at such constellations.
reguards
rig
> AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
> ---------------------------------------------------------------------------------
>
> Key: AXIS-2055
> URL: http://issues.apache.org/jira/browse/AXIS-2055
> Project: Apache Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: java full version "1.4.2_01-b06"
> Reporter: Ephemeris Lappis
> Attachments: axis3.wsdl, deploy.wsdd, http-request.txt, http-response.txt, second_parameter_is_null_by_rig.txt, server-error.txt
>
> It seems an axis internal error occurs on the server side, using document/literal style, when processing an operation with the following signature :
> public int testIntegerPairToInteger(int i1, int i2)
> The wsdl and wsdd files that are attached seem ok for me, and the sent request too.
> The error trace on the server side is also attached.
> Just for information, the same operation is processed without any problem in both wrapped and document styles...
> I've done another test with an operation like
> CustomeType operation(CustomeType v1, CustomeType v2)
> And it seems the problem is similar. No error is produced, but the server class only receives the first parameter, the second one is always null.
> The http request seems ok :
> POST /axis3/services/TestServicePort HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 127.0.0.1:81 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 689 <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <in13 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>13.0</doubleProperty>
> <integerProperty>11</integerProperty>
> <longProperty>12</longProperty>
> <stringProperty>a</stringProperty>
> </in13>
> <in14 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>23.0</doubleProperty>
> <integerProperty>21</integerProperty>
> <longProperty>22</longProperty>
> <stringProperty>b</stringProperty>
> </in14>
> </soapenv:Body>
> </soapenv:Envelope>
> And the wsdd extract too :
> <operation name="testFlatBeanPairToFlatBean" qname="testFlatBeanPairToFlatBean" returnQName="retNS:testFlatBeanPairToFlatBeanReturn" xmlns:retNS="urn:axis-test3" returnType="rtns:FlatBean" xmlns:rtns="urn:axis-test3" soapAction="" >
> <parameter qname="pns:in13" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> <parameter qname="pns:in14" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> </operation>
> But the server class always receives null for the second parameter...
> See the attachments...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-2055) AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
Posted by "Ronny Riedel (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2055?page=comments#action_12314338 ]
Ronny Riedel commented on AXIS-2055:
------------------------------------
Hello,
i have the same problem. My Function looks like:
public ArrayOfString getSomething(String p_str_1, String p_str_2) throws RemoteException { ... }
(ArrayOfString is a bean that contains a String-Array)
Because of using Strings, i get no Server-Exception and everything looks find - but it isn't :-). I put on debugging and wonder, that the output stops after the proccessing of the first parameter. I add the debug-output, so you can see..
My Environment
SuSE Linux Enterprise Server 9
--
Apache Tomcat/5.0.27
Apache Axis 1.2.1 (downloaded and installed today because of that bug)
--
java version "1.4.2_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode)
reguards
rig
> AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
> ---------------------------------------------------------------------------------
>
> Key: AXIS-2055
> URL: http://issues.apache.org/jira/browse/AXIS-2055
> Project: Apache Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: java full version "1.4.2_01-b06"
> Reporter: Ephemeris Lappis
> Attachments: axis3.wsdl, deploy.wsdd, http-request.txt, http-response.txt, server-error.txt
>
> It seems an axis internal error occurs on the server side, using document/literal style, when processing an operation with the following signature :
> public int testIntegerPairToInteger(int i1, int i2)
> The wsdl and wsdd files that are attached seem ok for me, and the sent request too.
> The error trace on the server side is also attached.
> Just for information, the same operation is processed without any problem in both wrapped and document styles...
> I've done another test with an operation like
> CustomeType operation(CustomeType v1, CustomeType v2)
> And it seems the problem is similar. No error is produced, but the server class only receives the first parameter, the second one is always null.
> The http request seems ok :
> POST /axis3/services/TestServicePort HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 127.0.0.1:81 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 689 <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <in13 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>13.0</doubleProperty>
> <integerProperty>11</integerProperty>
> <longProperty>12</longProperty>
> <stringProperty>a</stringProperty>
> </in13>
> <in14 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>23.0</doubleProperty>
> <integerProperty>21</integerProperty>
> <longProperty>22</longProperty>
> <stringProperty>b</stringProperty>
> </in14>
> </soapenv:Body>
> </soapenv:Envelope>
> And the wsdd extract too :
> <operation name="testFlatBeanPairToFlatBean" qname="testFlatBeanPairToFlatBean" returnQName="retNS:testFlatBeanPairToFlatBeanReturn" xmlns:retNS="urn:axis-test3" returnType="rtns:FlatBean" xmlns:rtns="urn:axis-test3" soapAction="" >
> <parameter qname="pns:in13" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> <parameter qname="pns:in14" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> </operation>
> But the server class always receives null for the second parameter...
> See the attachments...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-2055) AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
Posted by "Ephemeris Lappis (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2055?page=all ]
Ephemeris Lappis updated AXIS-2055:
-----------------------------------
Attachment: http-request.txt
http-response.txt
> AXIS 1.2 (final) - document/literal - error processing operation with 2 arguments
> ---------------------------------------------------------------------------------
>
> Key: AXIS-2055
> URL: http://issues.apache.org/jira/browse/AXIS-2055
> Project: Apache Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: java full version "1.4.2_01-b06"
> Reporter: Ephemeris Lappis
> Attachments: axis3.wsdl, deploy.wsdd, http-request.txt, http-response.txt, server-error.txt
>
> It seems an axis internal error occurs on the server side, using document/literal style, when processing an operation with the following signature :
> public int testIntegerPairToInteger(int i1, int i2)
> The wsdl and wsdd files that are attached seem ok for me, and the sent request too.
> The error trace on the server side is also attached.
> Just for information, the same operation is processed without any problem in both wrapped and document styles...
> I've done another test with an operation like
> CustomeType operation(CustomeType v1, CustomeType v2)
> And it seems the problem is similar. No error is produced, but the server class only receives the first parameter, the second one is always null.
> The http request seems ok :
> POST /axis3/services/TestServicePort HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.2 Host: 127.0.0.1:81 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 689 <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <in13 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>13.0</doubleProperty>
> <integerProperty>11</integerProperty>
> <longProperty>12</longProperty>
> <stringProperty>a</stringProperty>
> </in13>
> <in14 xmlns="urn:axis-test3">
> <booleanProperty>true</booleanProperty>
> <doubleProperty>23.0</doubleProperty>
> <integerProperty>21</integerProperty>
> <longProperty>22</longProperty>
> <stringProperty>b</stringProperty>
> </in14>
> </soapenv:Body>
> </soapenv:Envelope>
> And the wsdd extract too :
> <operation name="testFlatBeanPairToFlatBean" qname="testFlatBeanPairToFlatBean" returnQName="retNS:testFlatBeanPairToFlatBeanReturn" xmlns:retNS="urn:axis-test3" returnType="rtns:FlatBean" xmlns:rtns="urn:axis-test3" soapAction="" >
> <parameter qname="pns:in13" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> <parameter qname="pns:in14" xmlns:pns="urn:axis-test3" type="tns:FlatBean" xmlns:tns="urn:axis-test3"/>
> </operation>
> But the server class always receives null for the second parameter...
> See the attachments...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira