From: "James Strachan" <[EMAIL PROTECTED]>
> > That could be a bug. The XSD document I've been using didn't use the
xsd:
> > prefix. e.g. look at xml/schema/personal.xsd
> > I'll look into that one - I should add a JUnit test case to the build
that
> > uses both a prefix based and non prefixed based XSD document.
>
> AFAIK xsd:string is working at the moment.
I was wrong, it goes to shows how much I know! :)
There was a bug in the handling of xsd:string and using schema documents
with a prefix (xsd:element and so on).
It turns out that there was also a bug was in the JUnit test case that
wasn't even testing the prefix-schema test case so I thought it worked when
it didn't. Thanks for your help Toby.
I've fixed this bug and checked it into CVS.
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dom4j-user
