I got everything converted to plain content types with the exception
of the ServiceProvider element in the service-jar.xsd. This element
seems to allow the nested properties file as usual plus either a
<properties-file> element or a <lookup> element. It doesn't look
like either of the classes for these elements are used anywhere in
the code, so I'm thinking about removing them.
Does anyone remember what these are for? If they are important, can
we switch them to attributes so we can make service provider a simple
type.
The schema for these elements follow.
-dain
<xsd:element name="ServiceProvider">
<xsd:complexType mixed='true'>
<xsd:choice minOccurs="0" maxOccurs="1">
<xsd:element ref="properties-file" minOccurs="0"
maxOccurs="1"/>
<xsd:element ref="lookup" minOccurs="0" maxOccurs="1"/>
</xsd:choice>
<xsd:attribute name="id" type="xsd:string" use="required"/>
<xsd:attribute name="provider-type" type="ProviderTypes"
use="required"/>
<xsd:attribute name="display-name" type="xsd:string"
use="optional"/>
<xsd:attribute name="description" type="xsd:string"
use="optional"/>
<xsd:attribute name="class-name" type="ClassName"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="properties-file">
<xsd:complexType>
<xsd:attribute name="file" type="xsd:string" use="required"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="lookup">
<xsd:complexType>
<xsd:attribute name="jndi-name" type="xsd:string"/>
<xsd:attribute name="jndi-provider-id" type="xsd:string"/>
</xsd:complexType>
</xsd:element>
