Hi Neil,
Thanks for your help.
I'm afraid I'm experiencing the problem w/ the CVS version I grabbed 3
hours ago, after Lisa fixed another bug that was, well, buging me ;-)
As for the test case, I can give you the schema I'm workig on (14 files or
so) or I can try and write a small one, based on those files and my
understanding of the problem ..
Regards
--
Etienne
Neil
Graham/Toronto To: [EMAIL PROTECTED]
/[EMAIL PROTECTED] cc:
Subject: Re: Weird inclusion
problem
06/19/2001
02:17 PM
Please respond
to
xerces-j-user
Hi Etienne,
Are you using Xerces 1.4.0 or a version from CVS? This sounds like a
problem that I fixed a couple of weeks ago.
If you are experiencing this problem with the CVS codebase though, please
send a test case along.
Thanks,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 416-448-3519, T/L 778-3519
E-mail: [EMAIL PROTECTED]
Etienne Roy/Watson/[EMAIL PROTECTED] on 06/19/2001 02:03:15 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Weird inclusion problem
Hi all,
AFAIK, I am allowed to declare 2 attributes with the same name provided
they're not in the same scope.
So the following snippet is valid:
<attribute name="foo" type="string"/>
<attributeGroup name="fooGroup">
<attribute name="foo" type="string"/>
</attributeGroup>
and XercesJ is Ok validating that but....
when that schema is imported in another schema, that raises isues like:
Schema error: prefix : [importing_schema] cannot be resolved to a URI.
And the validator is not able to find refs inside the importing schema
anymore !
Both schema are valid without the import statement.
The importing schema is ok when I comment out the globally declared
attribute in the imported one !
Any idea about that behaviour that could help me ? Do you want me to write
a test case reproducing that problem ?
Thanks for your help
--
Etienne
---------------------------------------------------------------------
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]
