Hi, On Mon, Feb 10, 2014 at 2:55 PM, Jukka Zitting <[email protected]> wrote: > On Mon, Feb 10, 2014 at 5:49 PM, Tobias Bocanegra <[email protected]> wrote: >> On Mon, Feb 10, 2014 at 1:30 PM, Jukka Zitting <[email protected]> >> wrote: >>> On Mon, Feb 10, 2014 at 2:50 PM, Tobias Bocanegra <[email protected]> wrote: >>>> in case of the LoginModules, that's not possible. >>> >>> But accessing the whiteboard is? I don't see what's special about the >>> whiteboard, it's just a service dependency like any other. >> >> No, it's a piece of infrastructure, and part of the Oak SPI. I think >> that components should be able to rely on a system wide Whiteboard if >> they want. >> Also, the LoginModules are not 'services' in that sense. they get >> instantiated by JAAS and can only communicate via Callbacks with the >> login context. > > The thing I don't understand here is why you'd be able to access the > Whiteboard instance, but not some other service. If it's "not > possible" to access a reference to a normal service, how would it be > possible to access a reference to the Whiteboard?
Aha! Because I make the Whiteboard available through the SecurityProvider.getConfiguration(Whiteboard.class) as a workaround - but I don't like this. I'd rather offer it via a Callback. Regards, Toby
