I'm using GWT for UI with a Grails backend. It's clumsy to use JSON
or DTO for remoting domain objects. Is there any plan for GWT to
handle Groovy domain objects ( possibly create javascript from
bytecode vs groovy source ) ?
Thanks,
Don Ruby
--
You received this message because you are
I think the GWT - Hibernate impedance problem is solved nicely with
Gilead (http://gilead.sourceforge.net) but I would like to use Grails/
GORM instead of using Hibernate/JPA directly. The problem is Grails/
GORM domain objects are Groovy source, which neither GWT nor Gilead
currently support.
Have you guys checked the http://github.com/chirino/resty-gwt project?
It has a generator
that does pretty much all the awful things Roger talks about.
On 1/28/10 9:14 AM, Abdullah Shaikh wrote:
Hi Roger,
Then the only option left is xml, of course if we are not going
GWT-RPC way.
So what
Hey Johan, thanks for the link, I will check it out.
On Thu, Jan 28, 2010 at 3:23 PM, Johan Rydberg johan.rydb...@edgeware.tvwrote:
Have you guys checked the http://github.com/chirino/resty-gwt project? It
has a generator
that does pretty much all the awful things Roger talks about.
On
Ooo.. will definitely check this out.
I'd gone to using semi-generic JavaScriptObjects on the client side, and
closely matching server side objects.. and then had Spring 3.0 w/ Jackson
handle the server side marshalling in 2 directions.
Thanks Johan
Roger
On Jan 28, 2010, at 4:53 AM, Johan
Dear Abdallah,
if your server side is java, for sure will be Servlet. why you don't try to
used Asynchronous HTTP Requests technique instead of JSON or XML. I guess
the below link helpful for you :)
http://www.gwtapps.com/doc/html/com.google.gwt.http.client.html
I hope that helpful for you .
Just checked this out.. it still has I guess the one sort-of problem.
If you have a complex client side object.. that you have to marshall into
JSON.. it is a pain point.
But hey, that is what coding is about :)
The reason I use a JavaScriptObject (btw, for me, it is a very large tree
And to add one thing.
Using JSON w/ GWT is well.. awful.
The main reason for this, is that you get JSON back to the client, and either
use Overlay Types (can't use instanceof with there, and about 500 other
issues).. or you hve to take a simple OverlayType and then re-instantiate all
of your
I read that GWT 2.0 supports serializing enhanced objects from JDO or
JPA. So if they are hibernate objects, wouldn't the JPA support cover
that?
On Jan 27, 1:30 am, Jan Ehrhardt jan.ehrha...@googlemail.com wrote:
The problem is the GWT RPC's serialization, which can't work with objects
created
Wow, I didn't recognize this feature. It's great, but it would only work, if
Hibernate is used as a JPA provider.
More on this:
http://code.google.com/intl/de/webtoolkit/doc/latest/DevGuideServerCommunication.html#DevGuideSerializableTypes
Look at the 'Serializing Enhanced Classes' section.
Oh I forgot to say, that Grails support JPA through the GORM-JPA Plugin
http://www.grails.org/plugin/gorm-jpa.
Regards
Jan Ehrhardt
On Thu, Jan 28, 2010 at 7:51 AM, Jan Ehrhardt
jan.ehrha...@googlemail.comwrote:
Wow, I didn't recognize this feature. It's great, but it would only work,
if
GWT is the obvious choice for UI. But if you want to use Grails/Groovy
for server side, you have to either code messy DTOs or client side
POJOs. It would be nice if GWT would support using the Grails/Groovy
domain objects directly on the client. Any chance of that happening?
--
You received
The problem is the GWT RPC's serialization, which can't work with objects
created by hibernate. You can use the DTO Grails plugin (
http://www.grails.org/plugin/dto) or you can use JSON / REST for
communication.
In the case of a Grails app, which comes with great support for REST / JSON,
I would
13 matches
Mail list logo
