[ 
https://issues.apache.org/jira/browse/CXF-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536296
 ] 

Daniel Kulp commented on CXF-1116:
----------------------------------


I can work on this on Monday, but need some help from the Aegis experts as to 
what people think it SHOULD look like.

Should it look like what JAXB generates:
<xsd:sequence> 
   <xsd:element maxOccurs="unbounded" minOccurs="0" name="return" 
type="xsd:string" /> 
</xsd:sequence>

Or should it look like what Aegis does with collections:
<xsd:sequence> 
   <xsd:element name="return" type="tns:ArrayOfString"/> 
</xsd:sequence>

Either one looks non-trivial to do.   The first mapping would require a lot 
more work in the Aegis databinding.    The second mapping would require a bit 
of work in the ReflectionServiceFactoryBean and some flags passed between it 
and the databinding.



> 1-dimentional arrays appear as 2-dimentional in the wsdl
> --------------------------------------------------------
>
>                 Key: CXF-1116
>                 URL: https://issues.apache.org/jira/browse/CXF-1116
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: Tawfik Lachheb
>            Priority: Blocker
>
> We are trying to publish interfaces using the simple frontend with aegis.  We 
> are seeing that any method that returns an array does not appear correctly in 
> the wsdl.  For example, if a method returns a String[], the return appears in 
> the wsdl as:
>   <xsd:sequence>
>   <xsd:element maxOccurs="unbounded" minOccurs="0" name="return" 
> type="tns:ArrayOfString" /> 
>   </xsd:sequence>
> which represents a 2-dimentional array because of the maxOccurs="unbounded".
> This is a show-stopper for us.  If a fix is made, we are willing to use a 
> snapshot build until a release happens.
> Thanks

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to