[iPojo] 1.8.0 migration trouble

Hi, Currently I am in trouble migrating from iPojo version 1.6.4 to iPojo 1.8.0. I am doing this migration in order to get all the evolutions and fixes. Unfortunately I discovered that there is a difference in the behavior of properties injection. With the version 1.6.4 I was using some lines of

RE: Getting a Bundle ClassLoader

Hi, You can declare the bundle that does not contain any Class as Fragment (say A) of another bundle (say B). The resources contained in the fragment A will be visible from the Classloader of B. Regards, /Etienne -Message d'origine- De : alasdair.notting...@gmail.com [mailto:alasdair.n

Re: iPojo - How can I force the factory to create an instance

Ok, thanks. for the immediate. It works. I have understood my trouble. The tags doesn't say anything when the component name provided is wrong. Do you think that its normal? For example: never complains Thanks, /Etienne -- View this message in context: http://www.nabble.com/iPojo

iPojo - How can I force the factory to create an instance

Hi, I am in trouble to figure out how I can force the factories of iPojo to create an instance of a component. In my case, I have a "manager" class that have an optional @Requires on an Array of plugins. My problem is that if nobody use my "manager", no instance of this manager is created. And i

Re: iPojo - How to create several instances of the same component installed in different versions

Hi, > Here is the issue: > When you/iPOJO call getServiceReferences the framework should returns > only "accessible" services. "Accessible" means that you (the bundle) > can access to the service object in term of class loading. So, it > generally means : must use the same service interface

Re: iPojo - How to create several instances of the same component installed in different versions

Hi, Thanks for the annotation support. I don't understand very well why you are speaking about using the "filter" parameter of the @Requires annotation. For me it's not clear if this filter is necessary in the Xml syntax case. If it's the case, I don't understand why it's mandatory. In Felix the

Re: iPojo - How to create several instances of the same component installed in different versions

Hi, Thanks for this new feature. http://www.nabble.com/file/p23639495/ipojo-component-testcase-metadata.tar.gz ipojo-component-testcase-metadata.tar.gz My first remark will be that I didn't use the Xml syntax of iPojo. Only annotations and the new version attribut is not available in the @Compo

iPojo - How to create several instances of the same component installed in different versions

Hi, I am trying to figure out how we can manage to run in Felix several versions of the same component that is using iPojo. iPojo use a component name to create component instances. My problem is that with the time some components will evolve and there version number will increase. The old vers

Re: iPojo - Whiteboard Pattern handler motivations

Thanks, I understand better the motivations. -- View this message in context: http://www.nabble.com/iPojo---Whiteboard-Pattern-handler-motivations-tp23410684p23411050.html Sent from the Apache Felix - Users mailing list archive at Nabble.com. --

iPojo - Whiteboard Pattern handler motivations

Hi, I am trying to figure out why the @WBP annotation exist, and what are the advantages compared to using the @Requires annotation. I failed to find some details regarding that point on the documentation. (http://felix.apache.org/site/white-board-pattern-handler.html) I managed to create the @