[
https://issues.apache.org/jira/browse/MUSE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531101
]
Dan Jemiolo commented on MUSE-256:
----------------------------------
One suggestion I would make is to use Resource.getCapability( ) or
Resource.hasCapability( ) rather than creating another init-param. Have the
Advertisement implementation(s) check for the presence of the Discovery
capability in the containing Resource and start the discovery process if it's
there; the ability to have these kind of conditional features was one of the
main goals of having the *Capability( ) methods in the Resource API and making
sure all capabilities had interfaces. This way you can have the optional
discovery stuff without adding another init-param - discovery just gets turned
on if you add the capability, and advertisement is augmented if it's there as
well.
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
