Re: Discussion: SecurityContext
On Thu, Jun 1, 2017 at 12:28 AM, Bill Shannon <bill.shannon@...> wrote:
You're absolutely right, good catch!
Okay, I was wrong here then. When called from another container or "entry point" into the application (not sure what you would call inflow into a JCA connector exactly), you cannot just call that method.
For a next spec release I could imagine a JNDI like namespace prefix, with java:app/[module name] querying for a specific module in the application and java:module being the default for the current module (which would then throw an IllegalArgumentException if called from an EJB module).
From an EJB:
Queries for /admin for app1 and app2
From web module app1
Queries for /admin for app1, where /admin must be treated equal to java:module/admin
Queries for /admin for app1 and app2, where java:app/app1/admin must be treated equal to java:module/admin