cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <>
Subject Re: Database connection by cocoon 2.2
Date Thu, 24 Jul 2008 16:30:22 GMT
On 23.07.2008 08:00, Derek Hohls wrote:

> Not sure if you are speaking for the dev team here?

No, that was my opinion.

> What exactly does "kind of  obsolete" mean - has it
> been deprecated, or is it still a valid component in 2.2?
> Or is there is some other meaning?

I'm not a native English speaker but I think "obsolete" is exactly what 
I want to express: It's still there, you are free to use it, but you 
don't need to since there are superior ways to do it like the DAO 
support provided by Spring. I did not intent any additional meaning than 
that (like deprecation).


>>>> On 2008/07/19 at 01:08, in message <>, Joerg
Heinicke <> wrote:
> I agree with Boris. In Cocoon 2.2 the database block is kind of 
> obsolete. An application should rather be developed with more standard 
> means as provided by Spring. Cocoon was never very good at integrating 
> database stuff.
> Joerg
> On 06.06.2008 10:05, Johannes Hoechstaedter wrote:
>> I know, cocoon is based on spring. But isn't there another possibility 
>> with cocoon blocks only? There is this database-block. What it is good 
>> for, when I have to write my own spring application? I want to write as 
>> less code as possible.
>> Johannes
>>> Johannes -- you may want to search for tutorials on using databases with
>>> Spring.  My understanding is that with Cocoon 2.2 it is best to have
>>> Spring configure and manage any database connections.  Then you can add
>>> Cocoon features (eg, the SQL transformer or whatever) once that is set
>>> up.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message