Friday, May 14, 2010

Re: XML binding/mapping and GWT-RPC

Server-side translation and sending through serialized classes is a
fine way to go. I do it using xmlbeans, but then do a trivial
conversion to some POJO classes that are much simpler and more compact
for use on the client side, and of course work through RPC. I didn't
actually try seeing if the results of xmlbeans were GWT-serializable,
they were in any case not well suited for my client side needs, and
also allowed me deal with references as I required rather than trying
to make the xmlbeans classes work. If the xml schema(s) you're using
aren't too big and don't change much, this is an attractive option.

jk

On May 14, 11:18 am, ciosbel <andrew...@gmail.com> wrote:
> > 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)
>
> > 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 .
>
> This is exactly what i want to do. But i can't figured it out how.
> Binding into POJOs at server-side (XMLs are huge) and having them
> available at client side through serialization, is wrong? Possible?
> Useless?
>
> Thank you,
> ciosbel.
>

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate