Thanks Manoj! So I was wondering, is it feasable to use Spring Roo with GWT 2.0.3 (for spring roo to do the persistence bit with e.g. Hibernate?) or is it necessary to use GWT 2.1 M1?
I'm thinking of doing both Spring Roo Hibernate and db4o versions and commenting out one to test the performance of the other in turn. I hope they make a nice Spring Roo module for GWT+db4o if that would help using db4o as well. So, do I need to use GWT 2.1 to use Spring Roo? On May 21, 6:56 pm, Manoj <vkma...@gmail.com> wrote: > There are enhancements in GWT 2.0 to handle enhanced classes > especially the ones related to persistence. Please see the section > "Serializing Enhanced Classes" > ofhttp://code.google.com/webtoolkit/doc/latest/DevGuideServerCommunicat... > > As mentioned in their documentation, there still exists certain > limitations, but see if they are relevant to your application. Also > note that you need to add jpa-annotations-source.jar in gwt classpath. > You can get it from here > ->http://code.google.com/p/google-web-toolkit/issues/detail?id=1830 > > Thanks, > Manoj > > On May 21, 11:44 am, Ladislav Gazo <ladislav.g...@gmail.com> wrote: > > > And how does GWT handle associations where Hibernate (as JPA > > implementation) puts own Collection implementations? They are not > > serializable... that is the reason why Gilead exists. Can you tell me > > how is it possible to achieve it without such layer? > > > On 21. Máj, 16:00 h., Manoj <vkma...@gmail.com> wrote: > > > > I just completed an application on the following stack -> GWT, Spring > > > and EclipseLink (JPA). From my experience, if you are using GWT 2.x > > > and using annotations in your persistent classes, there is no need for > > > Gilead or Dozer. Don't get hung up digging the net as most of the > > > blogs/articles are outdated (for GWT 1.5 or 1.x) > > > > If you are developing your application as one big project, this is > > > super easy and everything just works. There is no problem transferring > > > objects from DAO layer all the way upto java script. (GWT 2.x knows > > > how to handle it). > > > But if you want to separate out your server side development you will > > > have to package those transfer objects along with source as a jar and > > > add them as gwt module(source is also required for gwt). Mine was a > > > relatively small application and hence followed the first approach. > > > But i did try out the second approach and it worked. (A simple build > > > script will do the > > > work for you) > > > > Thanks, > > > Manoj > > > > On May 21, 8:44 am, José González Gómez > > > > <jose.gonzalez.go...@gmail.com> wrote: > > > > Can't help there, as I haven't tried it yet. Anyway the Spring Roo > > > > tutorial includes generation of persistent classes using JPA and > > > > Hibernate, so I guess it will include some way to get those entities > > > > to GWT, taking into account that is integrated with it > > > > > Good luck!! > > > > > On 21 mayo, 12:57, Navigateur <naveen.c...@googlemail.com> wrote: > > > > > > Thanks José! > > > > > > Spring Roo looks brilliant! Just one issue, does any of its modules > > > > > utilise Gilead or another DTO assembler so that the Hibernate entities > > > > > can smoothly go to the GWT client-side? > > > > > > On May 20, 5:03 pm, José González Gómez > > > > > > <jose.gonzalez.go...@gmail.com> wrote: > > > > > > Although you could think they're the perfect solution for > > > > > > persistence > > > > > > in OO languages, object databases haven't taken off, so if you're > > > > > > doing anything serious I would be cautious about using them. I don't > > > > > > know of any big application in production with an OODB. Maybe we're > > > > > > too used to relational databases... > > > > > > > Take a look at Spring Roo, I think you will like it. > > > > > > > Best regards > > > > > > José > > > > > > > On 20 mayo, 17:43, Navigateur <naveen.c...@googlemail.com> wrote: > > > > > > > > Wow, thanks José and David! > > > > > > > > I'm new to "tools" so I'm a bit nervous about using them > > > > > > > (although I > > > > > > > probably shouldn't be) whereas db4o offers straightforward code > > > > > > > for > > > > > > > persisting objects. Are there any disadvantages to using db4o > > > > > > > instead > > > > > > > of ORM with tools? db4o seems intuitavely the best option for me > > > > > > > right > > > > > > > now, but could I be wrong? I thank David for bringing it to my > > > > > > > attention, it looks VERY interesting, and under active > > > > > > > development, > > > > > > > although the queries are currently reportedly slow, but when that > > > > > > > is > > > > > > > fixed, is there a reason why it shouldn't supercede RD and ORD > > > > > > > for new > > > > > > > projects? > > > > > > > > On May 20, 3:18 pm, José González Gómez > > > > > > > > <jose.gonzalez.go...@gmail.com> wrote: > > > > > > > > JPA/Hibernate supports annotations, so you don't have to fiddle > > > > > > > > with > > > > > > > > xml files any more; and JPA/Hibernate has adopted the "sane > > > > > > > > defaults" > > > > > > > > and "convention over configuration" policy, so unless you want > > > > > > > > to take > > > > > > > > control of your mappings (something you should do if you're > > > > > > > > doing > > > > > > > > anything serious) most of the times it's enough to annotate the > > > > > > > > persistent class with the @Entity annotation. > > > > > > > > > Anyway, if you're handling complex object structures, it's way > > > > > > > > more > > > > > > > > cumbersome to handle persistence by hand, instead of using a ORM > > > > > > > > framework. If you want to have automatic update of the database, > > > > > > > > Hibernate tools is able to generate the database schema from > > > > > > > > your > > > > > > > > mappings. I suggest to take a look at Maven, Maven Hibernate > > > > > > > > plugin, > > > > > > > > JBoss Tools, and Spring Roo. Haven't worked with the later, but > > > > > > > > GWT > > > > > > > > has just made a coordinated release with Spring Roo and I think > > > > > > > > it may > > > > > > > > be quite interesting for you. > > > > > > > > > I hope this isn't getting too much OT... > > > > > > > > > HTH, best regards > > > > > > > > José > > > > > > > > > On 20 mayo, 15:37, Navigateur <naveen.c...@googlemail.com> > > > > > > > > wrote: > > > > > > > > > > Thanks José! But don't they still require you to do the > > > > > > > > > "hibernate- > > > > > > > > > mapping" xml thing? Isn't this cumbersome for complex object > > > > > > > > > structures? Or is there a way of being able to play with your > > > > > > > > > object > > > > > > > > > structure without having to change the hibernate-mapping xml > > > > > > > > > every > > > > > > > > > time (i.e. a default automatic behaviour for all objects, > > > > > > > > > which also > > > > > > > > > updates the data-store to reflect object-structure changes in > > > > > > > > > the > > > > > > > > > code)? > > > > > > > > > > Thanks! > > > > > > > > > N > > > > > > > > > > On May 20, 10:08 am, José González Gómez > > > > > > > > > > <jose.gonzalez.go...@gmail.com> wrote: > > > > > > > > > > Although your question has (almost) nothing to do with > > > > > > > > > > GWT... we're > > > > > > > > > > working on a GWT + JavaEE application, and evaluated several > > > > > > > > > > alternatives regarding this problem. We had two winners, > > > > > > > > > > both of them > > > > > > > > > > using of course JPA with Hibernate provider: > > > > > > > > > > > 1. Use Gilead to transform your persistent entities and > > > > > > > > > > send them to > > > > > > > > > > GWT > > > > > > > > > > 2. Use DTOs, and use Dozer to transform from / to domain > > > > > > > > > > objects / > > > > > > > > > > entities > > > > > > > > > > > In our case we chose DTOs / Dozer over Gilead because we > > > > > > > > > > favoured > > > > > > > > > > layer separation, encapsulation and security over > > > > > > > > > > development ease. > > > > > > > > > > YMMV > > > > > > > > > > > Best regards > > > > > > > > > > José > > > > > > > > > > > On 20 mayo, 10:54, Navigateur <naveen.c...@googlemail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > Ah yes! Except that I want to be able to get persistent > > > > > > > > > > > things onto my > > > > > > > > > > > client side without too much conversion or trouble (i.e. > > > > > > > > > > > the same > > > > > > > > > > > objects client-and-server-side using the same language, > > > > > > > > > > > and the same > > > > > > > > > > > class definitions). > > > > > > > > > > > > What are my full range of options for this, anyway? > > > > > > > > > > > And which is the best one for the purposes I've mentioned? > > > > > > > > > > > > On May 20, 12:34 am, Blessed Geek <blessedg...@gmail.com> > > > > > > > > > > > wrote: > > > > > > > > > > > > > Wouldn't your initial question be like - > > > > > > > > > > > > What is the best power tool to use to build the fence > > > > > > > > > > > > around my garden > > > > > > > > > > > > if I wish to plant my garden with tulips. > > > > > > > > > > > > > But later on in your post, you reveal that your > > > > > > > > > > > > question actually has > > > > > > > > > > > > nothing to do with GWT, just as growing tulips has > > > > > > > > > > > > nothing to do with > > > > > > > > > > > > choice of power tools for your fence. > > > > > > > > > > > > > -- > > > > > > > > > > > > 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-tool...@googlegroups.com. > > > > > > > > > > > > To unsubscribe from this group, send email to > > > > > > > > > > > > google-web-toolkit+unsubscr...@googlegroups.com. > > > > > > > > > > > > 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 > > > > > > > > > > > google-web-tool...@googlegroups.com. > > > > > > > > > > > To unsubscribe from this group, send email to > > > > > > > > > > > google-web-toolkit+unsubscr...@googlegroups.com. > > > > > > > > > > > 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 > > > > > > > > > > google-web-tool...@googlegroups.com. > > > > > > > > > > To unsubscribe from this group, send email to > > > > > > > > > > google-web-toolkit+unsubscr...@googlegroups.com. > > > > > > > > > > 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 > > > > > > > > > google-web-tool...@googlegroups.com. > > > > > > > > > To unsubscribe from this group, send email to > > > > > > > > > google-web-toolkit+unsubscr...@googlegroups.com. > > > > > > > > > For more options, visit this group > > ... > > read more » -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
