Lookup
From APIDesign
| Line 1: | Line 1: | ||
| - | [[Lookup]] is | + | [[Lookup]] is an acient library that aligns [[Injection|component injection]] with adaptable pattern. It is baded on long time [[JDK]] standard for registering instances of services in [[JAR]] files. it extends this area and allows ''local pools'' of objects that can be queries for certain capability. That bridges the classical [[Injection|injection]] pattern with local adaptable pattern. |
* See [http://hudson.apidesign.org/hudson/job/lookup/org.apidesign$lookup/javadoc/ javadoc] | * See [http://hudson.apidesign.org/hudson/job/lookup/org.apidesign$lookup/javadoc/ javadoc] | ||
The basic idea, in its [[ServiceLoader]] incarnation is that it is enough to compose an application from various [[JAR]] files and let these [[JAR]] files communicate. This is achieved by well-known location, ''META-INF/services/etc.'' that is read from all available libraries [[JAR]]s on the classpath. This simplifies deployment of the application. It is enough to make the right [[JAR]]s available in the system and all the pieces may start to work together by mutually discovering themselves. | The basic idea, in its [[ServiceLoader]] incarnation is that it is enough to compose an application from various [[JAR]] files and let these [[JAR]] files communicate. This is achieved by well-known location, ''META-INF/services/etc.'' that is read from all available libraries [[JAR]]s on the classpath. This simplifies deployment of the application. It is enough to make the right [[JAR]]s available in the system and all the pieces may start to work together by mutually discovering themselves. | ||
Revision as of 20:48, 20 April 2009
Lookup is an acient library that aligns component injection with adaptable pattern. It is baded on long time JDK standard for registering instances of services in JAR files. it extends this area and allows local pools of objects that can be queries for certain capability. That bridges the classical injection pattern with local adaptable pattern.
- See javadoc
The basic idea, in its ServiceLoader incarnation is that it is enough to compose an application from various JAR files and let these JAR files communicate. This is achieved by well-known location, META-INF/services/etc. that is read from all available libraries JARs on the classpath. This simplifies deployment of the application. It is enough to make the right JARs available in the system and all the pieces may start to work together by mutually discovering themselves.
Follow
