I am having the exact same issue trying to publish my service with the
overviewDoc element :
<instanceDetails>
<overviewDoc>
<description>myExampleService
schema</description>
<overviewURL useType="XML
Schema">https://cypher.fgm.com/mdr/ns/myschema1.xsd</overviewURL>
</overviewDoc>
</instanceDetails>
juddi claims to follow uddi v3 api, but looks like it is sensitive about the
sequence of the overviewURL and description.
If I change my overviewDoc element to the below it works.
<overviewDoc>
<overviewURL useType="XML
Schema">https://cypher.fgm.com/mdr/ns/myschema1.xsd</overviewURL>
<description>myExampleService
schema</description>
</overviewDoc>
We are looking to migrate from HP to juddi, but looks like we cannot
directly use a uddi v3 client which is generated based on the uddi_v3.xsd.
Any idea how to change juddi to validate against the uddi v3 schema and not
its own generated schema?
Irwin, Wayne wrote:
>
> I installed JUddi by installing juddi-portal-bundle-3.0.1.zip and
> running it. I then configured an ESB product to use this instance as
> it's registry. The "Test Connection" function works from the ESB to
> JUddi. So far so good.
>
> When attempting to publish a web service from the ESB to JUddi, it
> throws a fault.
>
> Here is the request sent to JUddi
> ============================================
> POST /juddiv3/services/publish HTTP/1.1
> SOAPAction: "save_tModel"
> Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg,
> *; q=.2, */*; q=.2
> Content-Type: text/xml;charset="utf-8"
> User-Agent: JAX-WS RI 2.1.4-b01-
> Host: xxxxxxxx:8889
> Connection: keep-alive
> <?xml version="1.0" encoding="UTF-8"?>
> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/";>
> <S:Body>
> <ns2:save_tModel xmlns="http://www.w3.org/2000/09/xmldsig#";
> xmlns:ns2="urn:uddi-org:api_v3"
> xmlns:ns3="urn:uddi-org:sub_v3">
>
> <ns2:authInfo>authtoken:104cd94c-cc2b-4a6c-b9bf-70fb8d295ab1</ns2:authIn
> fo>
> <ns2:tModel>
> <ns2:name>ServiceDiagnosticService</ns2:name>
> <ns2:overviewDoc>
> <ns2:description>the original WSDL
> document</ns2:description>
> <ns2:overviewURL
> useType="wsdlInterface">http://L7Gateway.gwl.bz:8080/ssg/wsdl?serviceoid
> =491520</ns2:overviewURL>
> </ns2:overviewDoc>
> <ns2:overviewDoc>
> <ns2:description>Technical Note "Using WSDL in a
> UDDI Registry, Version 2.0.2"</ns2:description>
> <ns2:overviewURL
> useType="text">http://www.oasis-open.org/committees/uddi-spec/doc/tn/udd
> i-spec-tc-tn-wsdl-v202-20040631.htm</ns2:overviewURL>
> </ns2:overviewDoc>
> <ns2:categoryBag>
> <ns2:keyedReference keyValue="portType"
> tModelKey="uddi:uddi.org:wsdl:types"/>
> <ns2:keyedReference keyName="portType namespace"
>
> keyValue="urn:ca:gwl:aisc:service:StubDiagnosticService"
> tModelKey="uddi:uddi.org:xml:namespace"/>
> </ns2:categoryBag>
> </ns2:tModel>
> </ns2:save_tModel>
> </S:Body>
> </S:Envelope>
>
> And the response
> ============================================
> <?xml version="1.0" encoding="UTF-8"?>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
> <soap:Body>
> <soap:Fault>
> <faultcode>soap:Client</faultcode>
> <faultstring>Unmarshalling Error: cvc-complex-type.2.4.a:
> Invalid content was found starting with element 'ns2:overviewURL'. One
> of '{"urn:uddi-org:api_v3":description}' is expected. </faultstring>
> </soap:Fault>
> </soap:Body>
> </soap:Envelope>
>
>
> From what I can tell, the request is valid.
>
> Thanks
> Wayne Irwin, I.S.P. <http://www.cips.ca/certification> ITCP
> Senior Infrastructure Specialist
> Application Integration Solution Centre (AISC)
> Great-West Life Assurance Company
> 100 Osborne Street North
> Winnipeg MB Canada R3C 3A5
> Tel (204) 946-7999
> http://www.greatwestlife.com
>
> The contents of this communication, including any attachments,
> are confidential and may be privileged. If you are not the intended
> recipient (or are not receiving this communication on behalf of the
> intended recipient), please notify the sender immediately and delete or
> destroy this communication without reading it, and without making,
> forwarding, or retaining any copy or record of it or its contents. Thank
> you. Note: We have taken precautions against viruses, but take no
> responsibility for loss or damage caused by any virus present.
>
>
>
--
View this message in context:
http://old.nabble.com/Valid-Save_tModel-request-throwing-fault-tp28002905p31743019.html
Sent from the jUDDI - User mailing list archive at Nabble.com.
