I modified the Skeleton Key example and see that it does work with the
@RolesAllowed annotation which makes sense.  I know have different roles
for the CustomerService REST methods and the ProductService rest methods.
 The Skeleton Key solution is looking very good and will be good for many
of the requirements we come up against.

Thanks Bill!

*Doug Schnelzer*
*Technical Director, **Vizuri*

On Mon, Apr 15, 2013 at 2:36 PM, Doug Schnelzer <dschnel...@vizuri.com>wrote:

> In the oauth2 skeleton key example their was just one role ("user")
> specified for the database-services REST services.  Is it easy to protect
> some services with one role (say using the role "customer" for the
> CustomerService) and another required role for other services (say using
> the role "products" for the ProductService)?  Can I use the @RolesAllowed
> annotation?
> Thanks for the help
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
Resteasy-users mailing list

Reply via email to