You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Mohammad Fakhar (JIRA)" <ji...@apache.org> on 2006/11/27 20:04:20 UTC
[jira] Created: (MUSE-151) WS-Topics Muse implementation should
support messageType and messagePattern constraints
WS-Topics Muse implementation should support messageType and messagePattern constraints
---------------------------------------------------------------------------------------
Key: MUSE-151
URL: http://issues.apache.org/jira/browse/MUSE-151
Project: Muse
Issue Type: Improvement
Affects Versions: 2.1.0
Environment: any
Reporter: Mohammad Fakhar
Assigned To: Dan Jemiolo
Priority: Minor
The WS-Topics spec defines messageTypes and messagePattern options for specifying message type constraints on a topic at declaration time.
The following are snippets from the spec for these two options:
1) "/wstop:Topic/@messageTypes
An optional list of the QNames of XML elements that define the types of NotificationMessage
that may be used with the Topic. A Publisher using a given Topic MUST NOT generate a
NotificationMessage whose type is not included in this list, although the special value xsd:any
indicates that any NotificationMessage type MAY be used. A given QName MAY appear
multiple times in the list; second or subsequent appearance of a given QName are not
meaningful and MAY BE ignored. If this list is empty, or the attribute not defined, the default
value ofxsd:any is assumed."
2) "/wstop:Topic/MessagePattern
An optional QueryExpression as defined by WS-ResourceProperties. This QueryExpression
is used to describe the pattern of the message that will appear on the Topic. Conceptually,
the MessagePattern component can be thought of as the object of an boolean() expression,
evaluated against a NotificationMessage. This boolean() expression, with the value of
MessagePattern as parameter, is guaranteed to evaluate to "true" when evaluated in the
context of any NotificationMessage that is associated with the Topic. The MessagePattern
component constrains the NotificationMessages that can be used with the Topic. It is
additional to the constraint contained in @messageTypes, and provides a further refinement
to that constraint."
These two opttions are not supported by Muse's Ws-Topics implementation currently; they are optional and
can be added as an improvement to the WS-Topics support in Muse.
--
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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Commented: (MUSE-151) WS-Topics Muse implementation should
support messageType and messagePattern constraints
Posted by "Mohammad Fakhar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MUSE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465017 ]
Mohammad Fakhar commented on MUSE-151:
--------------------------------------
This is fine. I can live with programmatic setting of message patterns for now. I will verify if the xpath checks work soon after running a test.
> WS-Topics Muse implementation should support messageType and messagePattern constraints
> ---------------------------------------------------------------------------------------
>
> Key: MUSE-151
> URL: https://issues.apache.org/jira/browse/MUSE-151
> Project: Muse
> Issue Type: Improvement
> Components: WSN NotificationProducer, WSN Topics
> Affects Versions: 2.1.0
> Environment: any
> Reporter: Mohammad Fakhar
> Assigned To: Dan Jemiolo
> Priority: Minor
> Fix For: 2.2.0
>
>
> The WS-Topics spec defines messageTypes and messagePattern options for specifying message type constraints on a topic at declaration time.
> The following are snippets from the spec for these two options:
> 1) "/wstop:Topic/@messageTypes
> An optional list of the QNames of XML elements that define the types of NotificationMessage
> that may be used with the Topic. A Publisher using a given Topic MUST NOT generate a
> NotificationMessage whose type is not included in this list, although the special value xsd:any
> indicates that any NotificationMessage type MAY be used. A given QName MAY appear
> multiple times in the list; second or subsequent appearance of a given QName are not
> meaningful and MAY BE ignored. If this list is empty, or the attribute not defined, the default
> value ofxsd:any is assumed."
> 2) "/wstop:Topic/MessagePattern
> An optional QueryExpression as defined by WS-ResourceProperties. This QueryExpression
> is used to describe the pattern of the message that will appear on the Topic. Conceptually,
> the MessagePattern component can be thought of as the object of an boolean() expression,
> evaluated against a NotificationMessage. This boolean() expression, with the value of
> MessagePattern as parameter, is guaranteed to evaluate to "true" when evaluated in the
> context of any NotificationMessage that is associated with the Topic. The MessagePattern
> component constrains the NotificationMessages that can be used with the Topic. It is
> additional to the constraint contained in @messageTypes, and provides a further refinement
> to that constraint."
> These two opttions are not supported by Muse's Ws-Topics implementation currently; they are optional and
> can be added as an improvement to the WS-Topics support in Muse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Closed: (MUSE-151) WS-Topics Muse implementation should
support messageType and messagePattern constraints
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MUSE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Jemiolo closed MUSE-151.
----------------------------
Resolution: Fixed
> WS-Topics Muse implementation should support messageType and messagePattern constraints
> ---------------------------------------------------------------------------------------
>
> Key: MUSE-151
> URL: https://issues.apache.org/jira/browse/MUSE-151
> Project: Muse
> Issue Type: Improvement
> Components: WSN NotificationProducer, WSN Topics
> Affects Versions: 2.1.0
> Environment: any
> Reporter: Mohammad Fakhar
> Assigned To: Dan Jemiolo
> Priority: Minor
> Fix For: 2.2.0
>
>
> The WS-Topics spec defines messageTypes and messagePattern options for specifying message type constraints on a topic at declaration time.
> The following are snippets from the spec for these two options:
> 1) "/wstop:Topic/@messageTypes
> An optional list of the QNames of XML elements that define the types of NotificationMessage
> that may be used with the Topic. A Publisher using a given Topic MUST NOT generate a
> NotificationMessage whose type is not included in this list, although the special value xsd:any
> indicates that any NotificationMessage type MAY be used. A given QName MAY appear
> multiple times in the list; second or subsequent appearance of a given QName are not
> meaningful and MAY BE ignored. If this list is empty, or the attribute not defined, the default
> value ofxsd:any is assumed."
> 2) "/wstop:Topic/MessagePattern
> An optional QueryExpression as defined by WS-ResourceProperties. This QueryExpression
> is used to describe the pattern of the message that will appear on the Topic. Conceptually,
> the MessagePattern component can be thought of as the object of an boolean() expression,
> evaluated against a NotificationMessage. This boolean() expression, with the value of
> MessagePattern as parameter, is guaranteed to evaluate to "true" when evaluated in the
> context of any NotificationMessage that is associated with the Topic. The MessagePattern
> component constrains the NotificationMessages that can be used with the Topic. It is
> additional to the constraint contained in @messageTypes, and provides a further refinement
> to that constraint."
> These two opttions are not supported by Muse's Ws-Topics implementation currently; they are optional and
> can be added as an improvement to the WS-Topics support in Muse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Updated: (MUSE-151) WS-Topics Muse implementation should
support messageType and messagePattern constraints
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-151?page=all ]
Dan Jemiolo updated MUSE-151:
-----------------------------
Component/s: WSN NotificationProducer
WSN Topics
Fix Version/s: 2.2.0
> WS-Topics Muse implementation should support messageType and messagePattern constraints
> ---------------------------------------------------------------------------------------
>
> Key: MUSE-151
> URL: http://issues.apache.org/jira/browse/MUSE-151
> Project: Muse
> Issue Type: Improvement
> Components: WSN NotificationProducer, WSN Topics
> Affects Versions: 2.1.0
> Environment: any
> Reporter: Mohammad Fakhar
> Assigned To: Dan Jemiolo
> Priority: Minor
> Fix For: 2.2.0
>
>
> The WS-Topics spec defines messageTypes and messagePattern options for specifying message type constraints on a topic at declaration time.
> The following are snippets from the spec for these two options:
> 1) "/wstop:Topic/@messageTypes
> An optional list of the QNames of XML elements that define the types of NotificationMessage
> that may be used with the Topic. A Publisher using a given Topic MUST NOT generate a
> NotificationMessage whose type is not included in this list, although the special value xsd:any
> indicates that any NotificationMessage type MAY be used. A given QName MAY appear
> multiple times in the list; second or subsequent appearance of a given QName are not
> meaningful and MAY BE ignored. If this list is empty, or the attribute not defined, the default
> value ofxsd:any is assumed."
> 2) "/wstop:Topic/MessagePattern
> An optional QueryExpression as defined by WS-ResourceProperties. This QueryExpression
> is used to describe the pattern of the message that will appear on the Topic. Conceptually,
> the MessagePattern component can be thought of as the object of an boolean() expression,
> evaluated against a NotificationMessage. This boolean() expression, with the value of
> MessagePattern as parameter, is guaranteed to evaluate to "true" when evaluated in the
> context of any NotificationMessage that is associated with the Topic. The MessagePattern
> component constrains the NotificationMessages that can be used with the Topic. It is
> additional to the constraint contained in @messageTypes, and provides a further refinement
> to that constraint."
> These two opttions are not supported by Muse's Ws-Topics implementation currently; they are optional and
> can be added as an improvement to the WS-Topics support in Muse.
--
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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Commented: (MUSE-151) WS-Topics Muse implementation should
support messageType and messagePattern constraints
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MUSE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462602 ]
Dan Jemiolo commented on MUSE-151:
----------------------------------
I updated TopicFilter and SimpleNotificationProducer so that we now support message pattern checking, but not message types. The reason is that I am unclear on what they mean by the message name - I originally thought it was the content elements under wsnt:Message, but now I think it may be the root wsnt:NotificationMessage itself. Which doesn't seem very useful, since we only support that message type. I thought the goal was to filter on CBE/WEF/WSRP change/etc.
So, I've added an XPath check to TopicFilter, if the pattern is provided. You have to provide the pattern programmatically with Topic.setMessagePattern() right now because of the way Topics are initialized in Muse (via RMD initial/static values on wsnt:TopicExpression).
Please let me know if the xpath filtering is working for you. See MUSE-153 for more info on issues related to Topic initialization.
> WS-Topics Muse implementation should support messageType and messagePattern constraints
> ---------------------------------------------------------------------------------------
>
> Key: MUSE-151
> URL: https://issues.apache.org/jira/browse/MUSE-151
> Project: Muse
> Issue Type: Improvement
> Components: WSN NotificationProducer, WSN Topics
> Affects Versions: 2.1.0
> Environment: any
> Reporter: Mohammad Fakhar
> Assigned To: Dan Jemiolo
> Priority: Minor
> Fix For: 2.2.0
>
>
> The WS-Topics spec defines messageTypes and messagePattern options for specifying message type constraints on a topic at declaration time.
> The following are snippets from the spec for these two options:
> 1) "/wstop:Topic/@messageTypes
> An optional list of the QNames of XML elements that define the types of NotificationMessage
> that may be used with the Topic. A Publisher using a given Topic MUST NOT generate a
> NotificationMessage whose type is not included in this list, although the special value xsd:any
> indicates that any NotificationMessage type MAY be used. A given QName MAY appear
> multiple times in the list; second or subsequent appearance of a given QName are not
> meaningful and MAY BE ignored. If this list is empty, or the attribute not defined, the default
> value ofxsd:any is assumed."
> 2) "/wstop:Topic/MessagePattern
> An optional QueryExpression as defined by WS-ResourceProperties. This QueryExpression
> is used to describe the pattern of the message that will appear on the Topic. Conceptually,
> the MessagePattern component can be thought of as the object of an boolean() expression,
> evaluated against a NotificationMessage. This boolean() expression, with the value of
> MessagePattern as parameter, is guaranteed to evaluate to "true" when evaluated in the
> context of any NotificationMessage that is associated with the Topic. The MessagePattern
> component constrains the NotificationMessages that can be used with the Topic. It is
> additional to the constraint contained in @messageTypes, and provides a further refinement
> to that constraint."
> These two opttions are not supported by Muse's Ws-Topics implementation currently; they are optional and
> can be added as an improvement to the WS-Topics support in Muse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org