RE: Imported, included schemas

getResourceByName. What is this? Method of what? -Original Message- From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 12:49 AM To: user@xmlbeans.apache.org Subject: Re: Imported, included schemas I think that this has been covered, but

java.lang.IllegalStateException: Cursor has been disposed

I have a message that is throwing java.lang.IllegalStateException: Cursor has been disposed I can't see what I am doing wrong. Any help would be most appreciated. Thanks in advance ... public Instruction fromMessage(Message msg) throws MessageConversionException {

RE: java.lang.IllegalStateException: Cursor has been disposed

I've found it... selectPath( instructionXpath ); returns void! From: Chris Snow [mailto:[EMAIL PROTECTED] Sent: 19 March 2008 10:02 To: user@xmlbeans.apache.org Subject: java.lang.IllegalStateException: Cursor has been disposed I have a

RE: Imported, included schemas

What is this? I mean method getResourceByName(). What is it belong to? Which class? -Original Message- From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 12:49 AM To: user@xmlbeans.apache.org Subject: Re: Imported, included schemas I think that this

RE: Imported, included schemas

returns the path to the Schema file inside the jar that it came from I don't use jar files. I open my xsd schemas with my types, elements, etc -Original Message- From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 12:49 AM To:

RE: Imported, included schemas

Denis, when you compile your schema in xmlbeans (using scomp), you get a jar. Inside this jar, there will be a copy of the xsd file containing your schema. SchemaType.getSourceName() returns a string which is the path to this file in the jar. One of the points Radu was making is that you should

Algorithm for saving CDATA blocks in XML Beans 2.2 ?

I see that XML Beans 2.3 provides some control over when the saver generates CDATA. The XML Options setSaveCDataLengthThreshold and setSaveCDataEntityCountThreshold allow any of the following configurations: Every text is CDATA Only text that has an entity is CDATA Only text longer than x chars

RE: Algorithm for saving CDATA blocks in XML Beans 2.2 ?

Steve, The javadoc for setSaveCDataLengthThreshold and setSaveCDataEntityCountThreshold seems to be quite clear: * CDATA will be used if the folowing condition is true: * textLength cdataLengthThreshold entityCount cdataEntityCountThreshold * The default value of

RE: Algorithm for saving CDATA blocks in XML Beans 2.2 ?

Cezar, If I am not mistaken, the older XML Beans version 2.2 does not does not support these options. Please clarify. Thanks, Steve -Original Message- From: Cezar Andrei [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 4:38 PM To: user@xmlbeans.apache.org Subject: RE:

What's wrong with the following XML??

Hello, I've beening using inst2xsd script to generate xsd from xml. I added relationships block to add some new features. After regenerating the xsd, I noticed that subComponents has been changed. before ... xs:element name=subComponents xs:complexType

RE: Algorithm for saving CDATA blocks in XML Beans 2.2 ?

Indeed the options weren't available but the algorithm and default values are the same. Cezar -Original Message- From: Steve Davis [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 3:49 PM To: user@xmlbeans.apache.org Subject: RE: Algorithm for saving CDATA blocks in XML

Re: What's wrong with the following XML??

I can see why inst2xsd tool is doing that. subComponents subComponent/ subComponent sequence/ /subComponent /subComponents The tools sees: subcomponent / and subComponentsequence / ... As 2 different types, if you want to correct that, you can