Re: json result type not parse OGNL expressions in params

2012-10-21 Thread JOSE L MARTINEZ-AVIAL
I just tried that, but it does not make any difference. 2012/10/21 Per Pascal Grube > Hi, > > On Sunday 21 October 2012 03:12:07 JOSE L MARTINEZ-AVIAL wrote: > > Hi, > > I'm using a json result type defined as follows: > > > > class="org.apache.struts2.json.JSONResult"> > > false > > > > name=

Re: json result type not parse OGNL expressions in params

2012-10-21 Thread Per Pascal Grube
Hi, On Sunday 21 October 2012 03:12:07 JOSE L MARTINEZ-AVIAL wrote: > Hi, > I'm using a json result type defined as follows: > > > false > name="includeProperties">resultName,resultMessage,data.*,fieldErrors.*,actio > nErrors.*,actionMessages.* name="excludeNullProperties">true > true > ${erro

Re: json result type not parse OGNL expressions in params

2012-10-21 Thread JOSE L MARTINEZ-AVIAL
I just reviewed the code, and it seems that the HttpHeaderResult only parses the parameters headers and errorMessage, but not the parameters status or error. I think it could be a nice thing to have. my workaround is to extend JSONResult incorporating the following: public void setStatusCode(Strin

Re: Custom error result for ExceptionMappingInterceptor

2012-10-21 Thread Antonios Gkogkakis
Another option would be to extend the ExceptionMappingInterceptor and override the findResultFromExceptions method. In the overriden method you can do your checks and return a global result accordingly Antonios On 20 October 2012 21:35, JOSE L MARTINEZ-AVIAL wrote: > Hi, > I want to use Exce