Forwarding reply from Sandy on the same question posted by Manish Balsara on xerces-j-dev.
-------- Original Message -------- Subject: Re: PSVI Date: Tue, 23 Jul 2002 11:25:16 -0400 From: [EMAIL PROTECTED] Reply-To: [email protected] To: [email protected] You cannot get occurrence information from element decls, because that's part of a particle, not part of the element decl. To get such information, you need to start from the complex type definition of "RequestVerb". You can call getParticle on such complex type to get it's content (a particle). getTerm on such particle would return a model group (a sequence). You can then get a list of particles from this model group. Each of the particle in the list has information about min/maxOccurs and its term (element declaration). How to represent annotations is still an open issue of PSVI interface design. Your opinion on this would be appreciated. Cheers, Sandy Gao Software Developer, IBM Canada (1-905) 413-3255 [EMAIL PROTECTED] "manish balsara" <[EMAIL PROTECTED] To: [email protected] com> cc: Subject: PSVI 07/23/2002 11:46 AM Please respond to xerces-j-dev Hi 1. How can I get particle information from XSElementDeclaration for local elements? For example, in the below example, how can I find el2 has minOccurs=1 / maxOccurs=10 and el3 has minOccurs=1 / maxOccurs=20 <xs:complexType name="RequestVerb"> <xs:complexContent> <xs:extension base="ConfirmableVerb"> <xs:sequence> <xs:element name="el2" type="xs:string" minOccurs="1" maxOccurs="10"/> <xs:element name="el3" type="xs:string" minOccurs="1" maxOccurs="20"/> <xs:element name="el4" type="xs:string"/> <xs:element name="el5" type="xs:string"/> </xs:sequence> <xs:attribute name="attr11" type="xs:string"/> </xs:extension> </xs:complexContent> </xs:complexType> 2. What are the plans for parsing Annotations? Would there be capability to parse the user defined annotations during schema parsing to avoid having to parse in PSVI? thanks manish --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
