Re: OSGi-Bundles Distribution, generating the config.ini

2009-06-14 Thread Stuart McCulloch
2009/6/12 itripl itriple...@trash-mail.com well, that do not sound like the best way. I heard there is a way to do it with ant-contrib, but at the moment, I do not have the time to find out how. Maybe I can try it in a few weeks. When it does not work, I'm going to try to create a maven

Re: OSGi services as extension point mechanism

2009-06-14 Thread Dmitry Skavish
Thanks Neil! I see the issues now. Basically all the problems in that particular eclipse implementation, not in the idea of extension points. BTW which would you go with DS or iPOJO to implement plugins? On Fri, Jun 12, 2009 at 5:27 PM, Neil Bartlett njbartl...@gmail.com wrote: Hi Dmitry,

What is the correct service import behavior?

2009-06-14 Thread Todor Boev
Hello, Seems I have been chewing on the service dynamics issue forever. Just as I though I got a workable concept about tracking and releasing services I stumble on a contradicting concept. The problem is this: According to my understanding it is not acceptable importer behavior to ever call

Re: What is the correct service import behavior?

2009-06-14 Thread Richard S. Hall
On 6/14/09 5:08 PM, Todor Boev wrote: Some say we should never call out from the bundle while holding a lock but I think we are safe if we use a dedicated private lock for every tracked service. In any case I can't think of any other way to be safe at all times. Lately however I have been

Re: What is the correct service import behavior?

2009-06-14 Thread Todor Boev
Richard S. Hall wrote: Yes. iPOJO is of the philosophy that service departures will likely lead to errors, so you are better off being prepared to catch them and fail gracefully, sort of like errors in distributed computing. Even if you hold a dedicated lock, there is no guarantee that

Re: What is the correct service import behavior?

2009-06-14 Thread Todor Boev
Todor Boev wrote: Richard S. Hall wrote: Yes. iPOJO is of the philosophy that service departures will likely lead to errors, so you are better off being prepared to catch them and fail gracefully, sort of like errors in distributed computing. Even if you hold a dedicated lock, there is no