I said that I was talking about the context of standard business applications. IBatis is certainly very useful in highly technical. But in a functional context, iBatis does not object-oriented programming.
On 13 jan, 15:26, Matt Moriarity <[email protected]> wrote: > Ok that is simply not true. There are cases where Hibernate may be the > right choice but there also plenty of times where something else would > be better. Hibernate is not the only ORM solution for Java. I, for > instance, tend to use iBATIS. It's helpful to have control over the > SQL that is being used. > > On Jan 13, 3:15 am, philippe <[email protected]> wrote: > > > > > To make corporate application Hibernate is mandatory. Without > > Hibernate, you can not keep a good level of scalability while > > maintaining a satisfactory consistency in your application. The more > > you go up in functional complexity, the less you can maintain your > > application. > > > Gilead is a very good API. I use it in my projects. But I only use T > > PersistentBeanManager.clone(T) fonctionnality. I don't link to > > increase the dependence between Gilead and GWT. Therefore I do not > > gilead4gwt. I just prefer to use only The PersistenceBeanManager. > > > On 12 jan, 23:34, "[email protected]" <[email protected]> wrote: > > > > I never understand how to use hibernate. It seems so complex and doing > > > normal mysql commands seems a whole lot eaiser. > > > > On Jan 12, 12:19 pm, noon <[email protected]> wrote: > > > > > Oups, I forgot to post the project URL :http://gilead.sourceforge.net > > > > > Regards > > > > Bruno > > > > > On 12 jan, 21:09, noon <[email protected]> wrote: > > > > > > Hello, > > > > > > I am pleased to announce the new release of Gilead, an Open-Source > > > > > framework for seamless intregration of Hibernate and GWT. > > > > > > This new release brings new features, such as > > > > > - Predefined remote services, for both GWT : > > > > > * The Loading service allows you to load an entity or a lazy > > > > > association from the GWT side, > > > > > * The Request service brings the ability to execute a HQL > > > > > request directly from the GWT side, > > > > > - A new specific transport annotation (@LimitedAccess) to > > > > > implement custom access to entity fields (role based for example) > > > > > - Lazy property checking on GWT side, to know if a null > > > > > association on client side was already null on server or just lazy but > > > > > not loaded (and thus replaced with null by Gilead) > > > > > - A ConfigurationHelper class, to limit Gilead configuration to > > > > > one line of code > > > > > > A specific effort has also been made to improve performances and GWT > > > > > serialization. > > > > > > Finally, this release also fixes many issues, reported since 1.2.3, > > > > > especially on persistent collections. > > > > > > Hope this helps ! > > > > > Bruno
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
