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 "Balan Subramanian (JIRA)" <ji...@apache.org> on 2006/07/25 17:37:13 UTC
[jira] Created: (MUSE-47) Utility methods for finding properties
per capability and traversing service groups
Utility methods for finding properties per capability and traversing service groups
-----------------------------------------------------------------------------------
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
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.
--
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
[jira] Updated: (MUSE-47) Utility methods for finding properties
per capability
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ 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
[jira] Assigned: (MUSE-47) Utility methods for finding properties
per capability
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-47?page=all ]
Dan Jemiolo reassigned MUSE-47:
-------------------------------
Assignee: (was: Dan Jemiolo)
> 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
> 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
[jira] Commented: (MUSE-47) Utility methods for finding properties
per capability
Posted by "Balan Subramanian (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-47?page=comments#action_12423749 ]
Balan Subramanian commented on MUSE-47:
---------------------------------------
In my understanding the current Analyzer code only handles standard capabilities. I'd propose moving this out of the tools package into the utilities package and have the tools package use this utility class as needed.
> 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
> 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
[jira] Commented: (MUSE-47) Utility methods for finding properties
per capability
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-47?page=comments#action_12423754 ]
Dan Jemiolo commented on MUSE-47:
---------------------------------
I believe Andrew has code to get the other capabilities via Analyzer.getCapabilities( ), which provides a Map[uri, Capability]. each Capability can return its property names. The utility method proposed should simply tie together the static stuff (standard caps) and the getCapabilities() lookup.
We should not put this utility in muse-util because it will have a dependency on all of the ws-* modules - if muse-util has a dependency on muse-ws*-api, then users must include all those modules even if they do not use them, which defeats the purpose of modularizing them in the first place. muse-tools already depends on all modules, so in the interest of dependency and bundle management, the utility should go there. Since the SimpleAnalyzer code has the means of offering both static and custom capability info, it would be ideal to simply tie the two things together in one method. Andrew?
> 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
> 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
[jira] Closed: (MUSE-47) Utility methods for finding properties per
capability
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-47?page=all ]
Dan Jemiolo closed MUSE-47.
---------------------------
Fix Version/s: 2.0.0 M2
Resolution: Fixed
This should be possible using the Analyzer API and SimpleAnalyzer implementation.
> 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
> Priority: Minor
> Fix For: 2.0.0 M2
>
>
> 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
[jira] Commented: (MUSE-47) Utility methods for finding properties
per capability
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-47?page=comments#action_12423706 ]
Dan Jemiolo commented on MUSE-47:
---------------------------------
Andrew has this function in his implementation of Analyzer (muse-tools) - I'm looking to him to make all the necessary methods available and submit a patch of SimpleAnalyzer to resolve this issue.
> 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
> 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
[jira] Commented: (MUSE-47) Utility methods for finding properties
per capability and traversing service groups
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-47?page=comments#action_12423371 ]
Dan Jemiolo commented on MUSE-47:
---------------------------------
Please split these into separate items by moving the service group item to a new request under the service groups category. I will then change this item to just focus on the capability/property assocations.
> Utility methods for finding properties per capability and traversing service groups
> -----------------------------------------------------------------------------------
>
> 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
>
> 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.
--
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