On 9/13/06, Dev at weitling [EMAIL PROTECTED] wrote:
...Why does Cocoon provide not less than three different ways of handling
SQL queries?...
History, and the desire to stay compatible with existing applications,
There's even a fourth way, using JDBI/flowscript as shown in the Easy
SQL
All of this begs the question, what is the best way?
Bertrand Delacretaz wrote:
On 9/13/06, Dev at weitling [EMAIL PROTECTED] wrote:
...Why does Cocoon provide not less than three different ways of
handling
SQL queries?...
History, and the desire to stay compatible with existing
Florian
My 2c of understanding (as a user NOT a developer) -
But why not a schema/namespace/tag soup usable in XSP
I think you will find that, unless you're maintaining historical apps,
that there is simply no need to use XSP any more. There has been
a lot of discussion about this on the
On 9/14/06, Kamal Bhatt [EMAIL PROTECTED] wrote:
All of this begs the question, what is the best way?...
Depends on your skill set and goals.
If you don't want to program, the easiest might be the
SQLTranformer, though there might be some cases (I'm not sure about
that, hopefully someone can
If you don't want to program, the easiest might be the
SQLTranformer, though there might be some cases (I'm not sure about
that, hopefully someone can comment) where the ESQL stuff is more
flexible.
Is it possible to use ESQL without embedding in XSP 'cause XSP should
not be used anymore
The javascript worked fine for my skillset and project size
(medium complexity; longer-lived project) - it avoids having
to learn Hibernate and/or Spring (big jump IMO) or Java -
and leverages a syntax you are already likely to know
(Javascript).
Bertrand Delacretaz [EMAIL PROTECTED] 2006/09/14
On 9/14/06, Dev at weitling [EMAIL PROTECTED] wrote:
...Is it possible to use ESQL without embedding in XSP 'cause
XSP should not be used anymore (why?)...
XSP still works as well as ever, but most people don't use it anymore
for new projects, preferring to use java and/or flowscript.
There
