-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Not to beat on the same drum too long, but this is the kind of task for which
Apache Karaf feature descriptors do really well, because of their dynamic
nature. (As opposed to the more-or-less build-time nature of the Sling Launcher
system.) For example, if you load up some Stanbol components (with or without
the Web presence) and then realize that you want an additional component as
well, you can just load it into a running instance, provided the OSGi
dependency metadata is satisfied (and Karaf is helpful in making sure that
happens).
I realize that the original question was more to the point of offering a
deployable package all at once, but the Karaf system works just as well for
that, and the ability to have the container manage transitive dependencies
between components ("features", e.g. ContentHub or CMSAdapter) at a higher
level than bundles is quite nice, too.
It's clearly much too late to worry about offering this kind of deployment for
the forthcoming release, but I'll be glad to work on it for the next. My recent
experiment managed to get Stanbol (full) working quite happily in Karaf, so it
would be a question of integrating into the build system. Lots of Maven mojo.
{grin}
- ---
A. Soroka
Software & Systems Engineering :: Online Library Environment
the University of Virginia Library
On Apr 2, 2012, at 8:21 AM, Olivier Grisel wrote:
> Le 2 avril 2012 14:13, seralf <[email protected]> a écrit :
>> what about creating a sort of reusable simple "wrapper", in order to have
>> the possibility of use the components as a library inside other apps?
>> (without the need of starting the webapp). (just an idea)
>
> Some jars of stanbol can be used as regular java library, though most
> components need configuration that comes from the OSGi runtime. You
> can use felix to create such a runtime:
>
>
> https://felix.apache.org/site/apache-felix-framework-launching-and-embedding.html
>
>> Or is this yet possible creating such a custom launcher?
>
> Yes offcourse: the launchers are already quite modular, juste take a
> look at the "stable" and "full" launchers for instance:
>
> https://svn.apache.org/repos/asf/incubator/stanbol/trunk/launchers/stable/
> https://svn.apache.org/repos/asf/incubator/stanbol/trunk/launchers/full/
>
> You can copy the stable launcher as a start, and if you need
> additional components look at how they are configured in the full
> launcher to add them to your custom launcher.
>
> --
> Olivier
> http://twitter.com/ogrisel - http://github.com/ogrisel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJPear8AAoJEATpPYSyaoIkCvkIALW5jBG8of1Y73gdcW9cELmP
rOf62ds203yzMh7ot/9lfSNAyvQrYF6VGqoIYQ6u8ufgpZ5hXwjf8Bv6c58KE2nd
CxCCqmEshepdc6XVOpcB78pTzJBKBEnTuh83Ha9aZqDjlsPXuYS0wzgXTfAmJDoL
aL8fykf6NqrQEHRCWDYTbPnFOcCHgy/DNUShg/aDwopdUJL1g5i2V7sT9nWFNduQ
HWU4s3mjZiGh7aJIGa2LqzPgep3pAwSeHJPeI2lNHB+FCxCIwd2jjYymsp8KWQ9x
RGRQ47/ujAmj/D8qMOtSC6PE8DKo9p+Ipp1VnfySrDI513uWRj4ZKShuz2KXj0g=
=pj/h
-----END PGP SIGNATURE-----
