Hi, thanks both for the answers. OK maybe use the POJOs in client code
will not be a good idea, but my idea was to generate POJOs on the
server side and passing to the GWT client through RPC. Do you think it
is feasible ?
On Feb 29, 9:42 am, saida dhanavath dhana@gmail.com wrote:
Hi,
As
Hello,
I'm asking you What do mean by generating POJO at server?
what I am assuming is it's not a dynamic POJO generation I mean at runtime,
If this is the your answer, Yes it is not possible to pass POJO objects
through GWT RPC mechanism, because you know, GWT RPC generates some
serialization
What you are asking for is feasible doing what Sai described but I think it
would be better for you to use ValueProxy with the @ProxyFor annotation,
that is easier than creating a POJO just for the client side and then
writing code to convert your server POJO to another client specific POJO.
Hi,
As long as you provide the required source code for the generated POJO's to
GWT compiler for generating the JavaScript it will work.
But, I think when you generate POJO's using XMLBeans, your POJO's will have
some dependency on XMLBeans (Data Binding) annotations and GWT compiler
forces you
You can also use RequestFactory ValueProxy
On Wednesday, February 29, 2012 3:42:55 AM UTC-5, Sai wrote:
Hi,
As long as you provide the required source code for the generated POJO's
to GWT compiler for generating the JavaScript it will work.
But, I think when you generate POJO's using
Hi,
I'm trying to simplify the stack of a web application (based on J2EE)
that takes an XML profile from backend convert it in a POJO (with some
XML data binding tool) and then throughout several data
transformations it becomes a view bean and then presented in
JavaScript. The idea is to simplify
