RE: jUDDI v2 compliance

Mon, 10 Apr 2006 05:38:34 -0700

Title: jUDDI v2 compliance

You may be right. The tModelKeys specific to WSDL are missing in JUDDI’s ‘create_database.sql’ script, so apparently they aren’t available to you out of the box.

 

Your best bet is to find a provider-agnostic mapping of the WSDL metadata to UDDI metadata, which conforms to the OASIS technical note, and apply that in the context of JUDDI.

 

Have you looked at pre-canned WSDL-UDDI solutions, such as http://sourceforge.net/projects/wsdl4reg? For all we know, it already addresses all of your mapping concerns, not just at the run-time level but design-time too.


Best Regards,
Karthick Sankarachary
Lead Software Engineer

P +91 80 5125 8908 | F +91 80 5125 8901
www.webMethods.com

From: Andrei Kazyrevich [mailto:[EMAIL PROTECTED]
Sent: Monday, April 10, 2006 5:46 PM
To: [email protected]
Subject: RE: jUDDI v2 compliance

 

Karthick,

 

Nope, I'm curious about v2 compliance and not v3 one.

 

The reason is that accordingly the OASIS technical note (http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v202-20040631.htm  please see the "Mapping WSDL 1.1 in UDDI V2" section), one could publish WSDL artifacts into a UDDI registry in a more flexible manner. That can be done by mapping entries from a single WSDL into more than one UDDI structure (!). So, multiple UDDI tModels would be created from a single WSDL file, each covering  some part of the latter.

 

And it means that some of tModels should be categorized via so called canonical tModels that MUST (I guess) present in the UDDI registry.

Stating that such tModels are omitted in jUDDI I mean that they are omitted in the SQL scripts for jUDDI databases.

 

So, the approach from OASIS is not applicable for jUDDI. Right?

Thanks,

Andrew

 

 

From: Karthick Sankarachary [mailto:[EMAIL PROTECTED]
Sent: Monday, April 10, 2006 3:02 PM
To: [email protected]
Subject: RE: jUDDI v2 compliance

In general, v1/v2 tModel keys are GUID-based, and v3 tModel keys are URI-based. For more information on mapping between v2 and v3 keys, I refer you to http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908262.

 

So, you probably want to map your “evolved” keys to the corresponding “uuid” keys, using the algorithm specified in that spec, and hopefully JUDDI will recognize the types you’re looking for. If not, you may have to explicitly create those categories from scratch yourself.

 


Best Regards,
Karthick Sankarachary
Lead Software Engineer

P +91 80 5125 8908 | F +91 80 5125 8901
www.webMethods.com

From: Andrei Kazyrevich [mailto:[EMAIL PROTECTED]
Sent: Monday, April 10, 2006 5:07 PM
To: [email protected]
Subject: jUDDI v2 compliance

 

 

Hi there!
jUDDI claims to be v2-compliant but I don't see canonical tModels from the v2 spec! E.g., "uddi-org:wsdl:types" or "uddi-org:xml:namespace" or "uddi-org:xml:localName" etc.
I wonder if I had added them manually via sql "insert" commands, would I have obtained the v2 compliance?
Or does anybody think jUDDI could be v2 without these canonical tModels?
Or possibly I am missing something...
Thank you,
Andrew
PS. tModel details are taken from http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v202-20040631.htm#_Toc76437807

 

CONFIDENTIALITY CAUTION AND DISCLAIMER
This message is intended only for the use of the individual(s) or entity(ies) to which it is addressed and contains information that is legally privileged and confidential. If you are not the intended recipient, or the person responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. All unintended recipients are obliged to delete this message and destroy any printed copies.

Reply via email to