RE: [uddi-spec] Use of the final attribute in the UDDI V3 Schemas

[Luc Clément <luclclement@verizon.net>]

Sorry for the late reply; I'm catching up...

The final attribute was not set on the simple types you listed because that
we needed to allow simple types to reference our base types (e.g. uddiKey).
As such, setting the final attribute would preclude other types from
deriving from our base types which would prohibit 'bindingKey' for example
to derive from 'uddiKey'.

For this reason, the finalDefault attribute was not set on the schema
element given that it would have had the same effect of prohibiting
reference to our base types.

Luc

-----Original Message-----
From: John Colgrave [mailto:colgrave@hursley.ibm.com] 
Sent: Thursday, November 20, 2003 13:43
To: 'Max Voskob'; uddi-spec@lists.oasis-open.org
Subject: RE: [uddi-spec] Use of the final attribute in the UDDI V3 Schemas

Max,

Support for the final attribute is not mandatory in the JAX-RPC 1.1
Specification and the Standard Implementation (what used to be called a
Reference Implementation) maps anything that includes the final attribute to
the catch-all SOAPElement, which means that every operation in UDDI has a
return type of SOAPElement and an argument of SOAPElement, which is not very
useful.

Removing the final attribute removes one of the obstacles to getting a
useful Java mapping from the UDDI WSDL/Schema, and I was wondering if a
better approach would be to remove all uses of final from the normative
schemas and replace them with uses of finalDefault on the various schema
elements, hoping that the tools will not look at the schema element itself,
or at least will happily ignore a finalDefault attribute if they find one.

John Colgrave
IBM


> -----Original Message-----
> From: Max Voskob [mailto:max.voskob@paradise.net.nz]
> Sent: 19 November 2003 21:04
> To: John Colgrave; uddi-spec@lists.oasis-open.org
> Subject: Re: [uddi-spec] Use of the final attribute in the UDDI V3 
> Schemas
> 
> John,
> 
> Please, pardon my ignorance, but how does the final attribute affect 
> the code generation?
> 
> Cheers,
> Max
> 
> 
> ----- Original Message -----
> From: "John Colgrave" <colgrave@hursley.ibm.com>
> To: <uddi-spec@lists.oasis-open.org>
> Sent: Wednesday, November 19, 2003 11:58 PM
> Subject: [uddi-spec] Use of the final attribute in the UDDI V3 Schemas
> 
> 
> > I have a couple of questions relating to the use of the final 
> > attribute
> in
> > the UDDI V3 schemas, which have come up during my work on generating 
> > a JAX-RPC 1.1 client for UDDI 3.0.1:
> >
> > 1 Why is the final attribute specified on almost all of the elements 
> > and types rather than specifying the finalDefault attribute on the 
> > schema as
> a
> > whole?
> >
> > 2 Why do the following not have the final attribute:
> > uddi_v3.xsd
> > simpleType name="uddiKey"
> > simpleType name="findQualifier"
> > simpleType name="keyName"
> > simpleType name="keyValue"
> > simpleType name="sortCode"
> > simpleType name="useType"
> > complexType name="findQualifiers"
> > simpleType name="validationTypeAnyURI4096"
> > simpleType name="validationTypeString50"
> > simpleType name="validationTypeString80"
> > simpleType name="validationTypeString255"
> > simpleType name="validationTypeString4096"
> > simpleType name="validationTypeString8192"
> > uddi_v3subscription.xsd
> > simpleType name="chunkToken"
> > element name="maxEntities"
> > element name="endPoint"
> >
> > I have not looked at the other schemas, these are the only two that
> affect
> > the JAX-RPC work.
> >
> > John Colgrave
> > IBM
> >
> >
> >
> >
> > To unsubscribe from this mailing list (and be removed from the 
> > roster of
> the OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/uddi-
> spec/members/leave_workgroup.php.
> >
> >


To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgro
up.php.