Re: Ant task generating bad code

Nah I don't think so because my ant scipt blows away the directory before it gets going. I will run some tests and see if I can figure what exactly is different between the two .jar files. JonathanOn 10/26/05, Radu Preotiuc-Pietro <[EMAIL PROTECTED]> wrote: Those kind of things are very har

Re: nilable and validate()

Thank you. - Original Message - From: Cezar Andrei To: user@xmlbeans.apache.org Sent: Tuesday, October 25, 2005 3:12 PM Subject: RE: nilable and validate() There is an earlier discussion on this topic, please see:   http://www.mail-archive.com/user@xmlb

RE: nilable and validate()

There is an earlier discussion on this topic, please see:   http://www.mail-archive.com/user@xmlbeans.apache.org/msg00512.html   Cezar   From: Samuel B. Quiring [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 25, 2005 3:10 PM To: user@xmlbeans.apache.org Subject: nilable a

FW: Legal issue: jsr173 API jar licensing

Since revision 312915, XMLBeans uses a new jsr173 bundle containing only the jsr173 API, this bundle is licensed under an Apache ASF license. In order to pick up and build with the new bundle, please execute: ant clean.jars clean deploy Many thanks to Lawrence Jones and Cliff Schmidt, w

Re: Remove namespace prefix from XmlBean

If you just use XmlOptions.setUseDefaultNamespace(), it will still include the default namespace marker at the top like so: ... This isn't what you asked for in your email, but is probably what you want. If however you're dealing with a dumb XML parser that isn't namespace-aware or something l

RE: empty Attribute types cause error

Title: Message Basically, in your case, we are dealing with an invalid doc, since "" (empty string) is not in the value space of the "float" type. That being said, XmlBeans makes efforts to give you access to your data even for invalid documents. But this case, I think, falls under the catego

RE: Remove namespace prefix from XmlBean

Note that the two documents are _different_, XmlBeans will output the one that you created. Try using XmlOptions.setUseDefaultNamespace() when you print out the document and see how that looks. Radu -Original Message- From: R. C. Hill [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 19

RE: character sets

Also, Christian, could you try using "ISO8859_1" rather than "ISO-8859-1" for the encoding string in your code? XmlBeans is using the Java names for the encodings, which seemed more consistent than using the IANA names (so you can get the encoding from other Java code and set it directly etc). Of c

nilable and validate()

Greetings,   I have a schema fragment that looks like this:                             I'm calling validate() to verify the java object after I fill it with values.  For the three fields with minOccurs="0", if I set value to null validate returns this erro

RE: Ant task generating bad code

Title: Message Those kind of things are very hard to diagnose, especially over e-mail. Since scomp works correctly, I have to assume that this is ant's doing, maybe some dependency checking causing some classes not to get rebuilt?   Radu -Original Message-From: rabidgremlin

RE: catalog-support in xmlbean-ant-task

Have you tried the "catalog" attribute on the ant task? I haven't tried it myself, but from looking at the code, looks like it's what you want (of course, we also have this option on the "scomp" script and I have successfully used it in that context). Radu -Original Message- From: Johanne