cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jmi (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CXF-918) java code from wsdl2java for wrapped style if request and response have elements with the same names and different datatypes
Date Fri, 17 Aug 2007 15:18:30 GMT

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

jmi edited comment on CXF-918 at 8/17/07 8:17 AM:
--------------------------------------------------

I have question. I prefer solution, if generated code contains also wrapped classes - only
one input parameter for input and return type for output.
What should configure to have such output?

ok .. i found an anwer:
add 
	  <jaxws:bindings xmlns:jaxws="http://java.sun.com/xml/ns/jaxws">
	      <jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>
  	</jaxws:bindings>
to wsdl:porttype.


Is it ok, that the same block of configuration doesn't have effect when it's directly in wsdl:definitions
 ?

      was (Author: jmi):
    I have question. I prefer solution, if generated code contains also wrapped classes -
only one input parameter for input and return type for output.
What should configure to have such output?

thanks
regards
jmi
  
> java code from wsdl2java for wrapped style if request and response have elements with
the same names and different datatypes
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-918
>                 URL: https://issues.apache.org/jira/browse/CXF-918
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 2.0.1, 2.1
>         Environment: java 1.5.0_09
>            Reporter: jmi
>         Attachments: bug.wsdl
>
>
> wsdl2java renegares incorrect java code for some wsdls:
> wsdl uses "wrapped style" - request and response messages for operation, both have only
one message-part. Each element referenced from message-part has different compex type, where
both have multiple elements. 
> Problem is if there are two elements, one in request, one in response datatype, where
both have the same name, but they have different datatype. In such situation a Holder is generated,
which holds dataype from response. Request parameter is lost.
> maybe reason is common with bug 907

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


Mime
View raw message