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 > > 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 at http://groups.google.com/group/google-web-toolkit?hl=en.
