Due to the nature of HTTP, you cannot pass an object from
the client's browser to the Action. Instead you either need
to
a. pass the form fields/request parameters you need to build
your object again
or
b. store the Object in the session so you can retrieve it when
the Action is called.
I don'
It seems to me that you should consider refactoring your actions.
I would make a separate class that Action B delegates to in order
to create the JPG data. Then Action A can use this other object
without any problem. If there is shared state between the two, and
you need to have the same instance
Wow. I'm stumped. As I said, I don't have firsthand experience
with DynaForms...
Only thing I can think of is, did you set the input to your
JSP correctly in the struts-config?
Not to sound overly optimistic, but it's GOT to work. It uses
the same functionality on the sending as it does when sett
Hello Temp,
It seems like you want to use a combination of the
nested bean property naming and list-backed properties.
I think your property name in the form element will be
something like
mybean.prop
which will result in form.getMybean().setProp() when
the form is submitted.
I believe your s
Having never used DynaValidatorForm before, I'm not 100% sure what
the means for accessing the properties would be. It's clear that
getCatalogID() is not going to be defined on DynaValidatorForm
as an available method. So I'd try calling getDynaProperty() and
if that doesn't work you should researc
To the best of my knowledge, ActionErrors is deprecated
in 1.2. Note that ActionError is NOT deprecated, nor are
ActionMessages or ActionMessage. The API documentation
says to use ActionMessages.GLOBAL_MESSAGES instead.
That said, I don't know how you differentiate between
messages and errors if y
You might want to check Globals.MESSAGES_KEY
although this isn't how I understood the MessageResources to
work, I thought the ActionMessages was stored in the request
under the Global.MESSAGES_KEY and not the MessageResources...
anybody else?
> -Original Message-
> From: Scott Purcell [
Just having learned this last week, it's fresh in my mind.
Looks like you are missing the call to
this.saveErrors(errors);
this puts the ActionErrors into the request for your JSP
to display.
The other thing I'd say is that ActionErrors is deprecated;
you might use ActionMessages instead, which
No. This won't work automatically.
You can, however, use the tags or use scriptlet
code to access your form bean in the request/session and
pull the properties out that you need.
> -Original Message-
> From: wo_shi_ni_ba_ba [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 08, 2005 3:28
The good news is that this DOES work.
I simply declared my methods to be
public void setFoo(String key, String[] foos)
{
...
}
public String[] getFoo(String key)
{
...
}
and everything works fine. It took a detour through the Struts
source (and ultimately from there through the beanutils source
Note that there's also the java.util.LinkedHashMap which will
maintain whichever order you insert the values in. This gives
you the consistency of TreeMap without the overhead of resorting,
if your data is already sorted when you're populating the Map.
It also has a funky LRU-style option that orde
This works fine for list-backed form items (which we also use)
but in this case I need something like
public void setFoos(String key, String[] foos)
is this possible?
There are several workarounds I can think of, but this appears
to be the cleanest solution if I can make it work.
Mike
> -
12 matches
Mail list logo