I am using SQL Transformer for my queries - works well;
for more complex issues, SQL statements can issued from
within flow ... not sure what you mean by "messy"?  
Personally, when I look back on my old XSP code, I find
that to be very messy, with a horrible mix of XML and Java
and custom-code.

>>> On 2008/02/20 at 02:02, in message <[EMAIL PROTECTED]>, Kamal Bhatt <[EMAIL 
>>> PROTECTED]> wrote:
Andrew Savory wrote:
> Hi,
>
> On 20/02/2008, *Reinhard Poetz* <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>     kamal wrote:
>     > Hi,
>     > I have finally got around to looking at Cocoon2.2 and I am having
>     > problems understanding a couple of things:
>     >
>     > 1. What happened to XSPs? We extensively use XSPs at work and would
>     > require either a XSPs or a valid replacement.
>
>     XSP hasn't been migrated to 2.2 yet. The replacement is Cocoon
>     Template.
>
>
> In more detail: XSP has been deprecated for some time, since it often 
> resulted in a mixture of concerns (extensive logic, presentation and 
> content all in one file). A more robust alternative is to use java 
> objects + flowscript + template (jxtemplate using jxpath or jexl).
What about SQL queries? Last time I checked in 2.1, doing SQL queries 
were messy in JXTemplates, flowscript, etc...


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED] 



-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail 
legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at 
http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their 
support.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to