Am 22.08.2011 um 17:26 schrieb Marshall Schor: > e2) The application could take a string "name" of the aggregate to run, and > then > "look it up" in the OSGi registry. This would require that some other process > "install" the aggregate into OSGi and Register it.
It would be so fancy if the looking up would work against a Maven repository (for non-osgi/non-pear components) or an Eclipse update site (for OSGI bundles). I understand m2eclipse does something similar in Eclipse 3.7 when it imports a new Maven project with yet unknown Maven plugins. It goes to the Eclipse marketplace and tries to locate m2eclipse plugins to support the Maven plugins used in the project's POM. Cheers, Richard -- ------------------------------------------------------------------- Richard Eckart de Castilho Technical Lead Ubiquitous Knowledge Processing Lab FB 20 Computer Science Department Technische Universität Darmstadt Hochschulstr. 10, D-64289 Darmstadt, Germany phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117 [email protected] www.ukp.tu-darmstadt.de Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de -------------------------------------------------------------------
