cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Kavanagh <>
Subject Re: passing out params
Date Thu, 22 May 2003 20:15:59 GMT
My issue is that some people who have influence of the architecture want 
less intelligence in the stored procedures and more in the java (or 
cocoon) layer. Therefore, I get to call a series of dumb procedures.. 
yeah :-/


Luca Morandini wrote:

> David Kavanagh wrote:
>> I was afraid of that. I'd like to issues a bunch of statements as 
>> part of a transaction, so I can rollback if something fails. That 
>> isn't possible when I used multiple SQLTransformer instances in a 
>> pipeline. Another thing is that I wanted to have one .xsl file that 
>> generates the list of statements to be executed in the transaction. 
>> That way, I can read the whole transaction very easily. Much nicer to 
>> code/debug this way. It gets kind of un-wieldy when I have to split 
>> things up to much. I've been avoiding it, but I think I'll just have 
>> to write my own action to implement the JDBC calls. sigh.
> Well, my standard approach when it comes to transactions is the use of 
> Stored Procedures... or triggers maybe.
> If you need to call some SPs in sequence, better to put these calls 
> inside another SP and call the latter from you pipeline.
> Regards,
> ------------------------------------------
>                Luca Morandini
>                GIS Consultant
> ------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message