[
https://issues.apache.org/jira/browse/SCOUT-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056716#comment-13056716
]
Tom Cunningham commented on SCOUT-117:
--------------------------------------
I think it's the same issue and I think it may be fixed already. In
BusinessQueryManagerV3Impl, we check whether a qualifier is exactNameMatch, and
if it is, we set it to exactMatch.
Wrote Shawn asking for a stack to help reproduce the problem, but I think it
has been solved.
> EXACT_MATCH was EXACT_NAME_MATCH in v2. V3 should add EXACT_NAME_MATCH for
> backward compatibility in FindQualifiers
> -------------------------------------------------------------------------------------------------------------------
>
> Key: SCOUT-117
> URL: https://issues.apache.org/jira/browse/SCOUT-117
> Project: Scout
> Issue Type: Bug
> Components: Scout Implementation
> Affects Versions: 1.2.2
> Reporter: Shawn Jiang
> Assignee: Tom Cunningham
> Fix For: 1.2.3
>
>
> I added a patch for this in JUDDI. But Tom thought that it might be better
> to fix it in scout side.
> See: https://issues.apache.org/jira/browse/JUDDI-504
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
