[
https://issues.apache.org/jira/browse/AIRAVATA-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saminda Wijeratne updated AIRAVATA-174:
---------------------------------------
Attachment: AIRAVATA-174.patch
AIRAVATA-174.patch fixes the above issue + some refactoring of unwanted
functions in the jcr component registry class
> JCRRegistry implementation of search*Description(para) functions of the
> Registry API do not honor the passed filter parameters
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-174
> URL: https://issues.apache.org/jira/browse/AIRAVATA-174
> Project: Airavata
> Issue Type: Bug
> Components: XBaya
> Reporter: Saminda Wijeratne
> Attachments: AIRAVATA-174.patch
>
>
> searchServiceDescription function returns all service descriptions no matter
> what the name parameter value (placed for filtering purposes) is. filtering
> should occur using the string parameter that was passed assuming its a
> regular expression to match the service description name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
