[
https://issues.apache.org/jira/browse/JUDDI-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Webb updated JUDDI-570:
-----------------------------
Description:
My original description of this problem was misleading so I have reworded.
I have used the client jar to create a publisher, business and around 20 or so
services. All services at the moment have one binding each and obviously an
associated tmodel. If I perform a find_binding search using the client jar or
via soapUI and in the call set the service key and add a qualifier based on the
tmodel name it finds the service details (see soap call below). However if two
or more of the tmodel names are the same then the normal call returns no
binding details.
I'm not sure if this a bug or I am misunderstanding how I can obtain a binding
for a service based on the tmodel name.
Just for clarity I should mention we are using the tmodel name as a way of
specifying the service version, this has been enforced from elsewhere, so as
you can understand two services may have an interface version of say '1.0' and
each would have a tmodel with the same name.
By the way Pluto shows the full list of services and the correct endpoints, and
a search on tmodels shows all tmodels including the ones with the same names.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:urn="urn:uddi-org:api_v3">
<soapenv:Header/>
<soapenv:Body>
<urn:find_binding maxRows="100"
serviceKey="uddi:juddi.apache.org:47069ffa-6afa-40f9-a40e-ce0c22bd017c"
listHead="0">
<urn:find_tModel>
<urn:findQualifiers>
<urn:findQualifier>approximateMatch</urn:findQualifier>
</urn:findQualifiers>
<urn:name>FRED</urn:name>
</urn:find_tModel>
</urn:find_binding>
</soapenv:Body>
</soapenv:Envelope>
was:
I have published serveral services some of which the tModel name associated
with a service includes a colon 'http://www.mysite.com/fred/service1' for
example. If I get the service key and then try and use find_binding and in the
find_tModel attribute set the name with the colon no matches are found:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:urn="urn:uddi-org:api_v3">
<soapenv:Header/>
<soapenv:Body>
<urn:find_binding maxRows="100"
serviceKey="uddi:juddi.apache.org:47069ffa-6afa-40f9-a40e-ce0c22bd017c"
listHead="0">
<urn:find_tModel>
<urn:findQualifiers>
<urn:findQualifier>approximateMatch</urn:findQualifier>
</urn:findQualifiers>
<urn:name>http//www.myservice.com/service1</urn:name>
</urn:find_tModel>
</urn:find_binding>
</soapenv:Body>
</soapenv:Envelope>
If I remove the colon from the tmodel name when I load juddi all requests
succeed.
Interestingly if I make a find_tModel call by itself it works with the colon
which seems odd.
Also worth noting is that I observed the same problem whether making to call
using soapUI or via the java client jar.
> find_binding using match on tmodel name ?
> -----------------------------------------
>
> Key: JUDDI-570
> URL: https://issues.apache.org/jira/browse/JUDDI-570
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.1, 3.1.0
> Environment: Windows NT
> Reporter: Steve Webb
> Assignee: Kurt T Stam
>
> My original description of this problem was misleading so I have reworded.
> I have used the client jar to create a publisher, business and around 20 or
> so services. All services at the moment have one binding each and obviously
> an associated tmodel. If I perform a find_binding search using the client jar
> or via soapUI and in the call set the service key and add a qualifier based
> on the tmodel name it finds the service details (see soap call below).
> However if two or more of the tmodel names are the same then the normal call
> returns no binding details.
> I'm not sure if this a bug or I am misunderstanding how I can obtain a
> binding for a service based on the tmodel name.
> Just for clarity I should mention we are using the tmodel name as a way of
> specifying the service version, this has been enforced from elsewhere, so as
> you can understand two services may have an interface version of say '1.0'
> and each would have a tmodel with the same name.
> By the way Pluto shows the full list of services and the correct endpoints,
> and a search on tmodels shows all tmodels including the ones with the same
> names.
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:urn="urn:uddi-org:api_v3">
> <soapenv:Header/>
> <soapenv:Body>
> <urn:find_binding maxRows="100"
> serviceKey="uddi:juddi.apache.org:47069ffa-6afa-40f9-a40e-ce0c22bd017c"
> listHead="0">
> <urn:find_tModel>
> <urn:findQualifiers>
> <urn:findQualifier>approximateMatch</urn:findQualifier>
> </urn:findQualifiers>
> <urn:name>FRED</urn:name>
> </urn:find_tModel>
> </urn:find_binding>
> </soapenv:Body>
> </soapenv:Envelope>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
