Loosely based on the paramsPrepareParams interceptor I found this
interceptor configuration to solve my problem
The params interceptor fires once before the prepare interceptor. So far
there're no side effects
I'm not sure why the paramsPrepareParams
input,back,cancel
input,back,
Am 14.03.2012 21:21, schrieb Dave Newton:
And you've set the other referenced properties appropriately?
Well, here are my settings
value="myapp-common" />
I double checked my code there seems nothing wrong with the pattern
matching in general. For instance when I request t
And you've set the other referenced properties appropriately?
On Wed, Mar 14, 2012 at 3:17 PM, Mounir Benzid wrote:
>
>
>
>
> Mounir
>
> Am 14.03.2012 20:12, schrieb Dave Newton:
>
>> Are you actually using the `namedVariable` pattern matcher?
>>
>> http://struts.apache.org/2.x/**docs/wildcard-
Mounir
Am 14.03.2012 20:12, schrieb Dave Newton:
Are you actually using the `namedVariable` pattern matcher?
http://struts.apache.org/2.x/docs/wildcard-mappings.html#WildcardMappings-Parametersinnamespaces
Dave
On Wed, Mar 14, 2012 at 3:09 PM, Mounir Benzid wrote:
My problem is the id
Are you actually using the `namedVariable` pattern matcher?
http://struts.apache.org/2.x/docs/wildcard-mappings.html#WildcardMappings-Parametersinnamespaces
Dave
On Wed, Mar 14, 2012 at 3:09 PM, Mounir Benzid wrote:
>
> My problem is the id is always null.
>
> First I thought it could be b/c
My problem is the id is always null.
First I thought it could be b/c of the way the defaultStack is set up so
I switched to paramsPrepareParamsStack, yet the problem still remains.
Any ideas on how to obtain the id from the request?
Thanks!
Mounir
@Namespace("/public")
public class Person
6 matches
Mail list logo