[jira] Updated: (JUDDI-427) FindQualifiers using tModel name instead of tModelKey

["Lyudmil Latinov (JIRA)" <ju...@ws.apache.org>]

     [ https://issues.apache.org/jira/browse/JUDDI-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lyudmil Latinov updated JUDDI-427:
----------------------------------

    Attachment: FindQualifiers.java

Attaching file with fixed strings.

> FindQualifiers using tModel name instead of tModelKey
> -----------------------------------------------------
>
>                 Key: JUDDI-427
>                 URL: https://issues.apache.org/jira/browse/JUDDI-427
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.3
>            Reporter: Lyudmil Latinov
>            Assignee: Kurt T Stam
>         Attachments: FindQualifiers.java
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> As per UDDI v3.0.2 specification - http://uddi.org/pubs/uddi_v3.htm
> 5.1.4 Find Qualifiers
> Each of the find_xx APIs accepts an optional findQualifiers argument, which may contain multiple findQualifier values. Find qualifiers may be either tModelKeys or may be referenced by a string containing a "short name". Each of the pre-defined findQualifiers in UDDI can be referenced using either the appropriate tModelKey, or by its short name. 
> Currently jUDDI uses tModel names in org.apache.juddi.query.util.FindQualifiers
> e.g public static final String APPROXIMATE_MATCH_TMODEL = "uddi-org:approximateMatch:SQL99"; (same for all *_TMODEL)
> uddi-org:approximateMatch:SQL99 is the name of the tModel, not the tModelKey. tModeKey is uddi:uddi.org:findqualifier:approximatematch (see 11.4.1.3 tModel Definition)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.