Re: [OSWorkflow] Proposal for a Workflow.canInitialize with Inputs arg
Edgar González <[email protected]>
| Newsgroups | gmane.comp.java.open-symphony.devel |
|---|---|
| Message-ID | <00c101c30615$4d2535f0$f0882cc8@PORT2000P01> |
Hani, I agree with you +1 ---------------------------------------------------------------------------- Edgar Gonzalez Gonzalez VALHALLA Project, s.a. Chief Technology Officer Web: www.valhallaproject.com E-mail: [email protected] Phone: +58-212-242.4379 / 6662 / 4055 / 6475 Fax: +58-212-242.6809 "The limits of my language mean the limits of my world." Ludwig Wittgenstein ---------------------------------------------------------------------------- ----- Original Message ----- From: "Hani Suleiman" <[email protected]> To: <[email protected]> Sent: Thursday, April 17, 2003 10:23 PM Subject: Re: [Opensymphony-developers] [OSWorkflow] Proposal for a Workflow.canInitialize with Inputs arg this is a pretty good idea actually, adding a generic 'canXXX' type method. That way callers can see if performing a particular action or whatever is possible without actually doing anything. canInitialize is probably a bad name for it, maybe something like hasPermission(workflowId, stepId, actionId, inputs)? On Thursday, April 17, 2003, at 09:54 PM, Pat Lightbody wrote: > This is a good point. Though not clearly stated in the docs, it has > been my > opinion that the restrict-to conditions should not depend on INPUTS, > even > though they technically could. Instead, things that depend on inputs > should > be _validators_, since they validate the input. > > Open a case on this and we can discuss it more. Hani, how do you feel > about > this? > > -Pat > > ----- Original Message ----- > From: "Edgar González" <[email protected]> > To: <[email protected]> > Sent: Wednesday, April 16, 2003 2:31 PM > Subject: [Opensymphony-developers] [OSWorkflow] Proposal for a > Workflow.canInitialize with Inputs arg > > > Hi, > > Should it exist a canInitialize public method with an Inputs argument? > > Currently exist a private canInitialize which signature includes an > Inputs > arg and it's called by the initialize method in order to check if the > workflow can be initizalized. > > But you can't check if the workflow can be initialized in the same way > by a > client class. > > So why no create a canInitialize method with the same arguments as > initilialize method? > > If the proposal is accepted I can provide the patch > > ----------------------------------------------------------------------- > ----- > Edgar Gonzalez Gonzalez > VALHALLA Project, s.a. > Chief Technology Officer > Web: www.valhallaproject.com > E-mail: [email protected] > Phone: +58-212-242.4379 / 6662 / 4055 / 6475 > Fax: +58-212-242.6809 > > "The limits of my language mean the limits of my world." > Ludwig Wittgenstein > > ----------------------------------------------------------------------- > ----- > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensymphony-developers > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensymphony-developers ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf