Tony
Thanks for helping to clarify; perhaps what is then missing
from the docs is, for us oldies with bad habits, a guide
to Migrating apps from XSP to
For example; you say the approach to replacing ESQL in
XSP would be:
JXT Generator - SQLTransformer - Whatever
BUT; in my XSP, the SQL
Um, at the risk of being labelled a compromiser, I think
both posts here are saying essentially the same thing -
keep it simple and direct for folks starting out, but provide
the links/hooks [carefully labelled, of course!] for those
who want/need/can handle more detail. The only minor
argument
JD
This was *exactly* my post to the mailing list a few days
back - I have previously used XSP to do all the DB stuff
(in my case, it was all there was a while back) - and now
that JXT is available, I would like to refactor or just
move forward with the new (recommended?) approach.
However, it
Le 5 mai 04, à 08:16, Derek Hohls a écrit :
...The concept seems simple enough - but are we actually able
to do it??
Did you look at the new supersonic block already?
It's supposed to give a good overview of Cocoon to beginners (but
requires Cocoon to be installed as many things are dynamic).
I fully agree that the needs of users are seldom the same. So if we're
talking an experienced user I'd say a bunch of examples on all possible
ways is ok.
But this topic, as I understand it, is focussed on starting users. So I
think that it's not so much important how many examples and ways are
]
Subject: Re: Vote: to unify, or not to unify - results
let me put here my two cents
for select queries xsp/esql is great and the perfect _in_most_cases_
way
in most cases we create pipelines that make select queries and return
the
content in xml format. then we call this pipelines in most
Bruno
Then the question - if XSP is NOT a preferred generator;
and JXT is a fake generator - what exactlly are we supposed
to be using for simple generation use cases; or are we saying
all users have to be full-on Java programmers and create
custom generators each time they want to do something
be recommended
to
everyone?
Ralph
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 2:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Vote: to unify, or not to unify - results
let me put here my two cents
for select queries xsp
I was hoping it would be in Version 2.1.5, which I was
planning to download next week
Does it also address the issue of documentation?
[EMAIL PROTECTED] 2004/05/05 08:42:45 AM
Le 5 mai 04, à 08:16, Derek Hohls a écrit :
...The concept seems simple enough - but are we actually able
to
On Wed, 5 May 2004, Derek Hohls wrote:
Bruno
Then the question - if XSP is NOT a preferred generator;
and JXT is a fake generator - what exactlly are we supposed
to be using for simple generation use cases; or are we saying
all users have to be full-on Java programmers and create
custom
), or that you feel it
is
the
best way to perform an SQL query and that it should be
recommended
to
everyone?
Ralph
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 2:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Vote: to unify
Le 5 mai 04, à 09:01, Derek Hohls a écrit :
I was hoping it would be in Version 2.1.5, which I was
planning to download next week
The supersonic tour block will be included in the release, as an
unstable block.
Does it also address the issue of documentation?
The supersonic tour is both
On Wed, 2004-05-05 at 08:48, Derek Hohls wrote:
Bruno
Then the question - if XSP is NOT a preferred generator;
and JXT is a fake generator - what exactlly are we supposed
to be using for simple generation use cases; or are we saying
all users have to be full-on Java programmers and create
Bruno
Thanks, that is *very* clear now; I think one could make
a very good case for simplifying the naming here to be:
JXGenerator
and
JXTransformer
(and/or, in future, JXTemplate? if we create a stripped
down version, with no logic options...)
Would that not help avoid confusion??
it is
the
best way to perform an SQL query and that it should be recommended
to
everyone?
Ralph
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 2:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Vote: to unify, or not to unify - results
Well,
I most certainly would be glad if i got my hands on some nice tutorials... I
consider myself an interested and fast learner, but you guys come up with
something newer (and better?) every week. I would come in handy if there
was some drilldown list grouped on similar techniques/purpose or
Derek Hohls wrote:
Stavros
My point here was not so much getting the PHP
people into the SoC approach [XML+XSL=HTML] but
more the confusion that arises when you reply to
a series of questions [over some period of time] -
Oh, you want to read from a database - just learn XSP
It is said that
JD Daniels wrote:
Derek:
Short answer: I'm Hiding from it. heh heh. I have a project now that
is a month overdue because I tried to jump on the woody -- Cforms
bandwagon. I am just not Java literate enough. I came from php... it
is the separation of content and logic that made me move to
Thank you for your input! Some excellent comments have been made and all are
noted.
So far, the poll results show that there is no unanimity (see below). I
think that it would be pretty unscientific to reach any firm conclusions
based on such a small sample, but I think that some trends can be
Other than the CPA, we would show other options. For example, if a newbie
were reading up on JXTemplates, rather than saying that you can use Jexl or
JXPath, we would choose our CPA (for example, JXPath), but have a link to a
homologous page that explains the same things, but for Jexl. This would
:[EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 9:17 AM
To: [EMAIL PROTECTED]
Subject: RE: Vote: to unify, or not to unify - results
Generally, based on your comments, it appears that a good approach may be to
choose a currently preferred approach. This recognises that what is often
called best
David Leangen dijo:
***
[ ] A. I think that we should show users the best way
to get up and running with Cocoon.
[ X ] B. I think that we should show users all the options
possible and let them decide the best
Le 4 mai 04, à 18:39, Nacho Jimenez a écrit :
... The average user does not give a shiling about JXTemplates,
JXPath, JEXL or whatever load of letters we decide to acronymize
today.
The user wants to know how can he set up his ubercool website
accessing XML documents and SQL data with the
Nacho Jimenez wrote:
Other than the CPA, we would show other options. For example, if a
newbie
were reading up on JXTemplates, rather than saying that you can use
Jexl or
JXPath, we would choose our CPA (for example, JXPath), but have a
link to a
homologous page that explains the same things,
Bertrand Delacretaz wrote:
Le 4 mai 04, à 18:39, Nacho Jimenez a écrit :
... The average user does not give a shiling about JXTemplates,
JXPath, JEXL or whatever load of letters we decide to acronymize today.
The user wants to know how can he set up his ubercool website
accessing XML
On Tue, 2004-05-04 at 18:39, Nacho Jimenez wrote:
Other than the CPA, we would show other options. For example, if a newbie
were reading up on JXTemplates, rather than saying that you can use Jexl or
JXPath, we would choose our CPA (for example, JXPath), but have a link to a
homologous page
On Tue, 4 May 2004, JD Daniels wrote:
Nacho Jimenez wrote:
Other than the CPA, we would show other options. For example, if a
newbie
were reading up on JXTemplates, rather than saying that you can use
Jexl or
JXPath, we would choose our CPA (for example, JXPath), but have a
:[EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 2:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Vote: to unify, or not to unify - results
let me put here my two cents
for select queries xsp/esql is great and the perfect _in_most_cases_ way
in most cases we create pipelines that make select queries
PM
To: [EMAIL PROTECTED]
Subject: Re: Vote: to unify, or not to unify - results
let me put here my two cents
for select queries xsp/esql is great and the perfect _in_most_cases_ way
in most cases we create pipelines that make select queries and return the
content in xml format. then we
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 2:40 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Vote: to unify, or not to unify - results
i recommend the use of xsp/esql --- xml
when the needs are select only queries
it very simple/clean and cover the needs in most
30 matches
Mail list logo
