[ 
https://issues.apache.org/jira/browse/WODEN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523942
 ] 

John Kaputin commented on WODEN-162:
------------------------------------

r571310
Committed Dan's patch after applying a few changes:

* Changed QNameTokenUnion  so that it can only represent a qname or tokens 
#any, #none, #other (removed default ctor, made the string ctor private and 
introduced static finals to represent the 3 token types).

* Modified the implementation and testcases to match the above change.

* Changed the interface fault and interface message reference test cases to:
- instantiate the WSDL object model via the correct Woden API (the original 
code prior to this JIRA was calling impl ctors directly).
- changed some test methods so that they match the corresponding API methods 
and added //TODO comments for the testGetXmlSchemaElement methods, which still 
require XmlSchema objects to be added to the TypesElement.


> parser does not handle faults with element="#any" etc.
> ------------------------------------------------------
>
>                 Key: WODEN-162
>                 URL: https://issues.apache.org/jira/browse/WODEN-162
>             Project: Woden
>          Issue Type: Bug
>          Components: Parser
>    Affects Versions: M7a
>            Reporter: Jacek Kopecky
>            Assignee: Dan Harvey
>            Priority: Minor
>             Fix For: M8
>
>         Attachments: Woden-162.patch.txt
>
>
> similarly to interface message references, interface faults have {message 
> content model} property, i.e. the "element" attribute can have values "#any", 
> "#none" or "#other", or none at all which is equal to "#other"; the 
> parseInterfaceMessageReference method does the right thing, but the 
> parseInterfaceFault method only expects a qname.
> to test, just put element="#any" on a fault, instead of pointing to a qname.

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


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

Reply via email to