e to ALWAYS implement that interface
>> when
>> processing forms? (Or am I just too paranoid?) What is the general
>> consensus on this issue? (I could not find too much information on
>> this…)
>>
>> Lastly, instead of using the interface, would it be a good idea
interface, would it be a good idea to
have a
dedicated annotation for this?
Thanks!
Regards,
Gunnar Hillert
--
View this message in context: http://www.nabble.com/-S2--Form-
Processing---Security---ParameterNameAware-tf3944023.html#a11509072
Sent from the Struts - User mailing list
gt; Regards,
>
> Gunnar Hillert
>
>
--
View this message in context:
http://www.nabble.com/-S2--Form-Processing---Security---ParameterNameAware-tf3944023.html#a11509072
Sent from the Struts - User mailing list archive at Nabble.com.
--
dedicated annotation for this?
Thanks!
Regards,
Gunnar Hillert
--
View this message in context:
http://www.nabble.com/-S2--Form-Processing---Security---ParameterNameAware-tf3944023.html#a11187846
Sent from the Struts - User mailing list archive at Nabble.com
Thanks Laurie, I didn't even think of that.
I am going to explore what Michael posted, because I like the tidiness
of that solution.
Chris
On 3/3/06, Laurie Harper <[EMAIL PROTECTED]> wrote:
> Just for balance ;-) I'll also point out that you don't *have* to
> disable automatic validation to ach
Just for balance ;-) I'll also point out that you don't *have* to
disable automatic validation to achieve your goal; there are approaches
that will allow you to retain that functionality, too.
One possibility is to point the 'input' attribute to the same
DispatchAction and have one of the meth
Thank you for your help, I'll give all this a try :)
Chris
On 3/2/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> On 3/2/06, Chris Cheshire <[EMAIL PROTECTED]> wrote:
> > Thanks Michael, both of those are helpful.
> >
> > I have a few extra questions though:
> >
> > Regarding ActionDispatcher
On 3/2/06, Chris Cheshire <[EMAIL PROTECTED]> wrote:
> Thanks Michael, both of those are helpful.
>
> I have a few extra questions though:
>
> Regarding ActionDispatcher -
> * The ParameterListActionDispatcher class isn't in the 1.2.8 struts
> distribution that I downloaded, and is linked as a bugf
Thanks Michael, both of those are helpful.
I have a few extra questions though:
Regarding ActionDispatcher -
* The ParameterListActionDispatcher class isn't in the 1.2.8 struts
distribution that I downloaded, and is linked as a bugfix. Do I need
to download the entire struts source, add this in a
On 3/2/06, Chris Cheshire <[EMAIL PROTECTED]> wrote:
> I want to set up a form that is entered over 3 successive pages.
>
> I have a single form bean for all of them that includes all of the
> fields, and the validate method only validates the fields that were
> implemented on each particular step.
I want to set up a form that is entered over 3 successive pages.
I have a single form bean for all of them that includes all of the
fields, and the validate method only validates the fields that were
implemented on each particular step.
Step 2 will present 1 of 2 sub-forms, depending on an option
Hi Lee
Set your form property type to String. you could use "date" validation in
validation.xml. Whenever it's needed the type converting from String to Date
could be performed.
Nafise
-
Do you Yahoo!?
Yahoo! Mail - now with 250MB free stora
Thanks for your help. I changed the type to java.sql.Timestamp and my
problem went away.
I'm still having a tough time getting Hibernate to
prevent 2 users from changing the same data. For any kind souls who
know about such things, I've written up my problem on the hibernate
forum.
http://foru
I wonder if this has anything to do with what Joe Germuska explained
in a different thread:
"This is because the BeanUtils library *does* register a standard
converter for java.sql.Timestamp (as well as java.sql.Time and
java.sql.Date) but *does not* register a standard converter for
java.util.Dat
I have a date field: lastModDate
I am using dynaForms and have the following form:
My display of the form works fine. I can see the value...there are no
type issues.
When I try to save the value I get the following error:
==
OK. Now it works, sort of. On the form I am processing there are
2 sets of checkboxes. One set is simply made using html:multibox.
The other set is inserted by a single custom tag that I wrote.
I followed your suggestion (but had to dig for details) and created
the following:
public class SeriesPro
> From: Dean A. Hoover [mailto:[EMAIL PROTECTED]
> I don't quite understand how DynaActionForm
> gets populated when a form is submitted. The
> form I have gets processed exactly as I expect,
> except for a group of checkboxes
(This is a FAQ-- the answer is in the list archives multiple times.)
I don't quite understand how DynaActionForm
gets populated when a form is submitted. The
form I have gets processed exactly as I expect,
except for a group of checkboxes (generated in
JSP by a custom tag I wrote). If I have one or
more checked it works fine. However, if I uncheck
all of them, it fa
18 matches
Mail list logo
