It's important to note that there are two different sets of issues here.
The first is with regard to exposing Shiro components to client
applications - this is addressed by the patches for SHIRO-337 as well as
the code in the blog entry referenced by Les. The second is with regard to
configuring the Shiro system to integrate with other JEE components (e.g. a
Realm implementation backed by JPA) - this has not been addressed except as
one-off responses to queries posted to the list. The code in the referenced
blog entry does perform some configuration, though it assumes that the
default INI-based configuration is sufficient (which is probably not
sufficiently general and deviates from the recommended approach of using
@Alternatives for type-safe configuration).
