I’ve been looking at “ports & adapters” examples on GitHub this morning … does anybody have one where all interfaces/classes are NOT public?

@simonbrown in Java they have to be, because *something else* is responsible for composing app from domain, adaptors and technical libs

@natpryce not necessarily … Spring will instantiate package-protected classes, for example /cc @olivergierke

@simonbrown it does so by calling setAccessible(true), thereby violating module boundaries.

@natpryce all types being public means that ports & adapters is really no different from a good layered architecture

@simonbrown in a layered architecture, static and dynamic relationships are (usually) the same. In P&A, they are different