|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Environment:
|
All
|
|
|
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.
|
|
Description
|
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. |
Show » |
| There are no subversion log entries for this issue yet.
|
|
New Feature
Open
Major
Discovery based bootstrapping for advertisements
