-- Original Message
> From: Christian Schneider
> Sent: Thursday, December 8, 2016 09:20 PM
> To: OSGi Developer Mail List
> Subject: Re: [osgi-dev] Strange issue with enRoute and Aries SPI Fly.
>
> I think the really problematic thing in Aries-spi is the client side.
--- Original Message
> From: Christian Schneider
> Sent: Thursday, December 8, 2016 09:20 PM
> To: OSGi Developer Mail List
> Subject: Re: [osgi-dev] Strange issue with enRoute and Aries SPI Fly.
>
> I think the really problematic thing in Aries-spi is the client side.
chats.
Original Message
From: Christian Schneider
Sent: Thursday, December 8, 2016 09:20 PM
To: OSGi Developer Mail List
Subject: Re: [osgi-dev] Strange issue with enRoute and Aries SPI Fly.
I think the really problematic thing in Aries-spi is the client side.
On the server side I
I think the really problematic thing in Aries-spi is the client side.
On the server side I think it makes sense to look into the bundles and
provide the ServiceLoader services as OSGi services.
On the client side it only works if Aries-spi does the weaving early
enough. So I wonder if in many
Runtime weaving is always one of the worst programming hacks in existence, I
would avoid it like the plague at all costs. It looks so attractive but it
causes so much unexpected pain.
However, you probably can’t. So I guess the like problem is that your UI code
gets loaded before the weaver is
Hi Peter,
Yes, I also assume I am running the application without security. I have
tested this two ways, one by running the enRoute application directly
within Eclipse just as explained in the enRoute tutorials, and also by
exporting the enRoute application as a stand alone executable jar file. In
Since the system is all started up when you press play or use the gogo command
this does not look like a start ordering problem. Nor is it a R/C problem
because all is satisfied.
The path from Gogo must therefore follow a different trajectory. The best way
to find these things out is to single
@BJ Hargrave,
Yes, I just tested rearranging the items listed in -runbundles to make sure
the ones that should be loaded first are. The problem remains.
@Raymond Auge,
I'm having a hard time understanding your response. I think I generally
understand what you're saying, but I don't know what to
Properly configuring the SPI-Fly integration should result in a set of
requirement and capabilities on the target bundles causing them to have a
resolution time requirement which should force the weaving to affect them
in the correct order.
For instance, if you have API bundle X that requires bund
I am not aware of any support in -runbundles to set start levels for bundle. But the bnd launcher should start the bundle in the order they are specified on the -runbundles instruction. Did you try putting those bundles first that need to be started first?
--BJ HargraveSenior Technical Staff Memb
10 matches
Mail list logo
