Hi, On Thu, Apr 10, 2014 at 2:13 PM, Tobias Bocanegra <[email protected]> wrote: > On Thu, Apr 10, 2014 at 11:01 AM, Jukka Zitting <[email protected]> > wrote: >> Hmm, it should be available by default in a Sling environment: > > yes, in sling. but what if we run oak w/o sling?
It's up to the deployment to make all required dependencies available to the components that need them. In a plain java deployment you'd just pass the dependency as a constructor or setter argument. >> There's no major functional difference between the two types of >> repositories, so unless you specifically need one over the other, it's >> easiest to use the one that's already available. > the difference is, that the login context is setup by oak-core and so > the callback handler can only provide oak API classes right now. Callbacks should not be used like this, see http://markmail.org/message/nb2j324ppfdop34f. BR, Jukka Zitting
