Why is composition often preferred over inheritance in Java?

Composition improves changeability when variation occurs along multiple independent axes. A notification service can combine channel, retry, formatting, and recipient-selection policies without creating a subclass for every combination. Inheritance may still be the cleaner answer for a deliberately designed template with stable protected extension points or a closed domain hierarchy. I choose based on behavioral ownership and expected change, then keep the abstraction count proportional to the problem.