Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAMopvkPXR1=03XOKv7QJ8N5u00d1PFnKkcretus9Kpne12i4JQ@mail.gmail.com>
References: 
 <CABF62pnrGS03hodYJrMX4dC+hA5GDxdW2o3m=tWQj5erZVzKRw@mail.gmail.com>
	<CAMopvkPWb0H+-OVVn2q_iovRavgbmiBkN6jDJTa9505pHDD_pQ@mail.gmail.com>
	<CALaBdoqgL2fMwF7k_TSuQyrUTL_RtX9LDM2WWr6Mc3XQtxq11g@mail.gmail.com>
	<CAMopvkPoVKxBwa12sajS25D3d-TeUh2T==uA6Fn+XEy_ML_6AQ@mail.gmail.com>
	<CALaBdopvJD-O5bYZWZ2u_pZiocd9q98_mdH3sV9uEfHdL24-GA@mail.gmail.com>
	<CAMopvkNrD6UOc7GcBvZrfG8qtfi9HDhCddCr_-m1fLfWFv5jxQ@mail.gmail.com>
	<CALaBdop-RY_JUk=3+EPGt2+t03Ty0AUfWg9s4n_jkfbqwATSUg@mail.gmail.com>
	<CAMopvkPXR1=03XOKv7QJ8N5u00d1PFnKkcretus9Kpne12i4JQ@mail.gmail.com>
Date: Mon, 10 Dec 2012 19:39:41 +0000
Message-ID: 
 <CALaBdorbBomg03kfDs=SLQY4NDXWOiVqWmUUQa6Fr=+aZWuJuA@mail.gmail.com>
Subject: Re: REST Mappers
From: Antonios Gkogkakis <gkogkaka@tcd.ie>
To: Struts Users Mailing List <user@struts.apache.org>
Content-Type: multipart/alternative; boundary=f46d044401c202530804d084bada

--f46d044401c202530804d084bada
Content-Type: text/plain; charset=ISO-8859-1

> What would be the best way to share an example? Send it here on the list?
>You can register an issue and add text and example there or send it here


Since this is my first contribution I'll post it here :).  I based my
example on
https://cwiki.apache.org/confluence/display/WW/RestfulActionMapper so it
makes sense for someone viewing the wiki
Furthermore, I tested it struts 2.3.1.2 and I also have a similar working
example in production.

To use the Restful2ActionMapper in an existing struts application we have
to change the strus.mapper.class constant
and let it point to the Restful2ActionMapper
 <constant
name="struts.mapper.class"
value="org.apache.struts2.dispatcher.mapper.Restful2ActionMapper"
/>
The problem with the above approach is that we may break existing actions
because the Restful2ActionMapper tries to guess
the method name using conventions that aren't applicable to normal action
classes.

To overcome the above problem, we have to use a different action mapper
depending on the url we want to process.
REST actions will be processed by the Restful2ActionMapper and non-REST
actions by the DefaultActionMapper

To achieve that we have to rely on nampespaces and the
PrefixBasedActionMapper that can choose which action mapper to
use for a particular url based on a prefix (the action namespace).

To put everything together, we create a package for our rest actions
<package name="rest" namespace="/rest" extends="struts-default">
    ....interceptor config
     <action name="movie/*" class="app.MovieAction">
    <param name="id">{0}</param>
        ....results
     </action>
    ....
</package>
All other actions remain in their existing packages and namespaces

we use the PrefixBasedActionMapper telling it to use the
Restful2ActionMapper for actions
in the /rest namespace and the DefaultActionMapper for all other actions

<constant
name="struts.mapper.class"
value="org.apache.struts2.dispatcher.mapper.PrefixBasedActionMapper"
/>
<constant name="struts.mapper.prefixMapping" value="/rest:restful2,:struts"
/>

For the Restful2ActionMapper to work we also have to set
<constant name="struts.enable.SlashesInActionNames" value="true" />
<constant name="struts.mapper.alwaysSelectFullNamespace" value="false" />

@Chad
1) I think you are looking at the issue of failing to guess the method
using Rest conventions for non-REST actions
but in the context of the ActionMapper used in the REST plugin
I don't know if something similar can be applied to the
RestFul2ActionMapper, I just documented how we used
the Restful2ActionMapper
2) I've read your book, when I started working with struts2. Nice work
indeed !

Regards,
Antonios


>
>

--f46d044401c202530804d084bada--