You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by "John Kaputin (JIRA)" <ji...@apache.org> on 2007/02/06 02:40:06 UTC
[jira] Created: (WODEN-136) Message content model should not be
represented in the Element API
Message content model should not be represented in the Element API
------------------------------------------------------------------
Key: WODEN-136
URL: https://issues.apache.org/jira/browse/WODEN-136
Project: Woden
Issue Type: Bug
Components: Parser
Reporter: John Kaputin
Fix For: M8
{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.
--
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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
[jira] Commented: (WODEN-136) Message content model should not be
represented in the Element API
Posted by "Dan Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WODEN-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519996 ]
Dan Harvey commented on WODEN-136:
----------------------------------
I think you meant related to WODEN-162 not itself.
> Message content model should not be represented in the Element API
> ------------------------------------------------------------------
>
> Key: WODEN-136
> URL: https://issues.apache.org/jira/browse/WODEN-136
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Reporter: John Kaputin
> Assignee: Dan Harvey
> Fix For: M8
>
>
> {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.
--
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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
[jira] Assigned: (WODEN-136) Message content model should not be
represented in the Element API
Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WODEN-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Kaputin reassigned WODEN-136:
----------------------------------
Assignee: John Kaputin
> Message content model should not be represented in the Element API
> ------------------------------------------------------------------
>
> Key: WODEN-136
> URL: https://issues.apache.org/jira/browse/WODEN-136
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Reporter: John Kaputin
> Assignee: John Kaputin
> Fix For: M8
>
>
> {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.
--
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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
[jira] Assigned: (WODEN-136) Message content model should not be
represented in the Element API
Posted by "Dan Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WODEN-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Harvey reassigned WODEN-136:
--------------------------------
Assignee: Dan Harvey (was: John Kaputin)
> Message content model should not be represented in the Element API
> ------------------------------------------------------------------
>
> Key: WODEN-136
> URL: https://issues.apache.org/jira/browse/WODEN-136
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Reporter: John Kaputin
> Assignee: Dan Harvey
> Fix For: M8
>
>
> {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.
--
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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
[jira] Resolved: (WODEN-136) Message content model should not be
represented in the Element API
Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WODEN-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Kaputin resolved WODEN-136.
--------------------------------
Resolution: Fixed
This has been fixed via WODEN-162,
> Message content model should not be represented in the Element API
> ------------------------------------------------------------------
>
> Key: WODEN-136
> URL: https://issues.apache.org/jira/browse/WODEN-136
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Reporter: John Kaputin
> Assignee: Dan Harvey
> Fix For: M8
>
>
> {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.
--
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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
[jira] Commented: (WODEN-136) Message content model should not be
represented in the Element API
Posted by "Dan Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WODEN-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521476 ]
Dan Harvey commented on WODEN-136:
----------------------------------
The fix for this Jira is included in WODEN-162 as there was a lot of change overlap with that Jira.
> Message content model should not be represented in the Element API
> ------------------------------------------------------------------
>
> Key: WODEN-136
> URL: https://issues.apache.org/jira/browse/WODEN-136
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Reporter: John Kaputin
> Assignee: Dan Harvey
> Fix For: M8
>
>
> {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.
--
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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
[jira] Commented: (WODEN-136) Message content model should not be
represented in the Element API
Posted by "John Kaputin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WODEN-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519947 ]
John Kaputin commented on WODEN-136:
------------------------------------
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'.
> Message content model should not be represented in the Element API
> ------------------------------------------------------------------
>
> Key: WODEN-136
> URL: https://issues.apache.org/jira/browse/WODEN-136
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Reporter: John Kaputin
> Assignee: John Kaputin
> Fix For: M8
>
>
> {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.
--
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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org