Package restriced interfaces

Question

I,ve read a bit about access modifiers for interfaces. I want to define an interface restricted only to the package. I would do that by leaving out the access modifier in the interface declaration. Then I have the class implementing the interface (obviously, in the same package). Since I made the interface accessible only in the package, I would assume I would be able to also restrict the implementing methods to the package.Why am I forced to make the implemented method public?
Thanks for your time,
Cheers,
Radu Cosmin

Answer 1

True. This is kind of exacly my case. I want to extract that mehot (those methods) in an interface to keep the code clean, elegant an logic, but my main concern is to keep (as in your example) m() as being accessed only within the package. This is my example:
package org.dotit.desktop;
* This interface denotes something that can own the focus
interface IDOTFocusOwner {
    boolean isFocusOwner();
    void setFocusOwner(boolean focus owner)
package org.dotit.desktop;
public class DOTComponent extends BlaBla implements IDOTFocusOwner {
    public final boolean isFocusOwner() { // ... }
    final void setFocusOwner(boolean focusOwner) { //...}
}You understand that I wouldn't leave "setFocusOwner" accessible outsite the package, and I would still want the methods do be defined in an interface, so that
the pseudo-focus manager that I'm implementing woul work with the interface, not the concrete class. I really don't understand their decision...seems that I have to structure my code somehow else.