I know I am pushing enRout (sometimes I get tired of myself) but I think it is easy to start with and currently the best documented site for OSGi. Having examples that extend the base in only one dimension, Camel this case, will allow to mix and match it with other examples. OSGi enRoute apps can be used in many other environments like Karaf etc.
And a bonus (or a negative for some) you get my full attention :-)
Kind regards,
Peter Kriens
> On 9 jun. 2016, at 19:34, Balázs Zsoldos <[email protected]> wrote:
>
> @Daniel: Thanks for the clarification! Google generates the diagrams based on
> the answers. I cannot add something from the other section to this diagram,
> only if I upload the data into an external Diagram drawing tool and edit it.
> Next time I will add Karaf shell to the selectable options (or if the next
> survey is created by the OSGi Alliance, they should ;-) ).
>
> Zsoldos Balázs
> Rendszertervező | Software architect
>
>
>
> +36 70 594 9234 <> | [email protected]
> <mailto:[email protected]>
>
> EverIT Kft.
> 1137 Budapest, Katona József utca 17. III. em. 2.
> http://www.everit.biz <http://www.everit.biz/> I [email protected]
> <mailto:[email protected]>
>
>
> Ezen üzenet és annak bármely csatolt anyaga bizalmas, jogi védelem alatt áll,
> a nyilvános közléstől védett. Az üzenetet kizárólag a címzett, illetve az
> általa meghatalmazottak használhatják fel. Ha Ön nem az üzenet címzettje, úgy
> kérjük, hogy telefonon, vagy e-mail-ben értesítse erről az üzenet küldőjét és
> törölje az üzenetet, valamint annak összes csatolt mellékletét a
> rendszeréből. Ha Ön nem az üzenet címzettje, abban az esetben tilos az
> üzenetet vagy annak bármely csatolt mellékletét lemásolnia, elmentenie, az
> üzenet tartalmát bárkivel közölnie vagy azzal visszaélnie.
>
>
>
> This message and any attachment are confidential and are legally privileged.
> It is intended solely for the use of the individual or entity to whom it is
> addressed and others authorised to receive it. If you are not the intended
> recipient, please telephone or email the sender and delete this message and
> any attachment from your system. Please note that any dissemination,
> distribution, copying or use of or reliance upon the information contained in
> and transmitted with this e-mail by or to anyone other than the recipient
> designated above by the sender is unauthorised and strictly prohibited.
>
>
> On Thu, Jun 9, 2016 at 11:44 AM, Daniel McGreal <[email protected]
> <mailto:[email protected]>> wrote:
> That was me, and yes, that’s the correct interpretation - the feedback as
> several other contributors*.
>
> We don’t like to take the implied responsibility for maintaining jars we
> repackage ourselves with OSGi MANIFEST.MF headers for a variety of reasons.
> Luckily the situation is getting better, based on my experience.
> Generation tools are better, more convenient and therefore more prevalent
> (thanks bnd-maven-plugin).
> OSGi headers are cropping up from source more and more regularly (I’d love to
> see another scan of central to see how many jars supply them, broken down by
> popularity).
> ServiceMix provides distributions, though they sometimes seemingly haven’t
> been tested.
> Karaf wrap means things frequently just work at deployment time
>
> Best, Dan.
>
> * Balazs, I’d meekly suggest grouping the ‘other’ responses and including
> into the graphs where significant. For example, Karaf shell clearly deserves
> a place if the extra responses were grouped, as does Vaadin for UIs, etc.
>
>> On 8 Jun 2016, at 20:53, Balázs Zsoldos <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> My guess is that OSGi metadata here mean the OSGi MANIFEST headers and the
>> sentence mean something like the following: Lot's of technologies do not
>> have the OSGi MANIFEST headers in their jars, but thanks to ServiceMix the
>> situation is getting better (as ServiceMix re-packages many popular jars)
>
>
> _______________________________________________
> OSGi Developer Mail List
> [email protected] <mailto:[email protected]>
> https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
