Don't know whats the reason i'm getting this following WARNIng in latest
struts distro.
WARN [com.opensymphony.xwork2.ognl.OgnlValueStack]
(http-localhost/127.0.0.1:8080-1) Error setting expression
'action:documentManager!updateDocument' with value
'[Ljava.lang.String;@1c1abc1':
Looks like the colon char is not an expected input parameter.
You talk about latest distro, did it works before with other distros?
On 28 June 2013 09:43, Sreekanth S. Nair sreekanth.n...@egovernments.orgwrote:
action:documentManager!updateDocument
Twitter
Yes it was working
--
Thanks Regards
Srikanth
Software Developer
eGovernments Foundations
www.egovernments.org
Mob : 9980078913
On Fri, Jun 28, 2013 at 1:21 PM, Maurizio Cucchiara
mcucchi...@apache.orgwrote:
Looks like the
So, could you provide us some more details, maybe by filing an issue on
jira [1] with a sample code.
[1] https://issues.apache.org/jira/browse/WW
Twitter :http://www.twitter.com/m_cucchiara
G+ :https://plus.google.com/107903711540963855921
Linkedin
Updated in Jira
https://issues.apache.org/jira/browse/WW-4132
--
Thanks Regards
Srikanth
Software Developer
eGovernments Foundations
www.egovernments.org
Mob : 9980078913
On Fri, Jun 28, 2013 at 1:50 PM, Maurizio Cucchiara
fourni.
Date: Fri, 28 Jun 2013 13:13:26 +0530
Subject: OGNL WARNING
From: sreekanth.n...@egovernments.org
To: user@struts.apache.org
Don't know whats the reason i'm getting this following WARNIng in latest
struts distro.
WARN [com.opensymphony.xwork2.ognl.OgnlValueStack]
(http
obligatoire. Étant donné que les email
peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
aucune responsabilité pour le contenu fourni.
Date: Fri, 28 Jun 2013 13:13:26 +0530
Subject: OGNL WARNING
From: sreekanth.n...@egovernments.org
To: user@struts.apache.org
koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Date: Fri, 28 Jun 2013 15:42:56 +0530
Subject: Re: OGNL WARNING
From: sreekanth.n...@egovernments.org
To: user@struts.apache.org
As i replied in the jira, we are heavily depends on bang syntax, how can
we fix this... changing all
I got your point: what is explained on JIRA would not seem related to what
really happen.
On the other hand, it's just a debug message, I think is nothing to take
care.
Don't you think so?
Maurizio Cucchiara
Please forget my last mail, I mixed up the action name with the param name.
Anyway I have been able to test your specific use case, using the
blank webapp, and it works like a charm (that is without throwing any
exception).
So, I guess we need to know some further details.
Also, could you try to
to the target action causes an OGNL warning still fails
Please forget my last mail, I mixed up the action name with the param name.
Anyway I have been able to test your specific use case, using the
blank webapp, and it works like a charm (that is without throwing any
exception).
So, I guess we need
action causes an OGNL warning still fails
Please forget my last mail, I mixed up the action name with the param name.
Anyway I have been able to test your specific use case, using the
blank webapp, and it works like a charm (that is without throwing any
exception).
So, I guess we need to know some
...@gmail.com
Date: Thu, 8 Sep 2011 10:44:36
To: Struts Users Mailing Listuser@struts.apache.org
Reply-To: Struts Users Mailing List user@struts.apache.org
Subject: Re: Struts 2 WW-1714: Using the Redirect Action Result with
parameters to the target action causes an OGNL warning still fails
Users Mailing List user@struts.apache.org
Subject: Re: Struts 2 WW-1714: Using the Redirect Action Result with
parameters to the target action causes an OGNL warning still fails
Please forget my last mail, I mixed up the action name with the param
name.
Anyway I have been able to test your
Mailing Listuser@struts.apache.org
Reply-To: Struts Users Mailing List user@struts.apache.org
Subject: Re: Struts 2 WW-1714: Using the Redirect Action Result with
parameters to the target action causes an OGNL warning still fails
Please forget my last mail, I mixed up the action name
Hi,
I'm having some issues with this bug. Apparently it was fixed on 2.1.8,
but I've tested both with 2.1.8 and 2.2.3, and it still givin an error
message when I use a result like the following:
result name=enroll type=redirectAction
param
Does anything change if you change to lower the param name?:
param name=actionNamenavigateTo/param
Maurizio Cucchiara
On 7 September 2011 15:56, JOSE L MARTINEZ-AVIAL jlm...@gmail.com wrote:
NavigateTo
-
To unsubscribe,
You mean the param value for actionName? But that's the name of the action
where the user is redirected.
result name=enroll type=redirectAction
param name=actionNameNavigateTo/param
param name=navigateToEnroll/param
/result
action
18 matches
Mail list logo