ypomonh pisze:
Grzegorz thank you very much for your helpful reply!
No problem.
Last week I had the opportunity to get a hold of the book "Cocoon
Developer's Guide", where in Ch. 16 "Cocoon Interfaces: Databases", pg.
355 says:
"Because actions can influence pipeline operation, by both what they
return and
whether they return anything, they can be useful when th eresult of a
database
operation can result in different pipeline processing."
"A googd rule for database actions i sto use them either........, or
when the result
of the database operations somehow will influence the pipeline."
I understand that this book was written before flows took of but is this
approach still advisable?
I guess - no. Actions were good solution at the time of inventing them. There was no scripted flow, ORM tools were not so popular. Today,
ORM tools are de-facto standard technique for DB access so Cocoon is not different here anyhow.
Since actions are no longer developed they do not follow latest trends and have
several limitations. I strongly advise to not you them.
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
