On 9/12/2012 12:25 PM, David M. Lloyd wrote:
If this is in the context of a deployment, then yes the TCCL will be
the
class loader of the deployment and that's the one you should use if you
want the *combination* of services provided to the deployment by the
container *plus* the services defined in the deployment itself. But
you're using an intermediate aggregate module (which we don't normally
do for AS services). This means in order for it to work you have to do
two things:
1. Set the dependencies whose services must be visible to the deployment
to services="export"
2. When the module is imported into the deployment (presumably via the
deployer), it has to import services from that dependency as well.
Well, in this case, my module is only being used/referenced from a
configured standalone.xml security-domain login. So I don't think i
need to export any services, correct? I was able to get things working
if I manually set the context class loader from with the LoginModule
code. But this leaves me wondering if there's something I can do
internally in Resteasy to have a cover-all solution (please see my
previous email/response).
Bill
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com