Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] [jakartaee-ambassadors] Re: Jakarta EE Backlog -> Guide to Jakarta EE 10

Isn't there a @RolesAllowed in Jakarta Security and the idea would be to deprecate it in Jakarta REST in favor of that?
If Security needed a little more modularity or a "light" module where Authentication or Authorization may not always be required, I guess that is also something to explore.


On Fri, Jun 19, 2020 at 5:47 PM reza_rahman <reza_rahman@xxxxxxxxx> wrote:
I believe the idea is to use CDI when it is available and possible. So it is more "supports" than "requires". However, best to clarify this with folks like Markus.

Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker

Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.

Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone

-------- Original message --------
From: Kito Mann <kito.mann@xxxxxxxxxx>
Date: 6/19/20 11:39 AM (GMT-05:00)
To: arjan tijms <arjan.tijms@xxxxxxxxx>
Cc: Jakarta EE Ambassadors <jakartaee-ambassadors@xxxxxxxxxxxxxxxx>, Jakarta EE community discussions <>
Subject: Re: [] [jakartaee-ambassadors] Re: Jakarta EE Backlog -> Guide to Jakarta EE 10

On Wed, Jun 17, 2020 at 1:43 PM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

On Wed, Jun 17, 2020 at 6:50 PM Vano Beridze <vanuatoo@xxxxxxxxx> wrote:
2. @RolesAllowed for JAX-RS resources

Maybe not so much needed as JAX-RS resources will be deprecated in favour of it all being CDI beans, and then the Jakarta Security API will define a CDI/Interceptor based @RolesAllowed.

Is JAX-RS going to require CDI? I'm not sure that's a good idea. Some frameworks use those annotations without any DI. 

Kind regards,


You received this message because you are subscribed to the Google Groups "Jakarta EE Ambassadors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jakartaee-ambassadors+unsubscribe@xxxxxxxxxxxxxxxx.
To view this discussion on the web visit
_______________________________________________ mailing list
To unsubscribe from this list, visit

Back to the top