OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: 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





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]