Hi (included dev list as this may be too in depth for the user list)
I'm using XmlBeans 2.3.0 in a Weblogic 9.2 J2EE web application (JVM
1.5.0_10). We use XmlBeans to compile our schema and these effectively
become our domain objects. These are looked up from the DB, stored in
the Http Session
Hi All!
I have one XML file which gives me trouble.
The XML is really simple - just root element, subelement and a lot of
spaces around.
I have to attach the file since adding or removing just one character in
it makes it parsable again (very strange).
I really hope that somebody can help me t
Hi Paul,
When doing "local" updates a simple synchronization is done on the
synchronization domain of that XMLObject, we call it Locale. By default, each
new document XMLObject is created with a new Locale.
But when there is an update operation involving XMLObjects from two Locale-s,
we
Hi Paul,
I can tell you what the synchronization strategy is. Each XmlObject belongs to
an xml document, and each xml document belongs to what XmlBeans calls a Locale
object (nothing to do with the Java Locale). This is the synchronization domain
for XmlBeans. When doing a set, there are two X
Hm, this is strange indeed. Maybe a parser bug? You can use XmlOptions to
change the parser that XmlBeans uses, you should try that.
Radu
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2008 7:12 AM
To: dev@
Hi,
I also tried the example today and got the same error.
(used the saxonb9-0-0-4j package)
However only jdk1.5 is available at my workstation - could the raise the
problem?
Best
Christian
JIRA [EMAIL PROTECTED] wrote:
>
> Wing Yew Poon commented on XMLBEANS-383:
> --
