Hi Kiran,
Since I'm not sure the users list has been kept quite up to date with the status of features in the CVS repository, here's where I think we're at: block and final are now supported. fixed/default values of elements are supported except in the case of mixed content models (coming soon). Quite a number of constraints are supported, and more will be added soon. I think Elena is working on nillable as we write. Support for identity constraints will also hopefully be improved soon. Alpha testing on any or all of these features is always appreciated; all you need to do is checkout Xerces from CVS (instructions available off of the http://xml.apache.org site) and build it. Hope that helps, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 416-448-3519, T/L 778-3519 E-mail: [EMAIL PROTECTED] Kiran Halwai <[EMAIL PROTECTED]>@us.ibm.com on 04/20/2001 09:25:21 AM Please respond to [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Clarification: key/keyref Well, I started with the 'Xerces Java Parser 1.3.1 Release' but on http://xml.apache.org/xerces-j/schema.html, I saw the list of 'Features NOT Supported'. It does not support some of the things I need and one of that is constraints. I confirmed following Bug (1) and stopped using this parser. Is there any (alpha/final) release around that supports following unsupported features in 1.3.1? Features NOT Supported in 1.3.1 Constraints in Chapter 5 and elsewhere in the specifications Nullable Block and final Fixed and default values of elements Thank you very much. Regards, Kiran Andy Clark wrote: > Kiran Halwai wrote: > > functionality? I am using Oracle parser. > > Step 1: Uninstall Oracle parser. ;) > Step 2: Install Xerces-J parser. > Step 3: Try example again. > > > Any help would be greatly appreciated. > > Seriously, I ran into several problems using your sample with > Xerces-J but it's mostly various bugs interacting in Xerces. > Bug 1) If the Schema uses a named prefix (i.e. xsd:schema > instead of just schema) then the parser can't properly create > the identity constraints. Bug 2) Putting schema grammar in > default namespace solves Bug 1 but introduces another problem. > The parser will emit errors that it can't find the element > declarations for "my:ValidSet" and "my:Values". BUT... it > still creates the identity constrains and validates them in > the instance document correctly. Strange, indeed. > > -- > Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
