[#WODEN-136] Message content model should not be represented in the Element API

Woden

Message content model should not be represented in the Element API

Created: 06/Feb/07 01:38 AM Updated: 31/Aug/07 10:07 PM

Return to search

Component/s:

Parser

Affects Version/s:

None

Fix Version/s:

Time Tracking:

Not Specified

Resolution Date:

31/Aug/07 10:07 PM

Description

« Hide

{message content model} is a property of the InterfaceMessageReference component. It does not map directly to the WSDL 2.0 infoset. So the set/getMessageContentModel methods currently defined on the InterfaceMessageReferenceElement interface should not be part of the Element API at all. This property should only be represented in the Component API, via InterfaceMessageReference.

These two methods should be removed from the Element API for M7 or at least deprecated for M7 and removed for M8.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

John Kaputin added a comment - 15/Aug/07 12:47 PM

This is related to ~~WODEN-136~~. See comments there about adding new methods to Element API to handle the type 'union of xs:QName and xs:Token #any, #none, #other'.

[ Permlink | « Hide ]

Dan Harvey added a comment - 15/Aug/07 03:17 PM

I think you meant related to ~~WODEN-162~~ not itself.

[ Permlink | « Hide ]

Dan Harvey added a comment - 21/Aug/07 02:53 PM

The fix for this Jira is included in ~~WODEN-162~~ as there was a lot of change overlap with that Jira.

[ Permlink | « Hide ]

John Kaputin added a comment - 31/Aug/07 10:07 PM

This has been fixed via ~~WODEN-162~~,