Hi Derek,
Derek Hohls wrote:
Olivier
I still disagree - the SQLtransfomer is a much better alternative than XSP-ESQL for simple cases; its possible that there are very complex cases that may not be handled but, even then, the JXTemplateGenerator will give you a lot of additional flexbility to solving such problems.
I just began using the JXTemplateGenerator, and I don't see all features from Java, that let you dynamically generate a query from this sort of data : avalon components, LDAP, and so on...
I agree session and request infos are accessible from JX, but it's limitating for me. But again, I may miss something.
PS I say this as someone who has used XSP-ESQL extensively in the past and am now trying to "convert"
myself, as well!
I agree that in cases other than simple lists display, XSP and ESQL can easily be substituate by avalon data-components and flowscript (that's what I'm doing), and separates the business part and the presentation part, but a feature as flexible and powerfull as XSP-ESQL for simple result lists is in my humble opinion missing for the moment.
PPS From code Matt has sent me, I think this is more an XSLT problem, than a Cocoon problem.
I think so : maybe a namespace problem.
But the way of thinking is a little bit tricky : using a list of requests as a source of a pipe and transforming it form generating the "good" request is very stange.
I would prefer using an other way to get the good request (avalon + input-module for example) feeding the source of the pipeline. Maybe JXTemplate can use input-modules ? Or access the info via an input-module and pass it as a sitemap parameter seems better for me.
-- Olivier
[EMAIL PROTECTED] 2004/07/22 03:33:35 PM >>>
Hi Derek,
For most purposes, XSP is not the right way to go, I agree. I personnaly switched to flow/java and I'm very happy.
But if you look at the dev-list, you will see that currently, there is
no best alternative than XSP-ESQL to display simple result-lists like Matt seem to want to do :
- dynamically generate a query
- display a table of results
But I may be wrong on its intentions.
-- Olivier
Derek Hohls wrote:
Sorry, I disagree - XSP is pretty much deprecated and certainly not necessary in this case...
Derek
[EMAIL PROTECTED] 2004/07/22 03:02:43 PM >>>
Hi Matt,
Using XSP and the ESQL taglib is way simpler for your example.
see http://cocoon.apache.org/2.1/userdocs/xsp/esql.html
Matt Rich wrote:
Hello!
I'm currently trying to display sql request results in dropdown
menus
.
I think i must have three Transformers in my pipeline:
- I generate the requests from an XMl file through an XSL
Transformer
- Then I try to execute the generated requests through an SQL
Transformer
- Then I must rearrange the results ' presentation with another
XSL
Transformer
Is that correct ?
(As for now, the problem must be I don't manage to generate the
<sql:
...> tags so that they can be read by the transformer :
I' ve tried this way :
<xsl:element name="sql:execute-query">
<xsl:attribute name="xmlns:sql" namespace="http://apache.org/cocoon/SQL/2.0"/>)
Has anybody an idea?
Many thanks in advance!!!
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
