RE: jUDDI v2 compliance

[Karthick Sankarachary]

Title: 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: juddi-dev@ws.apache.org 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.