On Wed, 16 Mar 2005 14:27:02 -0600, Michael Rasmussen <[EMAIL PROTECTED]> wrote: > This may have been proposed long ago I don't know, but I will throw it > out there as it just popped into my head. > > I agree with those of you who are against POJO's, but I had a thought: > > Since Action is used mostly to populate a VO from the Form Bean and > then delegate to some business logic facade (at least that is how I > usually do things) why not create an action that takes a modified > version of a dyna form. The dyna form instead of "configuring" itself > from the struts-config, configures itself from a VO (I admit I have > not looked at the code for the magic dynaform so I don't know how it > is implemented). So, a dynaform takes a POJO classname (or instance, > I haven't decided which would be better) and builds itself by > reflecting over the getters/setters on this object. Then the Action > just delegates to the facade with the VO it was given. > > If this doesn't make sense, let me know and I will elaborate.
I understand what you're suggesting, and on the face of it, it seems like a nice idea. However, I fear that including such a mechanism in Struts would lead to serious security vulnerabilities in some peoples' applications. This is because essentially *any* method on the POJO could end up being invoked accidentally or maliciously. We had an issue like this with ActionForm some time ago, until someone pointed it out to us. -- Martin Cooper > From within the confines of my little world I'm not seeing the > downsides of this, so please feel free to shred my idea into oblivion > ;-) > > Michael > > > On Wed, 16 Mar 2005 11:36:58 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote: > > <SNIP> > > On Wed, 16 Mar 2005 14:08:58 -0500, Ted Husted <[EMAIL PROTECTED]> wrote: > > > On Wed, 16 Mar 2005 15:41:45 -0000, > > .............. > > > The teams with which I've met want a web framework to harvest input > > > values and render output values, so that their business classes can > > > focus on turning input into output. > > > > > > I'd suggest that something like POJO actions blurs the line even > > > farther. It implies that we want people to tie their whole application > > > to Struts. IMHO, that's not what we mean by "encouraging MVC and Model > > > 2". > > </SNIP> > > > > Boy, Howdy, as they say out West. I am as much behind this sort of > > thinking as you can be. > > > > Jack > > > > -- > > "You can lead a horse to water but you cannot make it float on its back." > > ~Dakota Jack~ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
