While I see the value of a launcher - I don't think that this is the
concern of Sling - we are the framework which should run in every OSGi
installation; so let's focus on the framework and leverage other efforts
like pax+runner, Karaf etc. instead of doing this stuff ourselves.
Just my 2c
On Thu, May 14, 2009 at 8:47 AM, Carsten Ziegeler cziege...@apache.org wrote:
...While I see the value of a launcher - I don't think that this is the
concern of Sling - we are the framework which should run in every OSGi
installation; so let's focus on the framework and leverage other efforts
On Wed, May 13, 2009 at 9:04 PM, Felix Meschberger fmesc...@gmail.com wrote:
Hi,
Bertrand Delacretaz schrieb:
I'm thinking of creating a generic launcher, using a text file
definition to load and start jars, allowing a Sling launcher to take
over and load and start bundles once a main class
Bertrand Delacretaz wrote:
On Thu, May 14, 2009 at 8:47 AM, Carsten Ziegeler cziege...@apache.org
wrote:
...While I see the value of a launcher - I don't think that this is the
concern of Sling - we are the framework which should run in every OSGi
installation; so let's focus on the
Hi,
I'm thinking of creating a generic launcher, using a text file
definition to load and start jars, allowing a Sling launcher to take
over and load and start bundles once a main class is started.
Here's a rough idea - I haven't looked at Karaf closely yet, there's
probably some overlap, but my
Hi,
On Wed, May 13, 2009 at 4:57 PM, Bertrand Delacretaz
bdelacre...@apache.org wrote:
Using a text file to define bundles makes it easy for people to
exchange configurations, as the text file fully defines the
application assembly, based on the bundles URLs and digests.
See below for a
Hi,
Bertrand Delacretaz schrieb:
I'm thinking of creating a generic launcher, using a text file
definition to load and start jars, allowing a Sling launcher to take
over and load and start bundles once a main class is started.
This sounds a lot like Tanuki Java Service Wrapper ...
Here's
