Open mkarg opened 2 years ago
I feel more comfortable letting the impl choose to support non-public constructors. We may say it is non-portable between impls.
So we could say: A portable application MUST have a public constructor. A compliant implementation MAY support non-public constructors in addition.
We should adopt the CDI rules assuming we turn Application subclasses into proper beans.
Apparently some compliant implementations allow non-public Application constructors, while others do not. To ensure that any custom Application implementation ist at-most portable, the JAX-RS specification should unambiguously say that Applications must have a public constructor.