>>>>>>>>> "acceptedParamNames" to "[[\p{Graph}\s]&&[^,#:=]]*" in your param
>>>>>>>>> interceptor.
>>>>>>>>>
>>>>>>>> Right, I am using displa
uot; to "[[\p{Graph}\s]&&[^,#:=]]*" in your param
>>>>>>>> interceptor.
>>>>>>>>
>>>>>>> Right, I am using displayTag(displaytag-1.2.jar). The parameter
>>>>>>>
using displayTag(displaytag-1.2.jar). The parameter
>>>>>>> looks
>>>>>>> like:
>>>>>>>
>>>>>>> https://info/ProcessBrowse.action?d-6836677-p=7
>>>>>>>
>>>>>>> "d-6836677-p=7&
r-h...@struts.apache.org
--
View this message in context:
http://old.nabble.com/What-may-cause---ognl.InappropriateExpressionException--warning---tp21818620p26481347.html
Sent from the Struts - User mailing list archive at Nabble.com.
-
ps://info/ProcessBrowse.action?d-6836677-p=7
>>>>
>>>> "d-6836677-p=7" caused the problem. Is there any way that
>>>> "d-6836677-p=7" can be accepted?
>>>
>>>
>>> Ok, I did a hack to disable warning message as a temporal
onsLogger=ERROR
>>
>> --
>> Lu Ying
>>
>> -----
>> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
>> For additional commands, e-mail: user-h...@struts.apache.org
>>
>>
-
> Lu Ying
>
> -
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>
>
--
View t
params interceptor doesn't like parameters with spaces
in the name (this was fixed in xwork already), to fix it, set
"acceptedParamNames" to "[[\p{Graph}\s]&&[^,#:=]]*" in your param
interceptor.
Right, I am using displayTag(displaytag-1.2.jar). The parameter looks like:
https://info/ProcessBro
That should work, it will complain in the logs that it wasn't able to
bind that parameter to the action, but you can just ignore it, or
configure the params interceptor to ignore it.
musachy
On Wed, Feb 4, 2009 at 9:37 AM, Emi Lu wrote:
> Good morning Musachy,
>
>> params interceptor doesn't lik
Good morning Musachy,
params interceptor doesn't like parameters with spaces
in the name (this was fixed in xwork already), to fix it, set
"acceptedParamNames" to "[[\p{Graph}\s]&&[^,#:=]]*" in your param
interceptor.
Right, I am using displayTag(displaytag-1.2.jar). The parameter looks like:
If you are, the params interceptor doesn't like parameters with spaces
in the name (this was fixed in xwork already), to fix it, set
"acceptedParamNames" to "[[\p{Graph}\s]&&[^,#:=]]*" in your param
interceptor.
musachy
On Tue, Feb 3, 2009 at 5:36 PM, Musachy Barroso wrote:
> That looks familiar
That looks familiar, are you using displaytag?
musachy
On Tue, Feb 3, 2009 at 4:39 PM, Dave Newton wrote:
> Wouldn't it make sense to include the JSP/expression that's causing the
> error?
>
> Dave
>
> Emi Lu wrote:
>>>
>>> When switching query result page by page (online), I got the following
>
Wouldn't it make sense to include the JSP/expression that's causing the
error?
Dave
Emi Lu wrote:
When switching query result page by page (online), I got the following
warning message:
WARNING: Error setting value
ognl.InappropriateExpressionException: Inappropriate OGNL expression:
(d - 6
When switching query result page by page (online), I got the following
warning message:
WARNING: Error setting value
ognl.InappropriateExpressionException: Inappropriate OGNL expression: (d
- 6836677) - p
I am lost. Could someone tell me what may cause this warning please?
Info searched for
Good morning,
When switching query result page by page (online), I got the following
warning message:
WARNING: Error setting value
ognl.InappropriateExpressionException: Inappropriate OGNL expression: (d
- 6836677) - p
I am lost. Could someone tell me what may cause this warning please?
Th
15 matches
Mail list logo
