[jira] Commented: (MUSE-256) Discovery based bootstrapping for advertisements

["Kam K. Yee (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MUSE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529504 ] 

Kam K. Yee commented on MUSE-256:
---------------------------------

Instead of directly modifying SimpleAdvertisement, why not create new classes (e.g., WSDiscoveryDynamicAdvertisement and SLPDynamicAdvertisement) that either extend SimpleAdvertisement or AbstractAdvertisement (which ever is more appropriate) and implement the newly introduced DiscoveryCapability?  This would not require changes to the muse descriptor schema and retain the now known and stable implementation of SimpleAdvertisement (which other classes extend).

> Discovery based bootstrapping for advertisements
> ------------------------------------------------
>
>                 Key: MUSE-256
>                 URL: https://issues.apache.org/jira/browse/MUSE-256
>             Project: Muse
>          Issue Type: New Feature
>          Components: WSDM MUWS Advertisement
>         Environment: All
>            Reporter: Balan Subramanian
>            Assignee: Dan Jemiolo
>             Fix For: 2.3.0
>
>         Attachments: muse-256.doc
>
>
> Currently Muse expects users to provide the EPR of the intended receiver of advertisements in muse.xml. The suggestion is to automatically discover this at runtime / initialization time using discovery mechanisms like SLP and WS-Discovery. 
> We can implement this in a pluggable manner by providing an abstract discovery definition of which a concrete implementation can be specified in muse.xml. If such a definition is present, Muse must first invoke the discovery code to discover the intended advertisement receiver. It is expected that advertisement receivers will "lend" themselves for discovery through various mechanisms like being Service Agents or in the case of WS-Discovery will be listening for probe messages. Hence this requirements actually has a endpoint side requirement for endpoints implementing advertisement capability and "client" side requirements for WS-N consumers (to advertise or listen for probe messages). The actual implementation is not a consideration for Muse.
> Before sending advertisements, Muse will check to see if a consumer-epr.xml file is specified or a discovery class is specified. If a discovery class is specified it will query the class to find the EPR of the WS-N consumer before sending the advertisement.
> The suggested default implementation is WS-Discovery. 

-- 
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@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org