11/6/2007, you wrote:
Yes I know but, can I convert a simple java class A to a XmlObject without
schema ?
Albert Bupp wrote:
>
> He means the XmlObject class which you'll find in the XmlBeans library.
>
> -Albert
>
> At 10:27 AM 11/6/2007, you wrote:
>
>>That sounds
He means the XmlObject class which you'll find in the XmlBeans library.
-Albert
At 10:27 AM 11/6/2007, you wrote:
That sounds good but, I don´t have a XmlObject, I have a simple pojo (class
A) and i want to convert it to XmlObject, my class A have to implements
XmlObject ? How can I do this ?
hank you for your tips, I think I have to come up with the way to map my
DOM tree to Relational tables first, using XMLBeans or writting the code
myself does not make much of differences to me about solving the mapping
problem, my problem is the way of mapping the DTD element or DOM tree into
RDBMS.
If I may jump in, I think what Gustavo means is you could use the
scomp utility included in the XMLBeans package to generate Java
classes representing the XML data that you want to populate your
RDBMS. This utility generates and compiles (and jars) a set of Java
class files which correspond to
stead of the setter.
So -
for
you can set it by
XmlBoolean xb = XmlBoolean.Factory.newInstance();
xb.setStringValue("1");
d.xsetDayWorking(xb);
------
From: Albert Bupp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 12:08 PM
To: user@xmlb
a bug. "true" and "1" are both
valid values for the schema type. When XMLBeans
writes the xml, it uses the canonical lexical representation, which is "true".
--
From: Albert Bupp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 8:46 AM
To: user@x
I recently had a similar problem. A schema defines an element thusly:
When calling the generated interface:
d.setDayWorking(true);
XMLBeans then writes:
true
However, the application reading the XML instance
(which is out of my control) needs it to be:
1
My work-around was to revise the
7 matches
Mail list logo
