Hi Jeromy,
Many thanks for your thoughtful feedback on this issue.
Jeromy Evans wrote:
Personally, I never expose primitives as properties of an action
because null values are always legal over this interface. In the
special case of Boolean which can easily accidentally cause an NPE, I
alway
Giovanni Azua wrote:
Personally, I never expose primitives as properties of an action
because null values are always legal over this interface. In the
special case of Boolean which can easily accidentally cause an NPE, I
always make the getter return false if the value is null..
This validatio
Hi Jeromy,
Jeromy Evans wrote:
2nd, the parameters interceptor is called and sets properties of your
action. It cannot set primitives to null, so it does not write to
these properties.
3rd, the validation interceptors are executed. They cals the getters
of your action instance and observe th
Giovanni Azua wrote:
hi,
I provided declarative XML validation for a form where the action
would expose primitive type properties. The problem is that a
primitive type property left blank in the form would never be caught
as not provided by the "required" validation. The property would
inste
hi,
I provided declarative XML validation for a form where the action would
expose primitive type properties. The problem is that a primitive type
property left blank in the form would never be caught as not provided by
the "required" validation. The property would instead be set with the
def
Hi,
if the action string is being evaluated in the URL tag
what does it output the expression as it is, If we
have the same expression in value attribute it does
evaluate, That is where we are doubtful.
In portal mode the action attribute does convert the
string to portal string where as value d
In the simple case, this:
and this:
would be identical. You can also use the tag to include request
parameters. You can create any URL you need using the value attribute
and params.
You referenced portal in your email so you might be using this in a mode
I haven't tried. Looking at the
Yes you are right,
Even though action attribute doesnt get evaluated
value attribute does,
but that is of no use as it does not create the URL
string to suite with Portal env.
The biggest concern is why the action attrbute of URL
tag doesnt evaluate.
that is following doesnt work
--- tom tom <[EMAIL PROTECTED]> wrote:
> for the second one there is no href
> attribute for the URL tag hence doesnt work.
The "value" attribute creates the href if the "action"
attribute isn't used.
d.
___
Hi,
Thanks for the reply,
I tried both but with no luck,
Option 1 as stated I gave $actionName but doesnt
evaluate and for the second one there is no href
attribute for the URL tag hence doesnt work.
I tried various combinations like
c:out, ${actionName}, ${testID.actionName} and also
%{actionNa
I haven't tried to use a dynamic action name like that so can't comment
on whether its a bug or feature, but one of these options should work:
1. Try using the ${} notation without the c:out
(I can't find the reference for this approach but it's somewhere on the
wiki)
2. Alternatively, work
Hi,
We are experiencing that action attribute of the
.
.
Is there any way to overcome this kind of
requirements.
Thanks
__
I downloader the archive with version 2.0.5 today,but I can't handle the
's treeSelected event using my code.
I found this error even in the example showcase.Is this a bug?
On 5/9/06, A. Alonso Dominguez <[EMAIL PROTECTED]> wrote:
Hi there!
I'm trying to use the new struts-action framework, version 1.3.3 with tiles
and faces. I'm following the example applications but I found possibly a bug
when rendering a struts-based FormBean.
...
While you wait for someone wh
Hi there!
I'm trying to use the new struts-action framework, version 1.3.3 with tiles
and faces. I'm following the example applications but I found possibly a bug
when rendering a struts-based FormBean.
The jsp code that I was using is as follows:
Yes. That's it.
Thanks a lot.
Tim Jian
Momentum systems, Inc.
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Friday, June 03, 2005 11:27 AM
To: Struts Users Mailing List
Subject: Re: -- is this a bug
From: "Qinjian Jian" <[EMAIL PROTECTED]&
d unchanged and still
> were checked. I can see them both on jsp page and form bean's property
> selectedUsers. Is this a bug for the tag?
http://struts.apache.org/userGuide/struts-html.html#multibox
" WARNING: In order to correctly recognize cases where none of the
associated
both on jsp page and form bean's property
selectedUsers. Is this a bug for the tag?
Thanks.
Tim Jian
Momentum systems, Inc.
18 matches
Mail list logo
