[ 
https://issues.apache.org/jira/browse/MUSE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Twiner updated MUSE-294:
------------------------------

    Fix Version/s:     (was: 2.2.1)
                   2.3.0

The PullPoint change can safely be added to 2.2.1 without changing binary 
compatibility.   All other parts break compatibility.

> Collective WS-N / Core improvements
> -----------------------------------
>
>                 Key: MUSE-294
>                 URL: https://issues.apache.org/jira/browse/MUSE-294
>             Project: Muse
>          Issue Type: Improvement
>          Components: Core Engine - Resource and Capability APIs, Core Engine 
> - Routing and Serialization, WSN NotificationConsumer, WSN 
> NotificationProducer, WSN PullPoint, WSN SubscriptionManager, WSN Topics, 
> WSRF & WSN - Property Change Notifications
>    Affects Versions: 2.2.0
>            Reporter: Chris Twiner
>            Assignee: Chris Twiner
>             Fix For: 2.3.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> In essence this work is a merge from a custom version of muse made by me.  It 
> addresses many parts of Muse but in particular meets the three main 
> functional areas:
> - two tier path handling for muse files.  (core, platform)
> - shutdowns / restarts (core, resource, platforms, ws-n)
> - WS-N improvements
> Each of these changes breaks interface compatibility and therefore must be on 
> the larger release version 2.3.0.
> The two tier path handling allows external writable directories for storing 
> subscriptions etc.
> WS-N improvements include:
> - PullPoints only notify against subscriptions (not all)
> - NotificationProducer supports proxied sends
> - Subscriptions are kept across restarts / shutdowns
> Details are added as seperate sub issues.

-- 
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]

Reply via email to