Hi, On Mon, May 17, 2010 at 11:00 AM, Thomas Müller <thomas.muel...@day.com> wrote: > - If you move classes to other packages, you will have to make many > method public.
My ultimate goal is to track down all these cases and refactor them away so we can better control all the code paths to and from a single session. By moving the session-related classes to their own package I'm able to use tools like jdepend to enforce strict access patterns. This is by no means a trivial refactoring, but I believe it's necessary since the complexity of the current o.a.j.core package makes implementing JCR-890 close to impossible. > Instead of moving session related classes to a separate package, what > about moving unrelated classes to different packages? These unrelated classes are mostly things like RepositoryImpl, TransientRepository, RepositoryCopier, etc. to which many external codebases are linking, so we can't move them. BR, Jukka Zitting
