apache > ws.apache

## Apache Muse - WS-DistributedManagement - CorrelatableProperties Capability

Spec name and port type: WS-DistributedManagement v1.1 (no port type)

Capability URI: http://docs.oasis-open.org/wsdm/muws/capabilities/CorrelatableProperties

Description: This capability defines a property about other properties; the muws2:CorrelatableProperties property tells a client which property values have to match between two resource property documents in order for the two WS-resources that own them to be considered equal. By equal, we mean that the two resources actually point to the same physical resource despite being addressed with different EPRs. The API for this capability provides a means of defining the dialects for the muws2:CorrelatableProperties property, as well as evaluating the correlations against two EPRs.

Java interface: org.apache.muse.ws.dm.muws.CorrelatableProperties

> JAR file: muse-wsdm-muws-api.jar

Default Java implementation: org.apache.muse.ws.dm.muws.impl.SimpleCorrelatableProperties

> JAR file: muse-wsdm-muws-impl.jar

Action on initialize(): None.

Action on initializeCompleted(): None.

Action on prepareShutdown(): None.

Action on shutdown(): None.

Non-Core Dependencies:

- org.apache.muse.ws.dm.muws.Correlation
- org.apache.muse.ws.resource.remote.WsResourceClient
- The Abstract WSDM MUWS Capability

Behavior and Limitations: The default implementation of this capability allows users to add correlations, or correlatable properties expressions, at runtime, and to evaluate them against resources at other EPRs. The standard correlation dialects - Property Boolean Match (PBM) and XPath - are implemented and allow users to easily create expression that can then be grouped together by the capability implementation and executed against a resource's WSRP document.

The capability's interface has a matches() method that allows server-side code to evaluate all of the current correlations against a resource by providing its EPR. The implementation will treat all EPRs as remote and will access the properties of the resource using SOAP even if the EPR belongs to a resource in the same application-space as the caller. It is assumed that if the user believes two internal resources two be equal despite having different EPRs, he could use a simple equality check to verify.

Initialization parameters: None.