Thanks for the reply.
I think I will focus on the most important things to have closed scope ready
to merge with trunk:
- leave the current @Secured and @RolesAllowed annotations support based on
spring
- add a single root resource with 3 dedicated (JAXRS) methods
- add support for permissions and
Hi Łukasz
On Mon, Nov 1, 2010 at 8:41 PM, Łukasz Moreń wrote:
> Hi Sergey,
>
> Yes, I was doing some commits recently and I have some work uncommitted. It
> was mainly support for @Secured and @RolesAllowed annotations and few
> simplifications.
> Support for @RolesAllowed is done with using spr
Hi Sergey,
Yes, I was doing some commits recently and I have some work uncommitted. It
was mainly support for @Secured and @RolesAllowed annotations and few
simplifications.
Support for @RolesAllowed is done with using spring configuration:
I need to look how it can be done without spring.
The
Hi Lukasz
You've done some merges recently to the sandbox OAuth project, thanks.
I haven't had time to run the latest code yet, so can you please elaborate a
bit on what do you
think remains to be done before we can start working on preparing a move to
the trunk ?
I'm not sure about the support f
On Wednesday 22 September 2010 2:50:17 pm Łukasz Moreń wrote:
> Hi all,
>
> There are still "few" things to do with OAuth module before it can be easy
> usable for users.
>
> From what I see:
>
> - integration with java role based access control (@RolesAllowed, @Secured
> annotations). At least
Hi all,
There are still "few" things to do with OAuth module before it can be easy
usable for users.
>From what I see:
- integration with java role based access control (@RolesAllowed, @Secured
annotations). At least show how to configure that in demo.
- simplified configuration i.e. by register
