Lack of "export dynamic" requires to export everything for existing frameworks

[Sander Mak]

On 03 Oct 2016, at 13:30, Peter Levart <peter.levart at gmail.com<mailto:peter.levart at gmail.com>> wrote:

Use qualified exports?

Which circles back to the discussion that you don't necessarily know at compile-time which JPA/DI/whatever implementation you're targeting with the module in a Java EE context. Nor would you want to commit to one if you can program to a standard API like JPA/CDI.

In this case, we could explicitly tie the application modules to Spring by doing a qualified export, and I agree that's better than the wholesale exports private. I think Paul's point is that dynamic export seemed like a solution in the sweetspot for these types of (common) DI/ORM-based applications. It's sad this had to go with new #AwkwardEncapsulation/#ReflectiveAccessToNonExportedTypes proposal.


Sander