> On Feb 15, 2016, at 1:30 PM, Jan Sindberg <[email protected]> wrote: > > We have seen the same, so lovely coined as "jar-hell", in many forums. We > almost choose to add the REST-server and talk with that to avoid the > dependencies. We never got to that, so I don't know if there is a thin > model available for REST?
Short answer ‘no’. Longer answer it’s possible, but requires breaking the core project up into pieces as being discussed on this thread. > > On Feb 15, 2016, at 1:30 PM, Jan Sindberg <[email protected]> wrote: > > If not, that could be a solution for some. > Moving the model into one module, wouldn't that still make you dependent of > real implementation and all the dependencies there is now - assuming you > would want to go with an API which connects directly to LDAP? I think we could have multiple ‘profiles’, each corresponds to what the client is doing for communication. One could be for ldap, two for rest impls. Of course this could be extended to include other protocols as well. Shawn
