beehive-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Beehive Wiki] Update of "Controls/AssemblyAndBinding" by JeremiahJohnson
Date Thu, 12 May 2005 07:09:09 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Beehive Wiki" for change notification.

The following page has been changed by JeremiahJohnson:
http://wiki.apache.org/beehive/Controls/AssemblyAndBinding

The comment on the change is:
BEEHIVE-20

------------------------------------------------------------------------------
  }}}
  
  External configuration of bindings is supported via a "controls binding file", an optional,
user-authored, application scoped properties file that contains:
-  * bindings between C''''''ontrolBean/interface types and control implementation types.
 Each binding applies to all usages of the C''''''ontrolBean/interface type within that app.
+  * bindings between C''''''ontrolBean types and control implementation types.  Each binding
applies to all usages of the C''''''ontrolBean type within that app.
   
- Example controls binding file (e.g. {{{MyApp.controls.properties}}})
+ Example controls binding file ({{{controlbindings.properties}}})
  {{{
  org.acme.controls.FooBean=org.acme.controls.FooSimulationImpl
  com.bea.controls.DailyTimerBean=org.acme.controls.CustomTimerImpl
  }}}
+ 
+ The external configuration file should be in the classpath as controlbindings.properties.
 If you are building a Web application that uses Controls, then you would put a controlbindings.properties
file in WEB-INF/classes to take advantage of external binding.  If you are building a jar
with Controls in it that requires external binding, then controlbindings.properties would
be in the root of the jar.
  
  {{{
  REVIEW: Do we need finer granularity over binding configuration?

Mime
View raw message