Hi again,
that's stange. I'll try it again.
Thank you for helping and spending so much time for my problem!
Greets
Igor :-)
Michael Glavassevich schrieb:
> Hi Igor,
>
> This works for me. I can only reproduce that error if I revert the patch
> [1]. It's likely you have another (old) copy of X
Hi Igor,
This works for me. I can only reproduce that error if I revert the patch
[1]. It's likely you have another (old) copy of Xerces in your environment
which is getting picked up instead of the one you think you're using.
[1]
http://svn.apache.org/viewvc/xerces/java/trunk/src/org/apache/x
Hi,
I've tried also with a namespace like this: http://domain.de/a/b/c/公司
/d, here the error was
...but the target namespace of the schema document is
'http://domain.de/a/b/c/%E5%85%AC%E5%8F%B8/d'.
Is there no way to use this chars (公司) directly in the namespace?
Greets
Igor :-)
[EMAIL P
Hi Michael,
I tryed with 2.6.2 and ne newest 2.9 Xerces. With both the same effect.
greets
igor :-)
Michael Glavassevich schrieb:
> Hi Igor,
>
> Which version of Xerces were you using when you tried this? There was a
> bug [1] in this area that was fixed [2] in Xerces 2.7.0.
>
> [1] http://iss
On Friday, 01/19/2007 at 05:58 GMT, Mark Goodhand <[EMAIL PROTECTED]> wrote:
> Where is the "absolute URI reference" requirement? Is it an XML
> Namespaces constraint or a Schema constraint?
XML Namespaces errata, after an extended and very painful debate over how
namespaces should be tested fo
On 19 Jan 2007, at 16:00, [EMAIL PROTECTED] wrote:
The first problem to fix is that this isn't a legal namespace name.
Namespace names must be absolute URI references -- which means they
have to start with a scheme, and then should follow that scheme's
syntax.
Where is the "absolute URI re
Hi Igor,
Which version of Xerces were you using when you tried this? There was a
bug [1] in this area that was fixed [2] in Xerces 2.7.0.
[1] http://issues.apache.org/jira/browse/XERCESJ-1039
[2]
http://svn.apache.org/viewvc/xerces/java/trunk/src/org/apache/xerces/impl/dv/xs/AnyURIDV.java?r1=32
The first problem to fix is that this isn't a legal namespace name.
Namespace names must be absolute URI references -- which means they have to
start with a scheme, and then should follow that scheme's syntax.
They also use URI character escaping conventions when necessary; I haven't
checked the s
Hello everybody,
i've a courios problem with schema-validation. There is a problem with
the namespace, which contains 'strange' UTF-8-characters (codes: 516C /
53F8). Is it posible that xerces do something wrong with the
schema-targetnamespace??
Thanks for helping :-)
igor :-)
Here some code-s
