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

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

InterfaceMessageReferenceElement supports these tokens via the method 
getMessageContentModel. However, {message content model} is a component model 
property and should only be represented on the Component API, not the Element 
API (WODEN-136 will remove this method from InterfaceMessageReferenceElement). 
We need another way to represent the 'element' infoset attribute on the Element 
API (that is, for both InterfaceMessageReferenceElement and 
InterfaceFaultElement), given that its type is the union of xsQName and 
xs:Token values #any, #none and #other.

We already have get/setElement and get/setElementName methods to handle the 
case where 'element' contains an xs:QName. Perhaps we could add 
get/setElementToken methods and maybe a boolean method isElementToken(). 
Alternatively, we need a new type to represent the union.

> 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: John Kaputin
>            Priority: Minor
>             Fix For: M8
>
>
> 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