You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Lin Sun (JIRA)" <ji...@apache.org> on 2007/04/13 05:43:15 UTC
[jira] Created: (GERONIMO-3097) Axis2:
ParameterDescriptionComposite still isn't built correctly
Axis2: ParameterDescriptionComposite still isn't built correctly
----------------------------------------------------------------
Key: GERONIMO-3097
URL: https://issues.apache.org/jira/browse/GERONIMO-3097
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: webservices
Affects Versions: 2.0-M5
Reporter: Lin Sun
Fix For: 2.0-M5
Dims, the fact that java.lang.ArrayIndexOutOfBoundsException happened (the one you fixed tonite) indicated we aren't building the ParameterDescriptionComposite correctly. I think we are building fine for simple cases where the complexType tag is inside of the element tag, like our calculator example or greetme example.
<xsd:element name="add">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value1" type="xsd:int"/>
<xsd:element name="value2" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
However, we aren't handling these ComplexType that don't sit inside of element tag correctly. For example:
<xsd:complexType name="product">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="description" type="xsd:string"/>
<xsd:element name="price" type="xsd:double"/>
<xsd:element name="SKU" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
I tried to step through such a wsdl file and the java method has only 1 parameter, but we are building 4 ParameterDescriptionComposites for it. I don't understand the above ComplextType well so if anyone has such an example with java source that would be great (the one I have doesnt have source).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3097) Axis2: ParameterDescriptionComposite
still isn't built correctly
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun closed GERONIMO-3097.
-----------------------------
close issue
> Axis2: ParameterDescriptionComposite still isn't built correctly
> ----------------------------------------------------------------
>
> Key: GERONIMO-3097
> URL: https://issues.apache.org/jira/browse/GERONIMO-3097
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.0-M5
> Reporter: Lin Sun
> Fix For: 2.0-M5
>
>
> Dims, the fact that java.lang.ArrayIndexOutOfBoundsException happened (the one you fixed tonite) indicated we aren't building the ParameterDescriptionComposite correctly. I think we are building fine for simple cases where the complexType tag is inside of the element tag, like our calculator example or greetme example.
> <xsd:element name="add">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="value1" type="xsd:int"/>
> <xsd:element name="value2" type="xsd:int"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> However, we aren't handling these ComplexType that don't sit inside of element tag correctly. For example:
> <xsd:complexType name="product">
> <xsd:sequence>
> <xsd:element name="name" type="xsd:string"/>
> <xsd:element name="description" type="xsd:string"/>
> <xsd:element name="price" type="xsd:double"/>
> <xsd:element name="SKU" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> I tried to step through such a wsdl file and the java method has only 1 parameter, but we are building 4 ParameterDescriptionComposites for it. I don't understand the above ComplextType well so if anyone has such an example with java source that would be great (the one I have doesnt have source).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3097) Axis2:
ParameterDescriptionComposite still isn't built correctly
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun resolved GERONIMO-3097.
-------------------------------
Resolution: Fixed
I think this has been resolved with http://svn.apache.org/viewvc?view=rev&rev=528929 and http://svn.apache.org/viewvc?view=rev&rev=529376
> Axis2: ParameterDescriptionComposite still isn't built correctly
> ----------------------------------------------------------------
>
> Key: GERONIMO-3097
> URL: https://issues.apache.org/jira/browse/GERONIMO-3097
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.0-M5
> Reporter: Lin Sun
> Fix For: 2.0-M5
>
>
> Dims, the fact that java.lang.ArrayIndexOutOfBoundsException happened (the one you fixed tonite) indicated we aren't building the ParameterDescriptionComposite correctly. I think we are building fine for simple cases where the complexType tag is inside of the element tag, like our calculator example or greetme example.
> <xsd:element name="add">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="value1" type="xsd:int"/>
> <xsd:element name="value2" type="xsd:int"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> However, we aren't handling these ComplexType that don't sit inside of element tag correctly. For example:
> <xsd:complexType name="product">
> <xsd:sequence>
> <xsd:element name="name" type="xsd:string"/>
> <xsd:element name="description" type="xsd:string"/>
> <xsd:element name="price" type="xsd:double"/>
> <xsd:element name="SKU" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> I tried to step through such a wsdl file and the java method has only 1 parameter, but we are building 4 ParameterDescriptionComposites for it. I don't understand the above ComplextType well so if anyone has such an example with java source that would be great (the one I have doesnt have source).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.