Thank u for everything! I will keep studying! :D
--
Manolo Pájaro Santander
Ingeniero de Sistemas VIII Semestre (Actual)
<>
CUSOL-UAC
Linux Registered User # 522026
Exactly, so the default (execute) would run the validation, but not the ones
that are listed.
(*Chris*)
On Mon, Jul 25, 2011 at 4:53 PM, Mano Pájaro wrote:
> I see mm so, it only acts on the action which method attribute is diferent
> from in the list, that's it? :D
>
> 2011/7/25 Chris Pratt
I see mm so, it only acts on the action which method attribute is diferent
from in the list, that's it? :D
2011/7/25 Chris Pratt
> Not exactly. It would not execute for actions whose method name is input,
> back or cancel. It's on the action side, not the result side.
> (*Chris*)
>
>
--
Ma
Not exactly. It would not execute for actions whose method name is input,
back or cancel. It's on the action side, not the result side.
(*Chris*)
On Mon, Jul 25, 2011 at 2:59 PM, Mano Pájaro wrote:
> Thanks Maurizio, let me see if i got it straight. You mean that, for
> example:
>
>
>
Thanks Maurizio, let me see if i got it straight. You mean that, for
example:
input,back,cancel
won't be executed by results whose name is input, back or cancel?
2011/7/25 Maurizio Cucchiara
> There are some interceptors, like validator one, which are not triggered in
> ca
There are some interceptors, like validator one, which are not triggered in
case of the name of the invoked method matches one of the list element
(there is no reason to validate an input action, you don't yet obtain the
user input, so you have anything to validate).
Hope this help.
Maurizio Cucch
Hello list! I'm making a research about Struts2 and there are several things
that I don't understand (haha), I have studied really hard and I think I'm
in the righ way now, but there's a thing that i don't understand about this
examples i found about interceptors, i'm talking about the parameter
ex
Hi,
2008/6/9 Stanley, Eric <[EMAIL PROTECTED]>:
> Dave,
>Thanks. So if I understand you, I can set all my url's that
> don't use params to excludeParams, but leave the ones that use params
> alone? Also, where do I set the constant? Im sure its just me, but this
> doesn't seem like a wise
e
beneficial to append any parameters that are not explicitly coded?
-Ryan
-Original Message-
From: Dave Newton [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2008 9:18 AM
To: Stanley, Eric
Subject: RE: Parameter question
Okay, then the rest of my reply is probably helpful :)
It can be
parameter should only apply to that action/link.
-Ryan
-Original Message-
From: Dave Newton [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2008 7:15 PM
To: Struts Users Mailing List
Subject: Re: Parameter question
Are you talking about links to actions having parameters appended?
If so
Are you talking about links to actions having parameters appended?
If so, are you either excluding parameters at each or,
alternatively, setting a default excludeParams via config?
Dave
--- On Thu, 6/5/08, Stanley, Eric <[EMAIL PROTECTED]> wrote:
> In my app, I have this package/action def
All,
In my app, I have this package/action defined:
/pages/data/viewData.jsp
/pages/error.jsp
The problem is that as soon as its called, every subsequent action has a
bunch of parameters appended to it. This causes any other action to
fail. They fail because there is no object
For your posted example, where that value you want to pass is the value
you're rendering in the hidden field, you can just use the same OGNL
expression in both places:
...
...
If that hidden input's field is being changed by client-side Javascript,
though, or needs to come from a
Hmm, I see your point. I do not really need to do any
fancy Ajax stuff here, I just want an action invoked
by a url link to have access to what was selected on
the page (which I was going to stuff into a hidden
field.)
I know I can do this with a form and submit button,
but surely there is a way
--- Scott Nesbitt <[EMAIL PROTECTED]> wrote:
> I would like to have a url pass a parameter based on
> the value of a field on the JSP. My code looks like
> this:
Unless the field is set by the Action before
displaying the JSP the parameter won't hold a value
until it's submitted.
> actio
I would like to have a url pass a parameter based on
the value of a field on the JSP. My code looks like
this:
Lineup History
Sadly, in my action class this:
log.debug("In execute, parameters size: " +
parameters.size());
says zero.
If I use the name of a select tag instead of a hi
16 matches
Mail list logo
