Re: Java Project API/SPI

Jan Pokorsky wrote:
> I've been inspired by 
> http://openide.netbeans.org/tutorial/api-design.html document that 
> suggests to separate api for clients from support api and that clarifies 
> reasons. ProjectPath and JavaProject seem to me as good candidates.
> 
As I talked offline with several people, the approach is greatly 
beneficial if the API layer adds some value (e.g. brings 
synchronization, provides wrappers, accessors, helpers) on top of more 
narrow SPI interface.
Functionally the API-directly-subclassed and API/SPI approaches are 
equivalent; if you feel the split pattern is appropriate, why not.

-Svata