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 "Dan Armbrust (JIRA)" <ax...@ws.apache.org> on 2005/05/27 22:37:54 UTC
[jira] Created: (AXIS-2021) String Array Regression causes SAXException: Found character data ...
String Array Regression causes SAXException: Found character data ...
---------------------------------------------------------------------
Key: AXIS-2021
URL: http://issues.apache.org/jira/browse/AXIS-2021
Project: Axis
Type: Bug
Components: Serialization/Deserialization
Versions: 1.2
Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
Client - Axis running on Java 1.4.2_05 On Window XP SP2
Reporter: Dan Armbrust
Priority: Blocker
This seems to be a serious regression bug... But maybe I'm doing something wrong...
I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
Here is the error:
org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
Here is the message that it choked on:
<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>
<getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
<getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
<getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
<getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
<getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
</getSupportedMatchAlgorithmsResponse>
</soapenv:Body>
</soapenv:Envelope>
What it is supposed to be returning is a simple String[].
A snippit from the wsdl file:
<element name="getSupportedMatchAlgorithms">
<complexType/>
</element>
<element name="getSupportedMatchAlgorithmsResponse">
<complexType>
<sequence>
<element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
</sequence>
</complexType>
</element>
So I don't know why that ArrayOf_xsd_string gunk is in the response.
My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Dan Armbrust (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12313296 ]
Dan Armbrust commented on AXIS-2021:
------------------------------------
Verified fix in todays daily build. Thank you very much for fixing this!
Dan
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl, java.zip
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Dan Armbrust (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12313199 ]
Dan Armbrust commented on AXIS-2021:
------------------------------------
Ok, I just verified that your suggestion fixes the problem.
In the parameters, I changed all my patterns of
<element maxOccurs="unbounded" name="properties" type="xsd:string"/>
to this
<element name="properties" nillable="true" type="impl:ArrayOf_xsd_string"/>
And it works correctly. Then I discovered that the same bug affects things that return a simple String [] as well - the 1.2.1 daily build was generated this snippit of code (from the VocabBrower.wsdl attached to this bug)
<element name="getSupportedMatchAlgorithmsResponse">
<complexType>
<sequence>
<element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
</sequence>
</complexType>
</element>
I changed this to
<element name="getSupportedMatchAlgorithmsResponse">
<complexType>
<sequence>
<element name="getSupportedMatchAlgorithmsReturn" nillable="true" type="impl:ArrayOf_xsd_string"/>
</sequence>
</complexType>
</element>
And now that works as well. Thank you very much for tracking this down - at least now I know how to hack it if necessary, so I can start using the 1.2.1 release - even if the proper fix doesn't make it into the java2wsdl tool in time.
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl, java.zip
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Dan Armbrust (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_66755 ]
Dan Armbrust commented on AXIS-2021:
------------------------------------
Correct, this WSDL was generated using the -y WRAPPED option.
Here is the ant debug output of the actual command (ignore the [java] stuff):
[echo] Generating build/wsdl/VocabBrowser.wsdl from org.hl7.CTSVAPI.BrowserOperations
[java] Executing 'C:\Program Files\Java\j2sdk_1.4.2_05\jre\bin\java.exe' with arguments:
[java] '-classpath'
[java] 'C:\Eclipse Projects\general-workspace\CTS\hl7spec\build\idljava\classes;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\xerces.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\xml-apis.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\build\lib\ctsImpl.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\CTSUtility.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\build\wsdljava\classes;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\activation.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\axis-ant.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\axis.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\commons-discovery-0.2.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\commons-logging-1.0.4.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\jaxrpc.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\log4j-1.2.8.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\mail.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\saaj.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\wsdl4j-1.5.1.jar'
[java] 'org.apache.axis.wsdl.Java2WSDL'
[java] '-o'
[java] 'build/wsdl/VocabBrowser.wsdl'
[java] '-n'
[java] 'urn://hl7.org/CTSVAPI'
[java] '-i'
[java] 'org.hl7.CTSVAPI.refImpl.BrowserOperationsImpl'
[java] '-lhttp://localhost:8080/axis/services/VocabBrowserService'
[java] '-porg.hl7.cts.types=urn://cts.hl7.org/types'
[java] '-porg.hl7.CTSMAPI=urn://hl7.org/CTSMAPI'
[java] '-porg.hl7.CTSVAPI=urn://hl7.org/CTSVAPI'
[java] '-y'
[java] 'WRAPPED'
[java] 'org.hl7.CTSVAPI.BrowserOperations'
[java]
[java] The ' characters around the executable and arguments are
[java] not part of the command.
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12313189 ]
Davanum Srinivas commented on AXIS-2021:
----------------------------------------
Please replace the following 2 lines:
<element maxOccurs="unbounded" name="properties" type="xsd:string"/>
<element maxOccurs="unbounded" name="mimeTypes" type="xsd:string"/>
with the following:
<element name="properties" nillable="true" type="impl:ArrayOf_xsd_string"/>
<element name="mimeTypes" nillable="true" type="impl:ArrayOf_xsd_string"/>
And it works fine. Bug is in the Java2WSDL code. So i'll need more info from you. example the java code for lookupConceptCodesByProperty and RelatedCode...since both have arrays of string and RelatedCode's complexType looks fine.
thanks,
dims
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Dan Armbrust (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=all ]
Dan Armbrust updated AXIS-2021:
-------------------------------
Attachment: VocabBrowser.wsdl
Updated WSDL as generated by the daily build of axis.
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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: question related to WSIF and Axis
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
I would consider that a bug that needs to be fixed .. this is sort of
related to the recent thread on general@ws.apache.org related to moving
WSDL2* code out of Axis(2) and to a ws-commons project to enable clean
extension of WSDL2* by various WS projects.
Sanjiva.
On Fri, 2005-06-10 at 20:02 -0700, Shantanu Sen wrote:
> Currently, if I have a WSDL with a non-soap binding
> (e.g. ejb/jms binding), WSDL2Java does not produce the
> service interface correctly. Note that it correctly
> generates the java types specified in the types
> section of the WSDL, but the portType interface is not
> generated.
>
> My question was regarding the portType generation.
>
> Shantanu
>
> --- Paul Fremantle <pz...@gmail.com> wrote:
>
> > WSIF should work with the JAX-RPC interfaces that
> > WSDL2Java creates.
> >
> > As Sanjiva says, the bindings shouldn't affect the
> > interface.
> >
> > Paul
> >
> > On 6/10/05, Sanjiva Weerawarana
> > <sa...@opensource.lk> wrote:
> > > I doubt that kind of work being done on the 1.2.x
> > path at this point ..
> > >
> > > For Axis2, I'd like to look at doing a WSIF2 on
> > top of AXIOM. However,
> > > I'm not clear why that WSIF affects the
> > types/interfaces - the WSIF
> > > binding details go inside the stub. What I'm
> > suggesting is that with
> > > AXIOM we now have a universal way to propagate
> > data inside WSIF
> > > (essentially to re-do WSIFMessage). We did this a
> > while back with
> > > something called JROM, but JROM never made it out
> > of AlphaWorks due to
> > > IBM change of heart.
> > >
> > > Sanjiva.
> > >
> > > On Thu, 2005-06-09 at 17:47 -0700, Shantanu Sen
> > wrote:
> > > > Is there any plan to augment WSDL2Java so that
> > it can
> > > > understand and generate types/interfaces for
> > WSDL that
> > > > contains (non-SOAP) binding extensions as
> > defined by
> > > > WSIF e.g. ejb, jms etc?
> > > >
> > > > I am asking this question in the context of both
> > Axis
> > > > 1.2.x and Axis 2.
> > > >
> > > > Thanks,
> > > > Shantanu Sen
> > > >
> > >
> > >
> >
>
>
Re: question related to WSIF and Axis
Posted by Shantanu Sen <ss...@pacbell.net>.
Currently, if I have a WSDL with a non-soap binding
(e.g. ejb/jms binding), WSDL2Java does not produce the
service interface correctly. Note that it correctly
generates the java types specified in the types
section of the WSDL, but the portType interface is not
generated.
My question was regarding the portType generation.
Shantanu
--- Paul Fremantle <pz...@gmail.com> wrote:
> WSIF should work with the JAX-RPC interfaces that
> WSDL2Java creates.
>
> As Sanjiva says, the bindings shouldn't affect the
> interface.
>
> Paul
>
> On 6/10/05, Sanjiva Weerawarana
> <sa...@opensource.lk> wrote:
> > I doubt that kind of work being done on the 1.2.x
> path at this point ..
> >
> > For Axis2, I'd like to look at doing a WSIF2 on
> top of AXIOM. However,
> > I'm not clear why that WSIF affects the
> types/interfaces - the WSIF
> > binding details go inside the stub. What I'm
> suggesting is that with
> > AXIOM we now have a universal way to propagate
> data inside WSIF
> > (essentially to re-do WSIFMessage). We did this a
> while back with
> > something called JROM, but JROM never made it out
> of AlphaWorks due to
> > IBM change of heart.
> >
> > Sanjiva.
> >
> > On Thu, 2005-06-09 at 17:47 -0700, Shantanu Sen
> wrote:
> > > Is there any plan to augment WSDL2Java so that
> it can
> > > understand and generate types/interfaces for
> WSDL that
> > > contains (non-SOAP) binding extensions as
> defined by
> > > WSIF e.g. ejb, jms etc?
> > >
> > > I am asking this question in the context of both
> Axis
> > > 1.2.x and Axis 2.
> > >
> > > Thanks,
> > > Shantanu Sen
> > >
> >
> >
>
Re: question related to WSIF and Axis
Posted by Paul Fremantle <pz...@gmail.com>.
WSIF should work with the JAX-RPC interfaces that WSDL2Java creates.
As Sanjiva says, the bindings shouldn't affect the interface.
Paul
On 6/10/05, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> I doubt that kind of work being done on the 1.2.x path at this point ..
>
> For Axis2, I'd like to look at doing a WSIF2 on top of AXIOM. However,
> I'm not clear why that WSIF affects the types/interfaces - the WSIF
> binding details go inside the stub. What I'm suggesting is that with
> AXIOM we now have a universal way to propagate data inside WSIF
> (essentially to re-do WSIFMessage). We did this a while back with
> something called JROM, but JROM never made it out of AlphaWorks due to
> IBM change of heart.
>
> Sanjiva.
>
> On Thu, 2005-06-09 at 17:47 -0700, Shantanu Sen wrote:
> > Is there any plan to augment WSDL2Java so that it can
> > understand and generate types/interfaces for WSDL that
> > contains (non-SOAP) binding extensions as defined by
> > WSIF e.g. ejb, jms etc?
> >
> > I am asking this question in the context of both Axis
> > 1.2.x and Axis 2.
> >
> > Thanks,
> > Shantanu Sen
> >
>
>
Re: question related to WSIF and Axis
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
I doubt that kind of work being done on the 1.2.x path at this point ..
For Axis2, I'd like to look at doing a WSIF2 on top of AXIOM. However,
I'm not clear why that WSIF affects the types/interfaces - the WSIF
binding details go inside the stub. What I'm suggesting is that with
AXIOM we now have a universal way to propagate data inside WSIF
(essentially to re-do WSIFMessage). We did this a while back with
something called JROM, but JROM never made it out of AlphaWorks due to
IBM change of heart.
Sanjiva.
On Thu, 2005-06-09 at 17:47 -0700, Shantanu Sen wrote:
> Is there any plan to augment WSDL2Java so that it can
> understand and generate types/interfaces for WSDL that
> contains (non-SOAP) binding extensions as defined by
> WSIF e.g. ejb, jms etc?
>
> I am asking this question in the context of both Axis
> 1.2.x and Axis 2.
>
> Thanks,
> Shantanu Sen
>
question related to WSIF and Axis
Posted by Shantanu Sen <ss...@pacbell.net>.
Is there any plan to augment WSDL2Java so that it can
understand and generate types/interfaces for WSDL that
contains (non-SOAP) binding extensions as defined by
WSIF e.g. ejb, jms etc?
I am asking this question in the context of both Axis
1.2.x and Axis 2.
Thanks,
Shantanu Sen
[jira] Commented: (AXIS-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12313204 ]
Davanum Srinivas commented on AXIS-2021:
----------------------------------------
Tom,
yes, you are right...a .NET client with the original wsdl works fine with the server-side code generated from the original wsdl. So the problem is out array serializer. Here is the bad soap message from our client. See the extra xsi:type stuff...if we get rid of it, then all's well.
-- dims
<?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>
<lookupConceptCodesByProperty xmlns="urn:hl7.org/CTSVAPI">
<codeSystem_id>2.16.840.1.113883.5.4</codeSystem_id>
<matchText>TEXT</matchText>
<matchAlgorithm_code>StartsWithIgnoreCase</matchAlgorithm_code>
<language_code>en</language_code>
<activeConceptsOnly>true</activeConceptsOnly>
<properties xsi:type="ns1:ArrayOf_xsd_string" xmlns:ns1="urn:hl7.org/CTSVAPI">textualPresentation1</properties>
<properties>textualPresentation2</properties>
<properties>textualPresentation3</properties>
<properties>textualPresentation4</properties>
<mimeTypes xsi:type="ns2:ArrayOf_xsd_string" xmlns:ns2="urn:hl7.org/CTSVAPI">A</mimeTypes>
<mimeTypes>B</mimeTypes>
<mimeTypes>C</mimeTypes>
<timeout>0</timeout>
<sizeLimit>10</sizeLimit>
</lookupConceptCodesByProperty>
</soapenv:Body>
</soapenv:Envelope>
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl, java.zip
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Dan Armbrust (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12312751 ]
Dan Armbrust commented on AXIS-2021:
------------------------------------
I just tested with yesterdays daily build (6/5/05) and I am happy to report that there is progress. It no longer breaks on simple string returns. However, now I am seeing it break when the client code tries to submit a String[] of parameters.
When I call my method "lookupConceptCodesByProperty" - with one item in the "properties" parameter - the following request is submitted:
<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>
<lookupConceptCodesByProperty xmlns="urn://hl7.org/CTSVAPI">
<codeSystem_id>2.16.840.1.113883.5.4</codeSystem_id>
<matchText />
<matchAlgorithm_code>StartsWithIgnoreCase</matchAlgorithm_code>
<language_code>en</language_code>
<activeConceptsOnly>true</activeConceptsOnly>
<properties xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">textualPresentation</properties>
<mimeTypes xsi:nil="true" />
<timeout>0</timeout>
<sizeLimit>10</sizeLimit>
</lookupConceptCodesByProperty>
</soapenv:Body>
</soapenv:Envelope>
And here is the response from the server:
<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>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>org.xml.sax.SAXException: Found character data inside an array element while deserializing</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">mir04</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
If I change my parameters, such that I don't submit any "properties" items, then the request looks like this:
<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>
<lookupConceptCodesByProperty xmlns="urn://hl7.org/CTSVAPI">
<codeSystem_id>2.16.840.1.113883.5.4</codeSystem_id>
<matchText />
<matchAlgorithm_code>StartsWithIgnoreCase</matchAlgorithm_code>
<language_code>en</language_code>
<activeConceptsOnly>true</activeConceptsOnly>
<properties xsi:nil="true" />
<mimeTypes xsi:nil="true" />
<timeout>0</timeout>
<sizeLimit>10</sizeLimit>
</lookupConceptCodesByProperty>
</soapenv:Body>
</soapenv:Envelope>
And it works correctly.
So the bug seems to be fixed, as far as the server returning correctly encoded arrays, and the client parses them correctly. But something remains broken with the client submitting arrays of parameters to the server.
Here are snippits of the WSDL generated with this build:
<element name="lookupConceptCodesByProperty">
<complexType>
<sequence>
<element name="codeSystem_id" type="xsd:string"/>
<element name="matchText" type="xsd:string"/>
<element name="matchAlgorithm_code" type="xsd:string"/>
<element name="language_code" type="xsd:string"/>
<element name="activeConceptsOnly" type="xsd:boolean"/>
<element maxOccurs="unbounded" name="properties" type="xsd:string"/>
<element maxOccurs="unbounded" name="mimeTypes" type="xsd:string"/>
<element name="timeout" type="xsd:int"/>
<element name="sizeLimit" type="xsd:int"/>
</sequence>
</complexType>
</element>
<element name="lookupConceptCodesByPropertyResponse">
<complexType>
<sequence>
<element maxOccurs="unbounded" name="lookupConceptCodesByPropertyReturn" type="impl:ConceptId"/>
</sequence>
</complexType>
</element>
I'll attach the full WSDL as generated by Axis.
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_66743 ]
Davanum Srinivas commented on AXIS-2021:
----------------------------------------
Just to confirm, Is this the WSDL generated by java2wsdl tool, using the "-y WRAPPED" option in your build process?
thanks,
dims
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12313211 ]
Davanum Srinivas commented on AXIS-2021:
----------------------------------------
Checked in a fix to prevent the bad xsi:type showing up on the wire. Please use your original WSDL and try latest nightly / CVS
thanks,
dims
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl, java.zip
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_66551 ]
Davanum Srinivas commented on AXIS-2021:
----------------------------------------
Please upload the complete WSDL
thanks,
dims
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Dan Armbrust (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12313191 ]
Dan Armbrust commented on AXIS-2021:
------------------------------------
Thank you for your research - I will try the manual fix you metioned above today.
The code that I run the Java2WSDL program on is actually code that is output by a IDL -> Java converter (to complicate things even more)
Here are the parts of the class that I believe you are interested in:
public interface BrowserOperations extends org.hl7.CTSVAPI.IdentificationOperations
{
....
org.hl7.CTSVAPI.ConceptId[] lookupConceptCodesByProperty (String codeSystem_id, String matchText, String matchAlgorithm_code, String language_code, boolean activeConceptsOnly, String[] properties, String[] mimeTypes, int timeout, int sizeLimit) throws org.hl7.CTSVAPI.UnknownCodeSystem, org.hl7.CTSVAPI.BadlyFormedMatchText, org.hl7.CTSVAPI.UnknownMatchAlgorithm, org.hl7.CTSVAPI.UnknownLanguageCode, org.hl7.CTSVAPI.UnknownPropertyCode, org.hl7.CTSVAPI.UnknownMimeTypeCode, org.hl7.CTSVAPI.TimeoutError, org.hl7.CTSVAPI.UnexpectedError;
....
org.hl7.CTSVAPI.ConceptProperty[] lookupProperties (org.hl7.CTSVAPI.ConceptId concept_id, String[] properties, String matchText, String matchAlgorithm_code, String language_code, String[] mimeTypes) throws org.hl7.CTSVAPI.UnknownCodeSystem, org.hl7.CTSVAPI.UnknownConceptCode, org.hl7.CTSVAPI.BadlyFormedMatchText, org.hl7.CTSVAPI.UnknownLanguageCode, org.hl7.CTSVAPI.UnknownPropertyCode, org.hl7.CTSVAPI.UnknownMatchAlgorithm, org.hl7.CTSVAPI.UnknownMimeTypeCode, org.hl7.CTSVAPI.UnexpectedError;
}
I can zip up the entire java package of code, and attach it if you would like.
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Dan Armbrust (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=all ]
Dan Armbrust updated AXIS-2021:
-------------------------------
Attachment: VocabBrowser.wsdl
WSDL (as generated by Axis)
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Tom Jordahl (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12313202 ]
Tom Jordahl commented on AXIS-2021:
-----------------------------------
An maxOccurrs=unbounded string array should work from WSDL. That is doesn't is a pretty big bug. :-(
The ArrayOf stuff is ugly and we should be depending on typ mappings for that to recognize these simple structures.
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl, java.zip
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Dan Armbrust (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12312758 ]
Dan Armbrust commented on AXIS-2021:
------------------------------------
I believe this is the same issue as http://issues.apache.org/jira/browse/AXIS-1883
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Dan Armbrust (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=all ]
Dan Armbrust updated AXIS-2021:
-------------------------------
Attachment: java.zip
This is the entire java package that I use when I am generating the WSDL. I probably errored on the side of including more classes than necessary - I believe that you can dis-regaurd the entire MAPI package.
The command that I use to generate the WSDL from this is in an earlier comment.
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl, java.zip
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12313194 ]
Davanum Srinivas commented on AXIS-2021:
----------------------------------------
yes please.
thanks,
dims
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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] Resolved: (AXIS-2021) String Array Regression causes SAXException: Found character data ...
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2021?page=all ]
Davanum Srinivas resolved AXIS-2021:
------------------------------------
Resolution: Fixed
Fixed in CVS / Nightly
> String Array Regression causes SAXException: Found character data ...
> ---------------------------------------------------------------------
>
> Key: AXIS-2021
> URL: http://issues.apache.org/jira/browse/AXIS-2021
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2
> Environment: Server - Tomcat 5.0.25 on Java 1.4.2_01 on Fedora Core 3
> Client - Axis running on Java 1.4.2_05 On Window XP SP2
> Reporter: Dan Armbrust
> Priority: Blocker
> Attachments: VocabBrowser.wsdl, VocabBrowser.wsdl, java.zip
>
> This seems to be a serious regression bug... But maybe I'm doing something wrong...
> I was using 1.2 RC2, and everything was working for me. Now under 1.2 final, the handling of arrays appears broken.
> Here is the error:
> org.apache.axis.AxisFaultorg.xml.sax.SAXException: Found character data inside an array element while deserializing
> Here is the message that it choked on:
> <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>
> <getSupportedMatchAlgorithmsResponse xmlns="urn://hl7.org/CTSVAPI">
> <getSupportedMatchAlgorithmsReturn xmlns:ns1="urn://hl7.org/CTSVAPI" xsi:type="ns1:ArrayOf_xsd_string">IdenticalIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>StartsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>EndsWithIgnoreCase</getSupportedMatchAlgorithmsReturn>
> <getSupportedMatchAlgorithmsReturn>ContainsPhraseIgnoreCase</getSupportedMatchAlgorithmsReturn>
> </getSupportedMatchAlgorithmsResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> What it is supposed to be returning is a simple String[].
> A snippit from the wsdl file:
> <element name="getSupportedMatchAlgorithms">
> <complexType/>
> </element>
> <element name="getSupportedMatchAlgorithmsResponse">
> <complexType>
> <sequence>
> <element maxOccurs="unbounded" name="getSupportedMatchAlgorithmsReturn" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
> So I don't know why that ArrayOf_xsd_string gunk is in the response.
> My build process is kind of complicated - my initial definition of the API is in IDL. The idl is compiled into Java. Then, my WSDL is generated by the java2wsdl tool, using the "-y WRAPPED" option.
> Then, I generate java using wsdl2java tool - and I implement my API using the resulting java classes. One thing that I noted here, was that 1.2 rc2 generated "ArrayOf_X" classes for each array object, while 1.2 final does not generate any ArrayOf_X classes.
> Finally I install the code into my Axis server, and try it out. I can call most of the methods in my API - but anything that returns an a String Array throws the SAXException (as noted above) while trying to parse the response, which has stuff in it it shouldn't.
> Dan
--
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