Hi Guillermo,
You should be able to add ?method=method2 to your path statement (. We use something
very similar for the input tag. The only thing we do differently is that
we use a different parameter name. Whereas our base action mappings use
dispatchAction as the parameter, we use "valid
Hi Jacob,
I asked almost the same question when we were implementing validation. We
had the same issue with preparing things before creating the user page. We
ended up creating an input that forwarded to a mapping that was basically a
duplicate of the one with the validation failure. The o
Samuel,
If you look in the struts-config.xml file, within the tags,
there is a statement - inputForward="true" - that indicates the type of
value that will be specified in you input tags. If "true" is specified,
then your input tags must refer to a forward name. If "false" is specified
or
DispatchActions with validation
|
>----------|
> From: "Nicholas L Mohler"
> <[EMAIL PROTECTED]>
> Date: Mon, 17 May 2004 09:27:11 -0400
>
> Hi Jacob,
>
> I asked almost the same question when we were
&g
Hi Samuel,
I'm not sure why the input couldn't accept pages and forwards within one
application. That's probably a good question for the major contributors to
the framework. For the struts-config.xml file Ted Husted's book, "Struts
in Action", is a good reference that I have used . The boo
Satish,
The problen occurs because of the "indexed" getter/setter. if you change
the name from getStatus(int Index) to getOneStatus(int index) (or some
different name that you like). The problem will be resolved.
The indexed getter is used by Struts when your form is submitted.
Nick
Most likely the "browseType" parameter is not defined in you page, so it is
not submitted.
If you're using the struts submit buttons, you probably have something to
the effect of:
The effect of the button tag is that when it is clicked, the "browseType"
parameter will be added into th
cified' method of the LookupDispatchAction used to
> handle
> this issue though? I thought that's exactly what it's purpose was,
> but the
> method is not getting executed as I expected it to.
> Very frustrating...
>
>
> - Keith
>
>
>
> -Orig
Not having any information about what you're trying to do, its hard to give
you an answer. I think that your answer will start with using the indexId
attribute on the the iterate tag. Where the answer goes from there depends
on what you're doing.
Nick
|-+---
d out select Box Name.
Here is the code i am writing
Here I am able to display the values from Iterate tag but i want to name of
the select box in the Iterate tag. How to find out the name ..
Please help me
Thanks
Srinivas
Nicholas L Mohler <[EMAIL PROTECTED]> wrote:
We have a similar situation with our validations. We created our own
validators to handle those situations. For the javascript, we cloned the
javascript for the validation and added logic to apply the validation when
a field was populated - very easy. For the server-side validation, our
ja
?
Integer does not depend on the required validation, so it should be fine -
if there is nothing in the field the validation will just return true.
Sample code in validation.xml would be:
Matt
- Original Message -
From: "Nicholas L Mohler" <[EMAIL PROTECTED]>
To:
Kevin,
I think it depends on how you're deploying your reports.
Are you deploying your reports using Crystal's "E-Portfolio"? If so, I've
haven't tried this, so I can't be much help.
Are you deploying via jsp? If so, then your action mapping just needs to
point to the jsp/tile that calls and s
Hi,
We are having a problem that occurs when a property fails a server-side
validation. The problem is that the value that we specify for the "input"
tag is not correctly resolved and we end up with a blank page being
returned, as opposed to the page that originated the error with the
appropr
Subject: Re: Strange Validation Behavior
|
>--|
Send your mappings so that others can "trace" the path along with you, an
15 matches
Mail list logo
