I looked at the CVS code last night, and it seems like the latest code
acquires the ServiceManager from the container-manager context, and then
proceeds to wrap it in a DefaultServiceManager. Is there any reason why the
wrapping needs to happen? In our application, we have a specialized lookup
method that takes a context, so that authorization can be checked when the
service is obtained. I have worked around it by later wrapping the
DefaultServiceManager again in another KeelServiceManager, but it'd be nice
if Fortress used what it was provided when the container was setup.
Shash
_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
