Hello!
On 2017-04-10T08:58:45 +0100
Timothy Ward wrote:
> Hi,
>
> I’ve answered your specific questions about BundleTracker inline, so feel
> free to skip ahead, but it would also be perfectly possible to define a
> reusable DS component (as described in your initial email) without requiring
Hi,
I’ve answered your specific questions about BundleTracker inline, so feel free
to skip ahead, but it would also be perfectly possible to define a reusable DS
component (as described in your initial email) without requiring code from the
user.
If the core game library contains a suitably wr
On 2017-04-08T18:28:07 +
elias vasylenko wrote:
> This is absolutely possible!
>
> Look into the OSGi extender model for the general mechanisms.
>
Couple of small things with this:
Everything I've read suggests that I need to use the standard
BundleTracker:
https://osgi.org/javadoc/r6/
On 2017-04-08T18:28:07 +
elias vasylenko wrote:
> This is absolutely possible!
>
> Look into the OSGi extender model for the general mechanisms.
>
Interesting! I'll take a look at this. Thanks!
M
pgpgA3VI64gr_.pgp
Description: OpenPGP digital signature
__
This is absolutely possible!
Look into the OSGi extender model for the general mechanisms.
It sounds like you want to create an extender which registers services on
behalf of your resource bundles. Resource bundles only have to have a
manifest entry advertising that they wish to be processed by y
On 2017-04-08T18:07:59 +
list+org.o...@io7m.com wrote:
>
> ... and the editing tool would insert information in the OSGi manifest
> that would, when the bundle is loaded into the game, result in an
> implementation of the SoundThemeType API being created and registered
> as a service using the
Hello.
As I've previously explained, I'm developing a game and am using OSGi
as the foundation. We want to encourage third-party additions to the
game and are therefore publishing APIs and building the whole thing as
a plugin/service-based architecture from the beginning.
Some plugin bundles will
