Hi again =)
This works in flow like this:
function example() {
dao.begin();
cocoon.sendPage("mypage");
dao.commit();
}
but it would be nice to be able to do that simple thing in sitemap..
Also that "executing actions after serializer is done" would be
usefull to do thins like "log that everything worked OK". It would be
useful in some pay per click or something services, or whatever you
want to do after you are sure document was processed without errors.
Thanks,
Joose
Joose Vettenranta kirjoitti 15.9.2005 kello 16:08:
To tell backgrounds of this:
Currently I have like this:
Action: create Collection from SQL
jx-Generator: create XML from that collection
transformer: sort result and do it HTML
serializer.
Problem is that if result is very very big, then Collection is very
very big. So solution could be like:
Action: generate SQL-query and sort it and just generate iterator
for it
JX-generator: create XML from that iterator (forEach
select="iterator.hasnext())")
transformer: xml -> html
serialize
problem is that that iterator needs to be inside transaction (begin/
commit) to work.
And of course I want to make XML to flow well, so I can't just do
blocking operation and I want to keep levels simple so that I don't
want to mix sql + xml together.. I could do that commit in jx-
generator, but then it would not just be template for data.
Maybe patch serializer to do like:
<map:serialize>
<map:act type="foo" />
</map:serilalize>
<!-- this is never executed -->
or <map:act type="foo" execute="documentStart|documentEnd" />
Thanks, Joose
Joose Vettenranta kirjoitti 15.9.2005 kello 15:41:
Hi again,
I tested this and seems like that execution of pipeline stops at
serializer,
so where to place that action to do sql:commit thing or do I have
to create CommitTransformer which just waits for endDocument?
Thanks,
Joose
Joose Vettenranta kirjoitti 15.9.2005 kello 11:25:
Hi,
is there a way to configure action to happen after XML-document
is fully passed that action?
basicly like this:
1. sql:begin
2. generator
3. transformer
4. serializer
and generator needs to be in transaction to be able to generate
XML.. so I can't place sql:commit between 2 and 3 right? how
about if I place it after serializer, is it executed when
document is fully processed?
or if I can define that execute this action after endDocument sax-
event, then I can place it after 2 and 3, but it might be little
bit unlogical, right?
Thanks, Joose
--
"Always remember that you are unique, just like everyone else!"
* http://iki.fi/joose/ * [EMAIL PROTECTED] * +358 44 561 0270 *
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
"Always remember that you are unique, just like everyone else!"
* http://iki.fi/joose/ * [EMAIL PROTECTED] * +358 44 561 0270 *
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
"Always remember that you are unique, just like everyone else!"
* http://iki.fi/joose/ * [EMAIL PROTECTED] * +358 44 561 0270 *
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
"Always remember that you are unique, just like everyone else!"
* http://iki.fi/joose/ * [EMAIL PROTECTED] * +358 44 561 0270 *
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
