|
From: Andrus A. <an...@ob...> - 2004-12-24 18:15:06
|
Folks, Thanks for the vote of confidence! I replied last night to Rod and Colin, but as there were more replies on the original thread, I decided to send a message to spring-developer. What's the best way to proceed with integration? I guess the simplest thing is for one of the current committers to take my code, review and commit it to Spring.... and handle any future contributions via patches. Aside from SourceForge anonymous CVS flakiness this shouldn't be a problem. Not sure what's Spring procedure for giving commit rights to new people, but I imagine it has to be something that takes time. Re: Juergen's note about Petclinic sample app. Doesn't matter to me. It probably does make sense to keep it in Cayenne. Andrus P.S. Here is the message to Rod a Colin that I sent last night: > Re: Colin's question about PlatformTransactionManager > > I didn't find a need to write one yet. Cayenne is designed around the > idea that data objects can be sitting around in uncommitted state > between transactions, so I imagine it is much more tolerant in this > respect than others... DataSourceTransactionManager worked fine in > Petclinic example, but I would like to get feedback from Spring > developers / power users based on the code that I posted. There maybe > some pitfalls that I am unaware of that would require a specialized > PlatformTransactionManager. > > > Re: Integrating to Spring > > I will be ready to do any needed work sometime early January. As I am > not a committer anyway, I need someone to review and check in the code > (the former wouldn't hurt even if I am granted committer status). |