hivemind-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta HiveMind Wiki] New: PrivatesProposal
Date Mon, 26 Apr 2004 15:37:55 GMT
   Date: 2004-04-26T08:37:55
   Editor: HowardLewisShip <>
   Wiki: Jakarta HiveMind Wiki
   Page: PrivatesProposal

   no comment

New Page:

= Problem Description =

HowardLewisShip, Apr 26 2004, 1.0-alpha-4

In many cases, a particular module will include a number of services and configurations that
are internal to that module. Whether for concerns about instability in an API, minimizing
knowledge needed by users of a module, or some type of security concern, it makes sense that
(sometimes) services and configuration points be visible only within a specific module.

= Proposed Solution =

Add a {{{private}}} attribute to <configuration-point> and <service-point>.  It
would default to false, but could be set to true. 

There would need to be some number of API changes to faciliate this as well.

= Discussion =

At the risk of violating ["YAGNI"], perhaps better scoping rules are needed.  That is, something
reminiscent of Java's protected modified, where a extension point would be visible within
sub-modules.  But what defines a sub-module?  A module which has the current (exporting) module's
id as a prefix?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message