Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Cocoon database access strategy
Date: Mon, 25 Jun 2007 12:07:02 +0200
Message-ID: <A955EA1F8FE31749AEC8C998082F6C7CD6E9FC@hai01.hippo.local>
Thread-Topic: Cocoon database access strategy
Thread-Index: Ace1eNsjSvedIIJ2Rp+2oBpSK+W2AwBlfxwA
From: "Ard Schrijvers" <a.schrijvers@hippo.nl>
To: <users@cocoon.apache.org>

Hello,

>This leads to start writing=20
> code before=20
> > the problem is fully understood and a reluctance to=20
> refactor once it=20
> > is. These are the very tendencies that Cocoon allows us to overcome=20
> > because it is entirely possible to develop fully fledged=20
> applications=20
> > without writing any Java code. These 'pure' XML applications are=20
> > likely to be much more maintainable, flexible and capable of re-use=20
> > than those that skew their centre of gravity back towards Java.

I can hardly believe everybody seems to take this statement for granted =
(jdo and jcr APIs are ofcourse totally redundant since you can write =
your own fine sql statements, and of course, sql is a brilliant strong =
specification, so when you have it running for oracle, you can switch =
automatically without effort  to mysql, derby, hsqldb, sql =
server)...anyway, if everybody wants to write sql, do many xsl =
transformations and take the burden of maintaining sql statements, be my =
guest :-)


Regards Ard


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org