[
https://issues.apache.org/jira/browse/JUDDI-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Faath closed JUDDI-404.
----------------------------
Resolution: Fixed
Keys are now all case-folded by the server. Inquiry operations will work fine
no matter what however, the returned keys will always be case-folded.
> Saved keys being converted to lowercase causes problems with keyedReference
> searches
> ------------------------------------------------------------------------------------
>
> Key: JUDDI-404
> URL: https://issues.apache.org/jira/browse/JUDDI-404
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.2
> Environment: Apache Tomcat 6.0.10, PostgreSQL 8.4
> Reporter: Jason Brown
> Assignee: Jeff Faath
> Fix For: 3.0.3
>
>
> When saving entity keys, jUDDI appears to be converting them to lowercase.
> This presents a problem in the following scenario:
> Inputs:
> Save the following tModel with an uppercase character in the tModelKey:
> <save_tModel xmlns="urn:uddi-org:api_v3">
> <tModel tModelKey="uddi:tmodel:A">
> <name>uddi:tmodel:A</name>
> </tModel>
> </save_tModel>
> Save the following business with a keyedReference referencing that tModel
> using the same uppercase tModelKey
> <save_business xmlns="urn:uddi-org:api_v3">
> <businessEntity businessKey="uddi:businesstest:a">
> <name>uddi:businesstest:a</name>
> <categoryBag>
> <keyedReference tModelKey="uddi:tmodel:A" keyValue="test01"/>
> </categoryBag>
> </businessEntity>
> </save_business>
> Since the tModel key is converted to lowercase, but the case is preserved in
> the keyedReference, a subsequent search using a the key that would be
> returned from a get_tModelDetail (uddi:tmodel:a) in the keyedReference:
> <find_business xmlns="urn:uddi-org:api_v3">
> <categoryBag>
> <keyedReference tModelKey="uddi:tmodel:a" keyValue="test_01"/>
> </categoryBag>
> </find_business>
> will not return the business. It would require knowledge beforehand that the
> key was initially saved with a capital letter somewhere within the key.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
