Re: jUDDI v2 compliance

Wed, 17 May 2006 19:25:12 -0700

All create_database.sql scripts have been updated to include these TModels and have been committed to Subversion.  Only the scripts for HSQLDB and MySQL have been tested however.
 
Steve

 
On 5/17/06, Steve Viens <[EMAIL PROTECTED]> wrote:
The following TModels will be added to the various jUDDI create database script.
 

uddi-org:wsdl:types
uuid:6E090AFA-33E5-36EB-81B7-1CA18373F457

uddi-org:xml:namespace
uuid:D01987D1-AB2E-3013-9BE2-2A66EB99D824

uddi-org:xml:localName
uuid:2EC65201-9109-3919-9BEC-C9DBEFCACCF6

uddi-org:wsdl:portTypeReference
uuid:082B0851-25D8-303C-B332-F24A6D53E38E

uddi-org:protocol:soap
uuid:AA254698-93DE-3870-8DF3-A5C075D64A0E

uddi-org:protocol:http
uuid:6E10B91B-BABC-3442-B8FC-5A3C8FDE0794

uddi-org:wsdl:categorization:protocol
uuid:4DC74177-7806-34D9-AECD-33C57DC3A865

uddi-org:wsdl:categorization:transport
uuid:E5C43936-86E4-37BF-8196-1D04B35C0099

uddi-org:wsdl:address
uuid:AD61DE98-4DB8-31B2-A299-A2373DC97212

Steve

 
On 5/17/06, Steve Viens <[EMAIL PROTECTED]> wrote:
Of course.
 
I'll add this to JIRA.

 
On 4/13/06, Anne Thomas Manes <[EMAIL PROTECTED] > wrote:
The tModels defined the the "Using WSDL with a UDDI Registry" technical note are not defined as canonical tModels in the UDDI spec, but a UDDI v2-compliant registry should come with those tModels preloaded. It's essential that these tModels be created using the appropriate tModel keys, so a user can't just create the tModels arbitrarily.

Is there someway that these tModels could be added to the 'create_database.sql' script?
 

Anne


On 4/10/06, Karthick Sankarachary < [EMAIL PROTECTED]> wrote:

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