You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@juddi.apache.org by Steve Viens <sv...@attbi.com> on 2003/06/01 00:47:05 UTC
RE: [juddi-Users] Problem accessing jUDDI 0.7 with JAXR
Mike you've probably uncovered a significant number of bugs here. :(
...but it's great to know about them now! I've summarized them below.
Would you mind submitting a bug ... to make it easy, you can just
copy-paste the text below.
jUDDI Bug Tracker: http://sourceforge.net/tracker/?group_id=42875
<http://sourceforge.net/tracker/?group_id=42875&atid=434422>
&atid=434422
Generally speaking, jUDDI's XML "Handlers" do not marshal the objects
into XML as the UDDI v2.0 schema dictates. Elements are added to parent
elements in an order that may not coincide with the UDDI v2.0 XML
Schema. Here are the jUDDI-XML Schema bugs I've identified in the jUDDI
response below. I'm sure there are others.
ContactHandler
- phone element should be positioned before email element
BusinessEntity (should be written out in this order)
- businessServices should precede categoryBag and identifierBag element
- categoryBag element should follow identifierbag element
- identifierBag element should not be included if empty
- discoveryURLs element should not be included if empty
BindingTemplate
- description should precede accessPoint
These are not exactly show-stopper bugs but will come up whenever
someone uses a tool that expects the XML to conform to the schema
(UDDI4j doesn't much care, neither does JWSDP I believe).
Steve
-----Original Message-----
From: juddi-users-admin@lists.sourceforge.net
[mailto:juddi-users-admin@lists.sourceforge.net] On Behalf Of Andy
Cutright
Sent: Friday, May 30, 2003 7:27 PM
To: juddi-users@lists.sourceforge.net
Subject: Re: [juddi-Users] Problem accessing jUDDI 0.7 with JAXR
the lack of a discovery URL is a known issue. i believe this has been
fixed, but i haven't tested it yet. i'm going to have look a bit closer
at the spec about the empty identifierBag element.
cheers,
andy
Michael Woinoski wrote:
As Steve and Anou suggested, I used tcpmon to peek at the messages
exchanged
between the registry and the jaxr client. With both juddi and jwsdp, the
jaxr
calls resulted 3 SOAP messages to the UDDI registry. One interesting
thing is
that the sequence of client requests is different, even though the only
code
change in the client was to replace the url
"http://localhost:7777/juddi/inquiry"
<http://localhost:7777/juddi/inquiry> with
"http://localhost:7777/RegistryServer/RegistryServerServlet"
<http://localhost:7777/RegistryServer/RegistryServerServlet> :
jwsdp SOAP messages: find_business, get_businessDetail,
get_bindingDetail
juddi SOAP messages: find_business, get_businessDetail,
get_serviceDetail
However, in juddi's response to the get_businessDetail request, the
<businessEntity> child of the <businessDetail> element does not match
the UDDI
schema, while the jwsdp message does match the schema:
<xsd:complexType name="businessEntity">
<xsd:sequence>
<xsd:element ref="uddi:discoveryURLs" minOccurs="0" />
<xsd:element ref="uddi:name" maxOccurs="unbounded" />
<xsd:element ref="uddi:description" minOccurs="0"
maxOccurs="unbounded" />
<xsd:element ref="uddi:contacts" minOccurs="0" />
<xsd:element ref="uddi:businessServices" minOccurs="0" />
<xsd:element ref="uddi:identifierBag" minOccurs="0" />
<xsd:element ref="uddi:categoryBag" minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="businessKey" type="uddi:businessKey"
use="required" />
<xsd:attribute name="operator" type="string" use="optional" />
<xsd:attribute name="authorizedName" type="string" use="optional" />
</xsd:complexType>
For the sake of brevity, I appended only the two different
<businessDetail>
responses below. Let me know if it would helpful to see all the other
requests
and responses as well.
Thanks,
Mike
-------------- jUDDI: response to get_businessDetail
---------------------
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
<http://schemas.xmlsoap.org/soap/envelope/>
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
<http://www.w3.org/2001/XMLSchema>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<http://www.w3.org/2001/XMLSchema-instance> >
<soapenv:Body>
<businessDetail generic="2.0" operator="jUDDI.org"
xmlns="urn:uddi-org:api_v2">
<businessEntity authorizedName="Learning Tree Java Web Services"
businessKey="3A4C1200-907B-11D7-B874-ADAF48E90910" operator="jUDDI.org">
<name xml:lang="en">Rainforest, Inc.</name>
<description xml:lang="en">Music and video
wholesaler</description>
<contacts>
<contact>
<personName>R. F. Jagger</personName>
<email>rainforest@glamourshack.com</email>
<phone>302-555-4321</phone>
</contact>
<contact useType="publisher">
<personName>Learning Tree Java Web Services</personName>
</contact>
</contacts>
<categoryBag>
<keyedReference keyName="Other Miscellaneous Nondurable
Goods
Wholesalers" keyValue="42299"
tModelKey="uuid:C0B9FE13-179F-413D-8A5B-5004DB8E5BB2"/>
</categoryBag>
<identifierBag/>
<discoveryURLs/>
<businessServices>
<businessService
businessKey="3A4C1200-907B-11D7-B874-ADAF48E90910"
serviceKey="3A90BC20-907B-11D7-B874-863AF5D8A4E8">
<name xml:lang="en">RainOrderService</name>
<description xml:lang="en">Order
recordings</description>
<categoryBag/>
<bindingTemplates>
<bindingTemplate
bindingKey="3AA94D30-907B-11D7-B874-F72311115D97"
serviceKey="3A90BC20-907B-11D7-B874-863AF5D8A4E8">
<accessPoint
URLType="http://localhost:8080/rainservice/RainAccessorService"
<http://localhost:8080/rainservice/RainAccessorService>
>http</accessPoint>
<tModelInstanceDetails/>
<description>Ordering recording</description>
</bindingTemplate>
</bindingTemplates>
</businessService>
</businessServices>
</businessEntity>
</businessDetail>
</soapenv:Body>
</soapenv:Envelope>
---------------- JWSDP: response to get_businessDetail ----------------
<soap-env:Envelope
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
<http://schemas.xmlsoap.org/soap/envelope/> >
<soap-env:Header></soap-env:Header>
<soap-env:Body>
<businessDetail xmlns="urn:uddi-org:api_v2" generic="2.0"
operator="Sun
Microsystems Inc." truncated="false">
<businessEntity authorizedName="testuser"
businessKey="f565de7f-17f5-65de-ac52-ee9df25799b6" operator="Sun
Microsystems
Inc.">
<discoveryURLs>
<discoveryURL
useType="getUrl">http://localhost:8080/registry-server/businessEntity?bu
sinessKey=f565de7f-17f5-65de-ac52-ee9df25799b6</discoveryURL>
</discoveryURLs>
<name xml:lang="en">Rainforest, Inc.</name>
<description xml:lang="en">Video and music
wholesaler</description>
<contacts>
<contact>
<description xml:lang="en"></description>
<personName>R. F. Jageger</personName>
<phone useType="">302-555-4321</phone>
<email>rainforest@glamourshack.com</email>
</contact>
</contacts>
<businessServices>
<businessService
businessKey="f565de7f-17f5-65de-ac52-ee9df25799b6"
serviceKey="f565de7f-17f5-65de-cf04-305ffc28afdc">
<name xml:lang="en">RainOrderService</name>
<description xml:lang="en">Order
recordings</description>
<bindingTemplates>
<bindingTemplate
bindingKey="f565de7f-17f5-65de-4b97-687d7c031474"
serviceKey="f565de7f-17f5-65de-cf04-305ffc28afdc">
<description xml:lang="en">Order
recording</description>
<accessPoint
URLType="http">http://localhost:8080/rainservice/RainAccessorService</ac
cessPoint>
<tModelInstanceDetails></tModelInstanceDetails>
</bindingTemplate>
</bindingTemplates>
</businessService>
</businessServices>
<categoryBag>
<keyedReference keyName="Other Miscellaneous Nondurable
Goods
Wholesalers" keyValue="42299"
tModelKey="uuid:C0B9FE13-179F-413D-8A5B-5004DB8E5BB2"></keyedReference>
</categoryBag>
</businessEntity>
</businessDetail>
</soap-env:Body></soap-env:Envelope>
-----Original Message-----
From: juddi-users-admin@lists.sourceforge.net
[mailto:juddi-users-admin@lists.sourceforge.net] On Behalf Of Michael
Woinoski
Sent: Tuesday, May 27, 2003 9:16 PM
To: jUDDI mailing list
Subject: [juddi-Users] Problem accessing jUDDI 0.7 with JAXR
Hi. (Sorry for the long post, but I thought the details might help.) I
installed jUDDI 0.7 and MySQL on W2K to replace the UDDI registry
bundled with Sun's JWSDP 1.1. jUDDI seems happy enough; I can use the
JAXR browser from JWSDP to publish to and search the jUDDI registry.
However, when I try to access the registry with the JAXR implementation
from JWSDP, the code connects to jUDDI successfully and gets some info
but then dies with a ClassCastException from one of the Castor classes.
The same code works fine with the JWSDP registry.
------------------------------------------------------- This SF.net
email is sponsored by: eBay Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________ juddi-users mailing list
juddi-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/juddi-users