Menu
▾
▴
springframework-developer
|
From: <sk...@fe...> - 2004-06-14 13:30:33
|
I'd vote for Toplink support first. I know it's not open source but a lot of us have to use it and I am pretty sure there are several Toplink users on the list, each of us rolling our own Spring integration. Sean Kroah FedEx Ground (412) 859-5130 sk...@fe... |---------+-----------------------------------------------------> | | "Rod Johnson" | | | <rod...@in...> | | | Sent by: | | | spr...@li...| | | ceforge.net | | | | | | | | | 06/13/2004 08:37 AM | | | Please respond to | | | springframework-developer | | | | |---------+-----------------------------------------------------> >----------------------------------------------------------------------------------------------| | | | To: <spr...@li...> | | cc: | | Subject: Re: [Springframework-developer] Cayenne ORM Support | >----------------------------------------------------------------------------------------------| Tim I would like Spring to have Cayenne support, to go with our Hibernate, JDBC and JDO support. I haven't used it, but I have heard good things about it. We have a well-established template for supporting ORM solutions, demonstrated in our JDO and Hibernate support: - templates and interceptors that handle resource open/close - integration with Spring transaction management - support for JDBC operations in the same transaction if possible (it is with Hibernate and most JDO implementations) - translation from ORM-specific exceptions (like HibernateException) to our own DataAccessException hierarchy As no one in the core Spring team is a Cayenne expert (AFAIK) we hope that the Cayenne team could work within this consistent architectural approach to lead the necessary implementation, and donate the code (and support the integration). We would of course be very happy to help them with this. Rgds Rod ----- Original Message ----- From: "Tim Nolan" <kat...@ho...> To: <spr...@li...> Sent: Sunday, June 13, 2004 11:39 AM Subject: [Springframework-developer] Cayenne ORM Support > Anyone looking at adding support for this Cayenne ORM? Anyone used it on > a project? It seems to have a bit of a following. > > For product, see: > http://www.objectstyle.org/cayenne/ > > For brief comment on Spring support see: > http://objectstyle.org/cayenne/lists/cayenne-user/2004/06/0028.html > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the new InstallShield X. > From Windows to Linux, servers to mobile, InstallShield X is the > one installation-authoring solution that does it all. Learn more and > evaluate today! http://www.installshield.com/Dev2Dev/0504 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Dmitriy K. <dko...@ru...> - 2004-06-14 13:34:58
|
If I remember correctly, a TopLink support has been discussed a while ago. Dmitriy. sk...@fe... wrote: > I'd vote for Toplink support first. I know it's not open source but a lot > of us have to use it and I am pretty sure there are several Toplink users > on the list, each of us rolling our own Spring integration. > > > Sean Kroah > FedEx Ground > (412) 859-5130 > > sk...@fe... > > > > |---------+-----------------------------------------------------> > | | "Rod Johnson" | > | | <rod...@in...> | > | | Sent by: | > | | spr...@li...| > | | ceforge.net | > | | | > | | | > | | 06/13/2004 08:37 AM | > | | Please respond to | > | | springframework-developer | > | | | > |---------+-----------------------------------------------------> > >----------------------------------------------------------------------------------------------| > | | > | To: <spr...@li...> | > | cc: | > | Subject: Re: [Springframework-developer] Cayenne ORM Support | > >----------------------------------------------------------------------------------------------| > > > > > Tim > > I would like Spring to have Cayenne support, to go with our Hibernate, JDBC > and JDO support. I haven't used it, but I have heard good things about it. > > We have a well-established template for supporting ORM solutions, > demonstrated in our JDO and Hibernate support: > > - templates and interceptors that handle resource open/close > - integration with Spring transaction management > - support for JDBC operations in the same transaction if possible (it is > with Hibernate and most JDO implementations) > - translation from ORM-specific exceptions (like HibernateException) to our > own DataAccessException hierarchy > > As no one in the core Spring team is a Cayenne expert (AFAIK) we hope that > the Cayenne team could work within this consistent architectural approach > to > lead the necessary implementation, and donate the code (and support the > integration). We would of course be very happy to help them with this. > > Rgds > Rod > > ----- Original Message ----- > From: "Tim Nolan" <kat...@ho...> > To: <spr...@li...> > Sent: Sunday, June 13, 2004 11:39 AM > Subject: [Springframework-developer] Cayenne ORM Support > > > >>Anyone looking at adding support for this Cayenne ORM? Anyone used it on >>a project? It seems to have a bit of a following. >> >>For product, see: >>http://www.objectstyle.org/cayenne/ >> >>For brief comment on Spring support see: >>http://objectstyle.org/cayenne/lists/cayenne-user/2004/06/0028.html >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by the new InstallShield X. >>From Windows to Linux, servers to mobile, InstallShield X is the >>one installation-authoring solution that does it all. Learn more and >>evaluate today! http://www.installshield.com/Dev2Dev/0504 >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the new InstallShield X. > From Windows to Linux, servers to mobile, InstallShield X is the > one installation-authoring solution that does it all. Learn more and > evaluate today! http://www.installshield.com/Dev2Dev/0504 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the new InstallShield X. > From Windows to Linux, servers to mobile, InstallShield X is the > one installation-authoring solution that does it all. Learn more and > evaluate today! http://www.installshield.com/Dev2Dev/0504 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Rod J. <rod...@in...> - 2004-06-15 06:26:14
|
Sean > > I'd vote for Toplink support first. I know it's not open source but a lot > > of us have to use it and I am pretty sure there are several Toplink users > > on the list, each of us rolling our own Spring integration. I don't think it's either/or. Ideally we'd like the development for either of these to be done outside the core Spring team--with our support of course. Especially as Juergen and I (mainly Juergen!) are currently putting a lot of effort into improving our JDO integration, which is already part of Spring. TopLink support would be good to have, and the topic has come up a few times, mainly in forums. I think someone once volunteered to contribute some code, but it didn't happen. Good TopLink integration is also non-trivial, because of the need to register objects selectively with the unit of work (via cloning) to minimize the cost of dirty checking. This makes the issues a bit different to those with Hibernate or JDO, for example. I know TopLink pretty well myself, but I don't have the time to actually do the integration, as it isn't currently a priority for a client. (It came close to being a priority for me last year.) I'd certainly be happy to advise anyone who wanted to work on it in Spring's data access architecture, and the issues I see in TopLink integration: getting it right is an interesting challenge. I tried to interest the TopLink team in Spring integration a few weeks ago--after an encouraging suggestion from someone at Oracle--but so far haven't had a response. We certainly don't have any objection to integrating with a product just because it's not open source. If it's a proven product and people want to use it, we're in favour of integrating with it... I'd be interested to hear about what solutions Spring/TopLink users are using now. R |
