Unless Dave is right, Chad,which I don't think he is, the difficulty
is that you get as a name/value pair in the request parameters
[property].x=[some integer] and [property].y=[some integer] so that
the task becomes getting the name which is the "property" in
[property] rather than the value, i.e. [some integer], in the
name/value pair.  This problem, however, once you solve it simply
provides lots of benefits which can be transferred to other areas. 
Normally the getX() and getY() methods test for null or not null so
that you can then detemine which "property" name was fired.  That is
what is done well in the suggested options on
www.michaelmcgrady.com/button.  'Hope this is helpful.  If Dave is
right, then I have something else to learn.

On 5/11/05, Dakota Jack <[EMAIL PROTECTED]> wrote:
> I may be wrong, Dave, but I think you are going to get an integer
> value for getX and getY and not "Update".  Isn't that right?  That is
> why the solutions have to be a little more detailed and why we got
> saddled with the LookupDispatchAction and other heavy solutions.  Once
> again, I think the options at www.michaelmcgrady.com/button are
> instructive, even if you want to do something different.
> 
> On 5/11/05, Durham David R Jr Ctr 805 CSPTS/SCE
> <[EMAIL PROTECTED]> wrote:
> > > <form-property name="updateCart.x" type="java.lang.String"/>
> > > <form-property name="updateCart.y" type="java.lang.String"/>
> >
> > From the docs:
> >
> >     A way of retrieving these values through a form bean is to define
> >     getX(), getY(), setX(), and setY() methods, and specify your
> >     property as a blank string (property="").
> >
> > So, you could just do:
> >
> > <form-property name="x" type="java.lang.String"/>
> > <form-property name="y" type="java.lang.String"/>
> >
> > In a JSP:
> >
> >     <html:image property="" value="Update"
> >         src="/cerebus/store/images/updateCart.gif"/>
> >
> > Then in your action:
> >
> >         if (((DynaBean)form).get("x").equals("Update")
> >
> > Probably better to use the request parameter though, and not go through
> > the trouble of setting up the form properties.  Honestly, I don't see
> > what the image tag really adds beyond some module support via the "page"
> > attribute.
> >
> > HTH,
> >
> > Dave
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> --
> "You can lead a horse to water but you cannot make it float on its back."
> ~Dakota 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]

Reply via email to