Hi sssanghavi,
The code on the trunk is tested against HP Systinet. I think you will
need either use that, or wait till 3.1.0 comes out, which should be a
matter of days.
Cheers,
--Kurt
On 5/31/11 1:43 PM, sssanghavi wrote:
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?
