I have an xml schema in which I define a key with a selector like './/Task'. My xml instance document contains nested Tasks, however when I parse it with xerces 1.4.4 only the top level Tasks appear to resolve in the key (as though the selector was './Task'. Thus a keyref I defined using that key fails. My xml schema and instance were both validate fully in xmlspy, so the problem is not a schema/instance mistake. I noticed a previous message relating to this problem with no solution (http://marc.theaimsgroup.com/?l=xerces-j-user&m=100404030711923&w=2). Is this a known xerces bug or is something else going on?
--Rolf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
