RE: Saxon 8.1.1 dependency saxon namespaces

2006-01-05 Thread Cezar Andrei
Marius, See a previous answer on this topic: http://www.mail-archive.com/user@xmlbeans.apache.org/msg00836.html We're still committed to have XMLBeans working with a 1.4 JDK, so we cannot apply your patch right now. But starting with v3 we'll most probably drop this requirement and your patch

Problem with element defined with xs:any

2006-01-05 Thread Jim McMaster
Using xmlbeans-2.0, although I get the same result with 2.1. I have defined an element in a schema as follows: xs:element name=blackBox xs:complexType xs:sequence xs:any minOccurs=0 nameSpace=##any maxOccurs=unbounded

RE: XmlBeans and xml digitail signature

2006-01-05 Thread Radu Preotiuc-Pietro
Title: Message I have thought about a feature along those lines. One place it would certainly be useful is when XmlBeans *has* to create prefix declarations because user code is setting a QName value (directly or indirectly) and so it is necessary to ensure that the meaning of that QName is

RE: Html forms - xmlBeans - xml document

2006-01-05 Thread Radu Preotiuc-Pietro
A couple of comments: - why do you say that you have to use xget/xset some times and set/get other times? It seems to me you should be able to standardize on one approach, the one that suits you best - we have an example of using Velocity + XmlBeans in the samples section on the website

RE: Problem with element defined with xs:any

2006-01-05 Thread Jim McMaster
On Thursday, January 05, 2006 3:55 PM, Radu Preotiuc-Pietro mailto:[EMAIL PROTECTED] wrote: Hm, actually I believe ELEMENT_CONTENT is what it should be. The xs:any tells you that you can have any number of arbitrarily named elements, but you can't have text as a direct child of blackBox.