> In our planned REST implementation, every method call will be
> receiving a session id in the authorization header.
> Therefore every method will start by calling the same boilerplate code
> to extract the associated session from Oracle, use that to extract
> user info and determine entitlements.
> (Or throw an exception if the session expired.)
>
> This seems like a pretty common use-case. Is there any way to handle
> that using annotations or through any other JSR-311 or Java standard
> construct?
> Some sort of AOP?
>
> Thanks, Victor
>
==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================