[jira] Created: (MUSE-281) Subscription Manager must throw faults on publish back to notification producer
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
[jira] Created: (MUSE-281) Subscription Manager must throw faults on publish back to notification producer
by JIRA jira@apache.org
::
Rate this Message:
Subscription Manager must throw faults on publish back to notification producer
------------------------------------------------------------------------------- Key: MUSE-281 URL: https://issues.apache.org/jira/browse/MUSE-281 Project: Muse Issue Type: Improvement Components: WSN SubscriptionManager Affects Versions: 2.2.0 Environment: All Reporter: Balan Subramanian Assignee: Dan Jemiolo Fix For: 2.3.0 SimpleSubscriptionManager's publish message catches exceptions but consumes them after logging them. This way at runtime, the actual publisher of the message, typically another capability in the resource, never knows that the publish failed. We can build a java listener based mechanism so that when a capability tries to call the publish operation, it must provide a reference to itself and implement a listener interface. This means we overload the publish method. If such a callback reference is available, the SimpleSubscriptionManager will call it back when it receives a fault, with the fault. -- 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: muse-dev-unsubscribe@... For additional commands, e-mail: muse-dev-help@... |
|
|
[jira] Commented: (MUSE-281) Subscription Manager must throw faults on publish back to notification producer
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/MUSE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558006#action_12558006 ] Balan Subramanian commented on MUSE-281: ---------------------------------------- I was under the mistaken impression that the actual publish of the message by the subscription manager was non-blocking and asynchronous. It seems that all that is needed for this is for publish to throw an exception. > Subscription Manager must throw faults on publish back to notification producer > ------------------------------------------------------------------------------- > > Key: MUSE-281 > URL: https://issues.apache.org/jira/browse/MUSE-281 > Project: Muse > Issue Type: Improvement > Components: WSN SubscriptionManager > Affects Versions: 2.2.0 > Environment: All > Reporter: Balan Subramanian > Assignee: Dan Jemiolo > Fix For: 2.3.0 > > > SimpleSubscriptionManager's publish message catches exceptions but consumes them after logging them. This way at runtime, the actual publisher of the message, typically another capability in the resource, never knows that the publish failed. > We can build a java listener based mechanism so that when a capability tries to call the publish operation, it must provide a reference to itself and implement a listener interface. This means we overload the publish method. If such a callback reference is available, the SimpleSubscriptionManager will call it back when it receives a fault, with the fault. -- 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: muse-dev-unsubscribe@... For additional commands, e-mail: muse-dev-help@... |
|
|
[jira] Updated: (MUSE-281) Subscription Manager must throw faults on publish back to notification producer
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/MUSE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kam K. Yee updated MUSE-281: ---------------------------- Attachment: muse-281.patch > Subscription Manager must throw faults on publish back to notification producer > ------------------------------------------------------------------------------- > > Key: MUSE-281 > URL: https://issues.apache.org/jira/browse/MUSE-281 > Project: Muse > Issue Type: Improvement > Components: WSN SubscriptionManager > Affects Versions: 2.2.0 > Environment: All > Reporter: Balan Subramanian > Assignee: Dan Jemiolo > Fix For: 2.3.0 > > Attachments: muse-281.patch > > > SimpleSubscriptionManager's publish message catches exceptions but consumes them after logging them. This way at runtime, the actual publisher of the message, typically another capability in the resource, never knows that the publish failed. > We can build a java listener based mechanism so that when a capability tries to call the publish operation, it must provide a reference to itself and implement a listener interface. This means we overload the publish method. If such a callback reference is available, the SimpleSubscriptionManager will call it back when it receives a fault, with the fault. -- 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: muse-dev-unsubscribe@... For additional commands, e-mail: muse-dev-help@... |
|
|
[jira] Assigned: (MUSE-281) Subscription Manager must throw faults on publish back to notification producer
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/MUSE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Twiner reassigned MUSE-281: --------------------------------- Assignee: Chris Twiner (was: Dan Jemiolo) > Subscription Manager must throw faults on publish back to notification producer > ------------------------------------------------------------------------------- > > Key: MUSE-281 > URL: https://issues.apache.org/jira/browse/MUSE-281 > Project: Muse > Issue Type: Improvement > Components: WSN SubscriptionManager > Affects Versions: 2.2.0 > Environment: All > Reporter: Balan Subramanian > Assignee: Chris Twiner > Fix For: 2.3.0 > > Attachments: muse-281.patch > > > SimpleSubscriptionManager's publish message catches exceptions but consumes them after logging them. This way at runtime, the actual publisher of the message, typically another capability in the resource, never knows that the publish failed. > We can build a java listener based mechanism so that when a capability tries to call the publish operation, it must provide a reference to itself and implement a listener interface. This means we overload the publish method. If such a callback reference is available, the SimpleSubscriptionManager will call it back when it receives a fault, with the fault. -- 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: muse-dev-unsubscribe@... For additional commands, e-mail: muse-dev-help@... |
|
|
[jira] Resolved: (MUSE-281) Subscription Manager must throw faults on publish back to notification producer
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/MUSE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Twiner resolved MUSE-281. ------------------------------- Resolution: Fixed fixed in head. NOTE that due to the success and shutdown semantics I've rejected the patch. The head fix captures the soapfault, but does not throw until after possible shutdown has occurred, and then only IF it wasn't actually sucessful. > Subscription Manager must throw faults on publish back to notification producer > ------------------------------------------------------------------------------- > > Key: MUSE-281 > URL: https://issues.apache.org/jira/browse/MUSE-281 > Project: Muse > Issue Type: Improvement > Components: WSN SubscriptionManager > Affects Versions: 2.2.0 > Environment: All > Reporter: Balan Subramanian > Assignee: Chris Twiner > Fix For: 2.2.1 > > Attachments: muse-281.patch > > > SimpleSubscriptionManager's publish message catches exceptions but consumes them after logging them. This way at runtime, the actual publisher of the message, typically another capability in the resource, never knows that the publish failed. > We can build a java listener based mechanism so that when a capability tries to call the publish operation, it must provide a reference to itself and implement a listener interface. This means we overload the publish method. If such a callback reference is available, the SimpleSubscriptionManager will call it back when it receives a fault, with the fault. -- 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: muse-dev-unsubscribe@... For additional commands, e-mail: muse-dev-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
