XmlBean and SAXON 8.9

2007-12-18 Thread Hacking Bear
Hello, My XmlBean was running fine on SAXON8.8, but failed when the saxon jar is replaced with the 8.9 version (full package) I got the stack trace: java.lang.RuntimeException: Trying XBeans path engine... Trying XQRL... Trying Saxon... FAILED on declare namespace saml='urn:oasis:names:tc:SAML:

Using inst2xsd tool to generate schema

2007-12-18 Thread Zapo
Hi, I have the following XML file given and I am trying to generate schema for the below XML But I keep getting this error Could not read file: 'APITestcase.xml'. Characters larger than 4 bytes are not supported: byte 0x93 implies a length of more than 4 bytes Can any body point where I am

Re: Using inst2xsd tool to generate schema

2007-12-18 Thread Zapo
Thanks, I tried but that does not seem to work. Is it something to do with my XML file at all? Regards sunder But it Jacob Danner-2 wrote: Hi Zapo, My guess on quick glance is the @ sign in parameter name MATCHVALUE -jacobd On Dec 18, 2007 5:37 PM, Zapo [EMAIL PROTECTED] wrote: Hi,

Re: Using inst2xsd tool to generate schema

2007-12-18 Thread Jacob Danner
I just copied your instance into a text editor and I found your problem. You've got bad quotation marks around ENDPOINT and EXPECTEDRESULTS. Replace them with a text editor, save (in UTF-8 format), and give it another try. -jacobd On Dec 18, 2007 5:53 PM, Zapo [EMAIL PROTECTED] wrote: Thanks,

Re: Using inst2xsd tool to generate schema

2007-12-18 Thread Jacob Danner
Hi Zapo, My guess on quick glance is the @ sign in parameter name MATCHVALUE -jacobd On Dec 18, 2007 5:37 PM, Zapo [EMAIL PROTECTED] wrote: Hi, I have the following XML file given and I am trying to generate schema for the below XML But I keep getting this error Could not read file:

validation mechanism while constructing a new XML instance..

2007-12-18 Thread dave
This is related to validating a brand new XML instance WHILE being created programmatically using XMLBeans: Do you generally perform validation at the very end of completely creating an XML instance? If Yes, how would you correct these validation errors programmatically? It looks like a daunting