OSGi enRoute has only one goal: simplify getting started using OSGi as it was
intended.
Much of the work went into creating the tooling that was missing to do it the
OSGi way. This work was mainly done in bnd and Bndtools. It was never the
intention to compete with Karaf, Aries, Equinox, Apache Felix, Amdatu,
Knopflerfish etc. The beauty of OSGi is that is a component system. Once you
got a simple version running you can easily extend it with more complex
components.
Since it is important to show a web app today OSGi enRoute added missing
components that were not available in the ‘OSGi way’ service. It therefore
defined their API and provided a simple provider. All these services are up for
specifications in the OSGi specification process. See the RFPs and RFCs on
Github. Several have progressed quite far and will likely replace the OSGi
enRoute services.
The goal is to make this set of specific OSGi enRoute bundles empty. This is
visible in the distro of OSGi enRoute. The distro is a shining example of OSGi.
It consists of bundles from all popular open source projects.
For an overview of OSGi services see the OSGi Compendium. All the information
you’re looking for is in there.
Kind regards,
Peter Kriens
> On 7 Dec 2016, at 20:53, Leschke, Scott <slesc...@medline.com> wrote:
>
> Much of what you have written below I’ve seen, but some of it, specifically
>
> With OSGi enRoute, a developer can make a single-page web OSGi application in
> just minutes. From there, it is easy to extend with the extensive number of
> OSGi open source and commercials components that exist.”
> (https://www.osgi.org/osgi-enroute-2-0-provides-maven-based-quick-start-to-osgi/
>
> <https://www.osgi.org/osgi-enroute-2-0-provides-maven-based-quick-start-to-osgi/>)
>
> I have not seen, probably since I’ve only looked at some of the content in
> the base tutorial so far. I believe you’re correct in that I’m confusing this
> with the work group specifications. I rather assumed this work has come out
> of the OSGi Alliance.
>
> From what I had previously read though, I mostly gathered that Enroute was
> intended to provide a consistent (web) “Application” model for OSGi but it
> struck me that many of the new services (osgi.enroute.*) listed in the
> Enroute service catalog seemed like they might just as well belong elsewhere
> so I started wondering about overlap with those other specs, hence my
> question about the distinction and rationale. I didn’t really feel I should
> need to do an entire tutorial to get clarity on the WHY.
>
> As for Bndtools, I’ve used it for some time but as far as I could tell, it’s
> really just an Eclipse plugin for doing OSGi development that was adopted for
> Enroute and is gathering specific Enroute support as a result, although what
> exactly that means at the moment I’m not exactly sure.
>
> Anyway, thank you for your response. I have another, somewhat related
> question though. Is there a page out there that shows ALL the available
> services in OSGi, their current version and a link to the latest version of
> the spec and the associated Javadoc? Similar to the Enroute service catalog
> but more complete I guess.
>
> Regards,
>
> Scott
>
> From: osgi-dev-boun...@mail.osgi.org [mailto:osgi-dev-boun...@mail.osgi.org]
> On Behalf Of Mike Francis
> Sent: Wednesday, December 07, 2016 9:55 AM
> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org>
> Subject: Re: [osgi-dev] Enroute
>
> Scott
>
> enRoute is intended to be a way for someone new to OSGi to quickly get
> started and use it. From the latest press release about enRoute:
> "OSGi enRoute is an OSGi Release 6 development environment that includes a
> complete tool chain based on Eclipse, Bndtools and either Gradle or Maven.
> OSGi enRoute also provides tutorials, examples, and application notes at
> http://enroute.osgi.org <http://enroute.osgi.org/>. With OSGi enRoute, a
> developer can make a single-page web OSGi application in just minutes. From
> there, it is easy to extend with the extensive number of OSGi open source and
> commercials components that exist.”
> (https://www.osgi.org/osgi-enroute-2-0-provides-maven-based-quick-start-to-osgi/
>
> <https://www.osgi.org/osgi-enroute-2-0-provides-maven-based-quick-start-to-osgi/>)
>
> In terms of its relation to other profiles I think you may be getting
> confused with the OSGi Alliance work groups and specifications. There are
> several work groups namely; CPEG (Core Platform Expert Group), EEG
> (Enterprise Expert Group), REG (Residential Expert Group) and IoTEG (IoT
> Expert Group). enRoute may or may not use some of the different
> specifications from these and it has also generated some potential
> requirements for new specifications.
>
> enRoute uses Bndtools, but Bndtools is a standalone open source project that
> provides a plugin for the Eclipse IDE to make it easier to develop OSGi
> software. If you have specific Bndtools questions I am sure the people on the
> Bndtools mail list will be pleased to help. This is the right place for
> enRoute questions though.
>
> To get your hands on enRoute and to start seeing what it provides the Quick
> Start tutorial should help (http://enroute.osgi.org/qs/050-start.html
> <http://enroute.osgi.org/qs/050-start.html>).
>
> Hope this helps.
>
> Regards
> Mike
>
> On 6 Dec 2016, at 20:29, Leschke, Scott <slesc...@medline.com
> <mailto:slesc...@medline.com>> wrote:
>
> I’ve started looking at Enroute and I’m a bit confused as to how it is
> distinguished from some of the other profiles that exist, say Enterprise or
> Residential? There’s talk of tooling and naming conventions and the like but
> it would seem to me that bndtools is general purpose OSGi and it’s not clear
> from what I’ve looked at online how exactly the naming conventions (.api,
> .provider, etc.) are enforced and what exactly they buy you.
>
> I have to admit I haven’t sat through a full tutorial yet because I was just
> kind of trying to get clarity on what exactly it is intended to buy you. I
> also expected to see an osgi.enroute repo in bndtools Repository view (under
> Bndtools Hub) but there is none so I’m not sure how to even get access to
> that profile.
>
> Color me mildly confused.
>
> Scott
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
