You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Dan Jemiolo (JIRA)" <ji...@apache.org> on 2006/07/26 05:37:14 UTC
[jira] Updated: (MUSE-47) Utility methods for finding properties
per capability
[ http://issues.apache.org/jira/browse/MUSE-47?page=all ]
Dan Jemiolo updated MUSE-47:
----------------------------
Summary: Utility methods for finding properties per capability (was: Utility methods for finding properties per capability and traversing service groups)
Description:
I'd like to propose additional code that provides the functions of finding all properties that belong to a capability
The first function can be implemented by comparing the namespace URI of properties implemented by a particular resource with the namespace URI of the capability. While this is not mandated by the spec, this is an useful convention to follow and most probably, tooling around WSDM could enforce this (based on user preference). We can specify this limitation in the documentation. Also for standard capabilities, it will use the the PROPERTIES array from the WS-* interfaces for standard capabilities. This function can be added to a MuwsUtils class.
was:
I'd like to propose additional code that provides the functions of:
1. Finding all properties that belong to a capability
2. Traversing service groups for resources that implement a particular capability
The first function can be implemented by comparing the namespace URI of properties implemented by a particular resource with the namespace URI of the capability. While this is not mandated by the spec, this is an useful convention to follow and most probably, tooling around WSDM could enforce this (based on user preference). We can specify this limitation in the documentation. Also for standard capabilities, it will use the the PROPERTIES array from the WS-* interfaces for standard capabilities. This function can be added to a MuwsUtils class.
The second function will use the content property specified for each service group entry to determine whether it implements the specified capability. It will also recurse through contained service groups. This function can be added to a WssgUtils class.
Priority: Minor (was: Major)
Splitting the original issue into two because it involves two distinct features in two distinct modules. Since this will have to depend on all -api modules, I don't know if it should go in muse-wsdm-muws-impl or muse-tools. Once I see the code it will be easier to make the call.
> Utility methods for finding properties per capability
> -----------------------------------------------------
>
> Key: MUSE-47
> URL: http://issues.apache.org/jira/browse/MUSE-47
> Project: Muse
> Issue Type: Improvement
> Components: Utilities - General, QName, and XML
> Affects Versions: 2.0.0 M1
> Reporter: Balan Subramanian
> Assigned To: Dan Jemiolo
> Priority: Minor
>
> I'd like to propose additional code that provides the functions of finding all properties that belong to a capability
> The first function can be implemented by comparing the namespace URI of properties implemented by a particular resource with the namespace URI of the capability. While this is not mandated by the spec, this is an useful convention to follow and most probably, tooling around WSDM could enforce this (based on user preference). We can specify this limitation in the documentation. Also for standard capabilities, it will use the the PROPERTIES array from the WS-* interfaces for standard capabilities. This function can be added to a MuwsUtils class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org