juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Cunningham (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Commented: (JUDDI-398) When using a find_business query using either a tModelBag or an embedded find_tModel non-pertinent services are not filtered
Date Mon, 05 Jul 2010 03:49:50 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885099#action_12885099
] 

Tom Cunningham commented on JUDDI-398:
--------------------------------------

I took a look at this tonight - it looks to me like we want to add a FindServiceByTModelKeyQuery
in InquiryHelper.getBusinessListFromKeys to overwrite what FetchBusinessEntitiesQuery returns
if there is a TModelBag or find_tModel within body.

> When using a find_business query using either a tModelBag or an embedded find_tModel
non-pertinent services are not filtered
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JUDDI-398
>                 URL: https://issues.apache.org/jira/browse/JUDDI-398
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.2
>         Environment: Tomcat 6.0.10, PostgreSQL 8.4
>            Reporter: Jason Brown
>            Assignee: Jeff Faath
>             Fix For: 3.0.3
>
>
> When using a find_business query using either a tModelBag or an embedded find_tModel
non-pertinent services are not filtered per the UDDI specifications. 
> Inputs:
> save two tModels:
> <tModel tModelKey="uddi:tmodeltest:01">
>         <name>tmodeltest01</name>
> </tModel>
> <tModel tModelKey="uddi:tmodeltest:02">
>         <name>tmodeltest02</name>
> </tModel>
> save a business with two services and binding templates:
> <businessEntity businessKey="uddi:businesstest:01">
>         <name>businesstest:01</name>
>         <businessServices>
>             <businessService serviceKey="uddi:servicetest:01">
>                 <name>servicetest:01</name>
>                 <bindingTemplates>
>                     <bindingTemplate bindingKey="uddi:bindingtest:01">
>                         <accessPoint>http://genericaccesspoint.com</accessPoint>
>                         <tModelInstanceDetails>
>                             <tModelInstanceInfo tModelKey="uddi:tmodeltest:01">
>                             </tModelInstanceInfo>
>                         </tModelInstanceDetails>
>                     </bindingTemplate>
>                 </bindingTemplates>
>             </businessService>
>             <businessService serviceKey="uddi:servicetest:02">
>                 <name>servicetest:02</name>
>                 <bindingTemplates>
>                     <bindingTemplate bindingKey="uddi:biningtest:02">
>                         <accessPoint>http://genericaccesspoint2.com</accessPoint>
>                         <tModelInstanceDetails>
>                             <tModelInstanceInfo tModelKey="uddi:tmodeltest:02">
>                             </tModelInstanceInfo>
>                         </tModelInstanceDetails>
>                     </bindingTemplate>
>                </bindingTemplates>
>             </businessService>
>         </businessServices>
>     </businessEntity>
> Perform either of the following queries:
> <find_business xmlns="urn:uddi-org:api_v3">
>  <find_tModel>
> <name>uddi:tmodeltest:01</name>
> </find_tModel>
> </find_business>
> <find_business xmlns="urn:uddi-org:api_v3">
>        <tModelBag>
>         <tModelKey>uddi:tmodeltest:01</tModelKey>
>     </tModelBag>
> </find_business>
> and the businessInfo will be returned with both serviceInfos where it should only be
"uddi:servicetest:01" per UDDI v3.0.2 spec, 1st paragraph of page 81:
> "If a tModelBag or find_tModel was used in the search, the resulting serviceInfos structure
reflects data only for the businessServices that actually contained a matching bindingTemplate."

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


Mime
View raw message