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
__
7 matches
Mail list logo
