Dave Newton wrote:
Removing the REST plugin restores regular S2 .action accessibility. So I guess
my questions are: is this by design, and is there a way to combine both in the
same app?
No, you can't use both approaches in the same app.
You can get most of the way by setting up the a composite action
mapper. Not THE CompositionActionMapper, but rather one that splits the
handling based on the URI.
eg. if it ends in .action, send to default action mapper, otherwise send
to RESTful action mapper.
That's not a complete solution though. The rest plugin overrides the
ActionProxyFactory with one that creates RestActionInvocations. You can
have DefaultActionInvocations and RestActionInvocations in the same
application unless you create a composite ActionProxyFactory.
It's all in or not at all I'm afraid.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
