[jira] [Commented] (SHIRO-39) JEE integration

["Benjamin Marwell (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SHIRO-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079642#comment-17079642 ] 

Benjamin Marwell commented on SHIRO-39:
---------------------------------------

EE is a big collection of standards.

There are (not exhausive):
 * CDI for Dependency Injection
 * Datasources using {{@Resource}} or other means, either by jdbc or more abstract: JPA.
 * Config via MicroProfile Config (which is somewhat similar to Spring's config mechanisms).
 * OpenAPI via MicroProfile OpenAPI
 * Threading by using {{@Resource ManagedExecutorService}} via concurrent
 * A new implementation-indipendent JSON api (both bindings and imperative) via jsonb and jsonp
 * EJBs (both remote and local)
 * Messaging via JMS

 

All of these are pluggable in many modern containers, e.g. wildfly or OpenLiberty. So they would need to be pluggable in Shiro 2.0 as well, if we wanted to use/support them. Which do make sense, which do not? The topic of this issue is very broad.

> JEE integration
> ---------------
>
>                 Key: SHIRO-39
>                 URL: https://issues.apache.org/jira/browse/SHIRO-39
>             Project: Shiro
>          Issue Type: Task
>            Reporter: Les Hazlewood
>            Priority: Major
>
> Make it easy for Ki to run inside a JEE server, using only JEE configuration mechanisms (annotations, JNDI).  Do not rely on Spring or other container-specific config if at all possible.  Write a sample app that can run in any JEE container (JBoss, Geronimo, etc).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)