ws-muse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kam K. Yee (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MUSE-256) Discovery based bootstrapping for advertisements
Date Mon, 07 Apr 2008 14:35:25 GMT

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

Kam K. Yee updated MUSE-256:
----------------------------

    Attachment: muse-256.zip

Attached is the implementation of this new feature contributed by the IBM Team

> 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, muse-256.zip
>
>
> 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


Mime
View raw message