Prev: restrict access of functionality
Next: DB as Imposed Model (was: Mixing P/R philosophy with OO...)
From: learning on 12 Apr 2007 15:54
Hi I am trying to build on JUNIT, but I want to restrict access to the
functionality that JUNIT has. Because it might extend the funciton of
it but don't want to change the core of junit, so taht when a new
version comes, I just plug it in on ground that their public interface
don't change.

I am going to add some pre/post condition on that and going to change
the UI to XMl based.


This way, i don't need to do a merge on thier code base.

So how can I thorw a compilation error when the clients that use my
wrapper try to uses junit directly?
how can I restrict the access modifier of somehting that is more lax
to something that is more restrictive?

any design pattern that can do that?

 | 
Pages: 1
Prev: restrict access of functionality
Next: DB as Imposed Model (was: Mixing P/R philosophy with OO...)