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 "Dan Jemiolo (JIRA)" <ji...@apache.org> on 2006/07/10 05:47:29 UTC
[jira] Created: (MUSE-31) Change NotificationProducer.publish( ) to
take a topic and message content instead of a NotificationMessage
Change NotificationProducer.publish( ) to take a topic and message content instead of a NotificationMessage
-----------------------------------------------------------------------------------------------------------
Key: MUSE-31
URL: http://issues.apache.org/jira/browse/MUSE-31
Project: Muse
Type: Improvement
Environment: Axis2 and OSGi
Reporter: Dan Jemiolo
Priority: Trivial
The WSN NotificationProducer interface could be improved so that users have to write less code and learn less APIs in order to publish a notification.
Right now, users must create a NotificationMessage, set the topic (or provide it in the constructor), add the message content (Objects or Elements), and then call NotificationProducer.publish( ) with the message as a parameter. The other fields in the message - e.g., the subscription reference - are filled in by the NotificationProducer implementation. This is inconsistent and can be fixed easily.
By making publish have the following signature:
void publish(QName topicName, Object messageContent)
The NP implementation can create a NotificationMessage object itself, set the topic itself, set the other fields it's already setting, and add the message content before publishing. This removes three lines of code from the process and lowers the number of classes (by 1) and methods (by 2) the user must know.
--
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] Closed: (MUSE-31) Change NotificationProducer.publish( ) to
take a topic and message content instead of a NotificationMessage
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-31?page=all ]
Dan Jemiolo closed MUSE-31.
---------------------------
Fix Version/s: 2.0.0 M2
Resolution: Fixed
Assignee: Dan Jemiolo
> Change NotificationProducer.publish( ) to take a topic and message content instead of a NotificationMessage
> -----------------------------------------------------------------------------------------------------------
>
> Key: MUSE-31
> URL: http://issues.apache.org/jira/browse/MUSE-31
> Project: Muse
> Issue Type: Improvement
> Environment: Axis2 and OSGi
> Reporter: Dan Jemiolo
> Assigned To: Dan Jemiolo
> Priority: Trivial
> Fix For: 2.0.0 M2
>
>
> The WSN NotificationProducer interface could be improved so that users have to write less code and learn less APIs in order to publish a notification.
> Right now, users must create a NotificationMessage, set the topic (or provide it in the constructor), add the message content (Objects or Elements), and then call NotificationProducer.publish( ) with the message as a parameter. The other fields in the message - e.g., the subscription reference - are filled in by the NotificationProducer implementation. This is inconsistent and can be fixed easily.
> By making publish have the following signature:
> void publish(QName topicName, Object messageContent)
> The NP implementation can create a NotificationMessage object itself, set the topic itself, set the other fields it's already setting, and add the message content before publishing. This removes three lines of code from the process and lowers the number of classes (by 1) and methods (by 2) the user must know.
--
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-31) Change NotificationProducer.publish( )
to take a topic and message content instead of a NotificationMessage
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-31?page=comments#action_12420177 ]
Dan Jemiolo commented on MUSE-31:
---------------------------------
Fixed: http://svn.apache.org/viewvc?view=rev&revision=420647
> Change NotificationProducer.publish( ) to take a topic and message content instead of a NotificationMessage
> -----------------------------------------------------------------------------------------------------------
>
> Key: MUSE-31
> URL: http://issues.apache.org/jira/browse/MUSE-31
> Project: Muse
> Type: Improvement
> Environment: Axis2 and OSGi
> Reporter: Dan Jemiolo
> Priority: Trivial
>
> The WSN NotificationProducer interface could be improved so that users have to write less code and learn less APIs in order to publish a notification.
> Right now, users must create a NotificationMessage, set the topic (or provide it in the constructor), add the message content (Objects or Elements), and then call NotificationProducer.publish( ) with the message as a parameter. The other fields in the message - e.g., the subscription reference - are filled in by the NotificationProducer implementation. This is inconsistent and can be fixed easily.
> By making publish have the following signature:
> void publish(QName topicName, Object messageContent)
> The NP implementation can create a NotificationMessage object itself, set the topic itself, set the other fields it's already setting, and add the message content before publishing. This removes three lines of code from the process and lowers the number of classes (by 1) and methods (by 2) the user must know.
--
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