Either I think you need to explain your use case even more, or there may
be another way to do it.
You said in your first post that you made "intense use readin/writing of
xml configuration files"
I assume that the files are on your server? If you are trying to set the
contents of the elements of the xml file, then why not
use an RPC mechanism that automatically binds them to POJOs on the
client? (you don't have to use GWT-RPC)
Then you could provide an editing interface in GWT and when you "save"
the file in the client the reverse process allows it to
be stored on the server.
Or am I missing something? If they are stored as XML on the server you
only need to bind/unbind them once and that should be in the RPC mechanism .
HTH
Alan
ciosbel wrote:
I need to manage xml files (already written), so i thought that
having them binded into serializable POJO's was a good choice.
But none of the technologies mentioned seemed to work in that way.
For example with JAXB you can autogenerate java classes from xsd
schema, having them serializable and usable through gwt rpc service.
But it doesn't work bacause of reflection. Xstream and XMLBeans is
the same.
Am i missing something?
On 13 Mag, 23:51, Mike <[email protected]> wrote:
Why do you need XML, and not just POJO ?
--
You received this message because you are subscribed to the Google Groups "Google
Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group
athttp://groups.google.com/group/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups "Google
Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
