Creating interface visibly outside package, but not implementable

Question

Hi,
I want to make interface which is implementable only within its package, but usable also outside the package.
for example:
package a
interface A {...} // not implementable out of the package
public interface Asafe1 extends A {...} // implementable out of the package
public interface Asafe2 extends A {...} // implementable out of the package
package b
public class Aimpl1 implements Asafe1 {...}
public class Aimpl2 implements Asafe2 {...}
public class Driver
     void doSomethong()
          for (A a : aList)
              // do some A stuff
}Is there a way to do it?
Edited by: s_roee on Aug 24, 2009 4:38 PM
Edited by: s_roee on Aug 24, 2009 4:38 PM

Answer 1

Hi,
I guess that there's no much difference if I put the interface here as an static internal interface of SomeClass, or as a package visible interface...
Its a little hard to understand how it bypass my problem.
Let me give an example (not the real example..) of a place my design takes place.
So, lets say that There is an interface IUSACitizen implementation,
Now lets say that every state treats its citizens with whole different methods and processes, so each state has its own IUSACitizen, like New Tork having NewYorkCitizen, Whashington has WashingtonCitizen.
For the sake of state purposes, new york processes will use NewYorkCitizen, but for the sake of U.S level usage, it will treat them all as IUSACitizen.
So, I want that methods that need to use IUSACitizen will be able to do so, but methods that will try to implement IUSACitizen will have to go through one of the underlying classes/interfaces.