[
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
