2018-04-29 11:24 GMT+02:00 Yasser Zamani :
> I couldn't understand what's the user expected behavior and what we
> should try to fix. Because of security, SMI is enabled by default and
> user has to annotate or define allowed methods. right? I think there are
> no other solution to keep both securi
Thanks for your reply.
I am already using struts-2 rest plugin in production. What we are trying to
solve here, is a hierarchical resource entity API implementation.
Let me give an example of what I am trying to do.
For getting an organization info, we can use a REST API like
/organizations/orga
Hi Yasser,
We already have a layer of security(a filter which runs first in our
web-app) which handles allowed url patterns. So in this we have to again add
code for allowed methods. So we are trying to get an option to disable it.
Thanks,
Deva.
--
Sent from: http://struts.1045723.n5.nabble.c
On 4/26/2018 4:03 PM, Lukasz Lenart wrote:
> Thinking on solution ... not so easy :(
I couldn't understand what's the user expected behavior and what we
should try to fix. Because of security, SMI is enabled by default and
user has to annotate or define allowed methods. right? I think there are
On 4/27/2018 11:45 AM, DevaGerald wrote:
> Hi,
>
> Sorry if i miss something here. As of my knowledge, the struts 2 rest plugin
> supports only the following :
> /resource - GET
> /resource - POST
> /resource/$resource_id - GET
> /resource/$resource_id - PUT
> /resource/$resource_id - DELETE
>
5 matches
Mail list logo
