about access modifiers (abstract and protected)

[Satyanvesh]

The combination of access modifiers such as abstract and protected are invalid combinations. If invalid please explain...

Please answer ASAP.


Thanks & Regards
M.Satyanvesh

[Mr.777]

Class can only be public or default.
And instance methods can be abstract and protected though. But you must need to implement this protected method in the very next concrete class(non abstract) or they will get private and will not be seen by any other hierarchy. So, this combination is valid.

[snowguy13]

Class can only be public or default.

Wait... I thought a class could be declared abstract, too. I also thought that if a class contained an abstract method, it must be declared abstract. Am I thinking of the wrong idea?

[Mr.777]

Wait... I thought a class could be declared abstract, too. I also thought that if a class contained an abstract method, it must be declared abstract. Am I thinking of the wrong idea?

There is the difference between access and non-access modifiers. A class can only have public or default access modifier while abstract, final, native etc are non access modifiers. So, yes a class can be declared abstract too.

I also thought that if a class contained an abstract method, it must be declared abstract

I guess these things are like to known by any java developer, a class having an abstract instance method is of course abstract class.

[snowguy13]

Ah, okay. Thank you.

Is "protected" an access modifier, or is it categorized as a non-access modifier?

[Tjstretch]

protected is an access modifier, because it modifies how the method/variable can be accessed. abstract is not a access modifier, because it doesn't affect access:
Controlling Access to Members of a Class (The Java™ Tutorials > Learning the Java Language > Classes and Objects)

[Mr.777]

Ah, okay. Thank you.

Is "protected" an access modifier, or is it categorized as a non-access modifier?

Only public, private and protected keywords are access modifiers while there are four different access levels including three keywords and default access level.

[snowguy13]

Hmm... I think it's a little bit odd that "protected" allows for more access than default!

But thanks both of you for the help!

[Mr.777]

Hmm... I think it's a little bit odd that "protected" allows for more access than default!

But thanks both of you for the help!

Well, both work same except when it comes to the different packages. protected works in different packages only if there is inheritance while default doesn't. And in remaining all cases both work exactly similar.

[copeg]

A class can only have public or default access modifier

This is not entirely true. What about the following?

public class OuterClass{
    public class PublicInnerClass{
 
    }
    private class PrivateInnerClass{
 
    }
 
    protected class ProtectedInnerClass{
 
    }
}

[vivekanand30]

"A class can only have public or default access modifier"

This statement is completely true don't mix Class with Inner Class both are completely different, It will confuse others.

As for as question is concerned

Class: this combination is not valid because protected can not be applied to Class(Not inner class) at all.

For methods there is no problem with this combination.

For Inner class again this is not a problem.
Below link could help you in access and non access.

Java Access Modifier
Java Non Access Modifier

A regular inner class just like member of the outer class, like instance variable or methods. So all the modifiers that apply to these will be applied to inner class too like
final, abstract, public, ..

[copeg]

...don't mix Class with Inner Class both are completely different, It will confuse others.

Fair enough...

[Mr.777]

This is not entirely true. What about the following?

public class OuterClass{
    public class PublicInnerClass{
 
    }
    private class PrivateInnerClass{
 
    }
 
    protected class ProtectedInnerClass{
 
    }
}

Well, i was supposed to talk about non-nested or non-inner classes. Well, thanks copeg anyways for pointing this out as well. Now, Any non-nested or non-inner class can have only public or default access. This seems fine now.