[osgi-dev] EclipseCon France 2018

2018-03-02 Thread Simon Chemouil via osgi-dev
the talks are selected. Regards, -- Simon Chemouil ___ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] FileSystemProvider for OSGi bundle

2017-05-17 Thread Simon Chemouil
Simon Spero a écrit le 18/05/2017 à 01:12 : > The reactive-streams API is provided by the nested interfaces in > jdk9s java.util.concurrent.Flow (Doug Lea original here > ). It's been

Re: [osgi-dev] Making sure some bundles are started first

2017-05-04 Thread Simon Chemouil
is available on GitHub[1] in ServiceWeavingManager#open() Hope this helps, Simon [1] https://github.com/primeval-io/aspecio Simon Chemouil a écrit le 02/11/2016 à 14:27 : > I thought about restarting bundles when I was first dealing with that > issue and judged it was a bit extreme, yet

Re: [osgi-dev] Determining the set of required bundles

2017-02-03 Thread Simon Chemouil
Hi, I'm sure others will give you a more detailed answer, but here's a quick pointer. list+org.o...@io7m.com a écrit le 03/02/2017 à 15:55 : > Is there a library out there that can do this kind of work for me? Yes, you seem to be describing exactly what the Resolver service does; it has an

Re: [osgi-dev] Making sure some bundles are started first

2016-11-02 Thread Simon Chemouil
I thought about restarting bundles when I was first dealing with that issue and judged it was a bit extreme, yet ended up with forcing an early start. Considering start level an optimization is a nice way to solve the problem. I will try to find some time to make the necessary adjustments to

Re: [osgi-dev] Help

2016-10-20 Thread Simon Chemouil
BJ Hargrave a écrit le 20/10/2016 15:56 : > Maybe we need an osgi-users list for more general help type questions > and osgi-dev can stay more focussed on spec related discussions? > > I could create the osgi-users list and intially subscribe everyone on > osgi-dev to it. Then people can

Re: [osgi-dev] Help

2016-10-20 Thread Simon Chemouil
Hi Peter, Peter Kriens a écrit le 20/10/2016 13:52 : > I did a quick check on the last messages on this list: [snip] > > So out of more than 60 messages, there were only 5 messages related > to OSGi enRoute. Are these your problem? Since I will spend much less > time on OSGi enRoute a new

Re: [osgi-dev] Help

2016-10-20 Thread Simon Chemouil
Resurrecting this old topic. It has been decided in the OSGi Alliance to move enRoute support here, but maybe it could be decided to move it elsewhere now? I'm interested in the osgi discussion / spec content, but the interest / noise ratio is decreasing rapidly, and it's only a few users of

Re: [osgi-dev] Promises 1.1 Draft

2016-10-12 Thread Simon Chemouil
Hi! > What you’ve described is how you would provide your own Promises > implementation (see also the Aries Promise > implementation: > https://github.com/apache/aries/tree/trunk/async/promise-api/src/main/java/org), > and could be what you choose to do. I would, however, consider > attempting

Re: [osgi-dev] Promises 1.1 Draft

2016-10-11 Thread Simon Chemouil
Hi Timothy, Thanks for your answer. Comments inlined. [snip] > occur if the provider of the promise is mis-coded, or simply if the > triggering event never occurs. Timing out is usually the right thing to > do in these situations, so adding a primitive for that to the Promise > was made a target

[osgi-dev] Promises 1.1 Draft

2016-10-11 Thread Simon Chemouil
Hi, I had a look at the recently published Compendium R7 draft. I noticed the Promise interface has, among other changes, two new methods: * public Promise timeout(long milliseconds) * public Promise delay(long milliseconds) (I somehow suppose these are also used by the new PushStream API) Is

Re: [osgi-dev] Waiting in deactivate/activate()?

2016-08-07 Thread Simon Chemouil
list+org.o...@io7m.com a écrit le 07/08/2016 22:36 : > The more I think about this, the less it seems like a DS issue and more > like something more fundamental instead. DS could help create write less code by exposing more functionality, but the general solution would remain the same. For

Re: [osgi-dev] Waiting in deactivate/activate()?

2016-08-07 Thread Simon Chemouil
Simon Chemouil a écrit le 07/08/2016 17:37 : >public void register(TCPServer tcpServer) { > > this.tcpServer = tcpServer; > > // blocking code. > reg = context.registerService(TCPServer.class, tcpServer, null); > > // this thread will potenti

Re: [osgi-dev] Waiting in deactivate/activate()?

2016-08-07 Thread Simon Chemouil
list+org.o...@io7m.com a écrit le 07/08/2016 14:01 : > Hello. Hi, > As a learning exercise, I've put together a very contrived example of a > "reverse" service (like an echo service, except that each returned line > comes back reversed). Mostly, I'm using it as a learning example of how > to

Re: [osgi-dev] OSGI++ / OSGI4COM

2011-03-29 Thread Simon Chemouil
Hi Philipp, At the company I work for have we have been looking for an OSGi-like C/C++ for some time and Celix is the only one that seems to be both open-source and actively developed (for some definition of active, but we talked to Alexander at the EclipseCon last week and he is still involved

Re: [osgi-dev] Classloader accessibility and ServiceTracker.open(true)

2011-02-21 Thread Simon Chemouil
Scott Lewis wrote: Are there any viable approaches other than this? e.g. can the wiring of the RSA (or TopologyManager) bundle be dynamically manipulated...to allow the RSA or TM itself to register the proxy service factory? I'm not sure this would work (someone else should confirm) or even

Service cleanup best practices (Was: [osgi-dev] What happens to class instances when bundle containing the class unloads)

2011-02-18 Thread Simon Chemouil
Hi there, I'm resurrecting an old thread that went relatively unnoticed (only one reply) but that has been bothering me when I thought back about it lately. The problem is described in the original message below, but in one word: I'm looking for best practices when it comes to cleaning after a