Re: [Springframework-developer] JDOTemplate and in-memory queries

[Colin S. <col...@ex...>]

Marc,

Sorry for the _extreme_ delay in this reply. I was busy at the time you 
initially posted, put it aside for a day or two to have time to think 
about it properly and reply, and then got even busier.

The main reason the Kodo stuff is not in CVS right now is that to build 
it it does require linking to the Kodo lib, and the latter is not free. 
I don't see much of a solution for this unless Solarmetric perhaps does 
something like allow us to put a non-working Kodo lib in CVS against 
which we can build, but which we don't distribute. alternately they 
could maintain it themselves, and we could link to it. However, that's 
actually a tiny class, so I don't necessarilly even see that big a deal 
with just listing the class in docs, and pointing to somewhere where 
it's avaialble for download too.

I agree also about the need for JDO docs. I may be able to help some 
here in the shorter term, although my first priority for docs is the 
Annotations stuff, and I need to spend most of my free Spring dev time 
on trying to help with the build/source organization refactoring we've 
been talking about for a while now and are probably going to go ahead 
with. At a minimum I should be able to proof and comment on anything you 
put out.

Colin


Marc Logemann wrote:

> Juergen Hoeller wrote:
>
>> FYI, I'm about to leave for Denmark, returning on Wednesday - which 
>> means
>> I'm not available for kicking this off till mix next week. Feel free to
>> create JIRA issues and/or gather stuff on the wiki in the meantime :-)
>
>
> Colin, perhaps we can discuss that, because i want to start with the 
> first section called "Resource Definitions in an Application Context"
>
> But we should agree on one approach in doing this. In my application i 
> am doing it the same way as you ve done it for the wiki with Kodo. Is 
> it possible to generalize this KodoPersistenceManagerFactoryBean (just 
> different naming?) and place it in the Spring tree, this way we would 
> have the same approach as with Hibernate. We would have a seperate 
> Datasource definition and the linking to the JDO resource via 
> "connectionFactory".
>
> I could also start with some general blabla in a section called 
> "Resource Management". Also the same as with Hibernate spring docs.
>
> Perhaps other might want to continue with sections like:
>
> - Inversion of Control: Template and Callback
> - Transactions
>
> Just a proposal. Happy to hear more on this from Rob or Colin. Hope 
> its ok to just proceed with the documentation issue. I dont want too 
> many users switching to hibernate just because Spring has no JDO docs 
> <g>.
>