Jim Collings wrote:
Hmmm, so it seems from testing that I've been doing that the constant
is mandatory in all cases where you want params set before Prepare is
called while using paramsPrepareParamsStack AND you are using the
Convention plugin. K, got it. I think this also might explain why I
co
> The configuration constant I pointed to still isn't in there.
>
> In the default stack, the params interceptor does not run before the
> prepare interceptor. For instances where you need the params set
> first, then the prepare interceptor fires afterwards, we created the
> paramsPrepareParamsSta
On Thu, Jun 4, 2009 at 12:47 PM, Jim Collings wrote:
[...]
>>
>> > />
>>
[...]
> OK, well it should have been:
>
>
>
>
>
> value="com.stuff.something.web"/>
>
>
>
>
> In any case, it is not this type of mapping problem because the
> Prepare method is getting called ju
> I'm assuming you are using the conventions plugin (since there is no
> action definition). How are you making sure your
> conventions-configured actions are in the "stuff" package? If this is
> your configuration, in whole, then you need to add -
>
>
>
> Just matching up namespace is not enough.
I'm assuming you are using the conventions plugin (since there is no
action definition). How are you making sure your
conventions-configured actions are in the "stuff" package? If this is
your configuration, in whole, then you need to add -
Just matching up namespace is not enough.
Another opti
5 matches
Mail list logo
