> From: John Austin [mailto:[EMAIL PROTECTED]] > > I posted a question on cocoon-users a while ago asking for help with > this Action class and took the source code upstairs with me to watch the > end of the NHL playoff game (Trawna lost in overtime - hooray!). > > As I have now read the code in some depth, I would like to ask whether > anyone has actually used this class for anything other than providing > workload for the compile engines. > > I am reasonably certain that DatabaseSelectAction isn't useful as it is > in 2.0.1 (looks the same in 2.0.3) and would like to know whether > anyone on cocoon-devel feels the class should be worked on. > > I would like to use it for simple table lookups which load parameters > into the sitemap. The user-case I have in mind is where you look up a > single row of a user profiles table and pass the user's preferences to > various elements of the pipeline. These could be passed to > transformations as parameters or used to construct file or path names. > > The class is very short right now but it appears to have some > questionable structure. I suspect it is a work-in-progress so please > don't recieve my criticism negatively. At the very least, I would like > to add some comments to the code and thereby to the JavaDoc.
This class is supposed to select single row from a column identified by the primary key values and populates with these values (or request parameter's values - if present) request attributes. It could be used with form validation action: if validation fails, present form to the user and populate it from request attributes and database. IIRC, it was doing this ok. As Christian pointed out, Database*Actions are not maintained well anymore, but if you want to put some comments in - you are welcome. Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
