[ 
http://issues.apache.org/jira/browse/WODEN-1?page=comments#action_12369109 ] 

Lawrence Mandel commented on WODEN-1:
-------------------------------------

I've created a workaround for this issue. I'm calling it a workaround because 
it requires reading the schema for schema for every model creation and will 
only work when reading an existing WSDL document (as opposed to creating one 
programmatically). I'm going to leave this issue open until this is properly 
resolved but the reported problem should function properly in M4.

> element attr of interface->input can contain a type and no validation error 
> is reported
> ---------------------------------------------------------------------------------------
>
>          Key: WODEN-1
>          URL: http://issues.apache.org/jira/browse/WODEN-1
>      Project: Woden
>         Type: Bug
>  Environment: J2SE 1.4.2
>     Reporter: Jeremy Hughes
>     Assignee: Lawrence Mandel
>     Priority: Minor

>
> This WSDL [1] has the following:
>         
>     <wsdl:interface name="EchoInterface">
>         <wsdl:operation name="Echo" 
> pattern="http://www.w3.org/2005/08/wsdl/in-out";>
>             <wsdl:input element="xs:string"/>
>             <wsdl:output element="xs:string"/>
>         </wsdl:operation>
>     </wsdl:interface>
> According to the spec [2], the element attribute value must resolve to an 
> element declaration from the element declarations of the Description. 
> xs:string isn't such an element as it is a simple type defined in XML schema 
> [3]
> [1] 
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/documents/bad/Service-1B/Service.wsdl
> [2] 
> http://www.w3.org/TR/2005/WD-wsdl20-20050803/#InterfaceMessageReference_Mapping
> [3] http://www.w3.org/2001/XMLSchema.xsd

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to