It's very hard for me to reproduce this problem, so I'm pretty sure I can't
generate a working test case...
Sorry about that...
Olivier
-Message d'origine-
De : Richard S. Hall [mailto:he...@ungoverned.org]
Envoyé : mercredi 13 juillet 2011 16:43
À : users@felix.apache.org
Objet : Re: N
If I understand correctly, we have to implement our own ConfigAdmin
PersistenceManager implementation to not store/load configs from file system,
but directly from our DB. Am I right?
And we just have to expose our implementation of this PersistenceManager OSGi
service and Felix will use our own
Hi,
What do you mean by "while the ipojo instance is being registered"?
How to be triggered when it is happening?
Is there a callback method that is always called when it is happening?
Thanks
Olivier
-Message d'origine-
De : Tribon Cheng [mailto:tribon1...@gmail.com]
Envoyé : lundi 9 ma
Hi all,
We faced a deadlock issue with iPojo 1.6.4 (and also reproduced with iPojo
1.8.0).
Here are the details of the context:
1) We have a first iPojo Component that we will call "PDP".
This Component is declared with the 3 iPojo annotations "Component",
"Instantiate" and "Provides".
2
users@felix.apache.org
Objet : Re: NoSuchElementException when uinstalling Bundle
On 2/14/11 5:45, Bigard Olivier wrote:
> Hi all,
>
> We are using Felix 3.0.2 with iPojo 1.6.4 and here is the exception we have
> sometimes when trying to uninstall a Bundle (
apache.org
Objet : Re: NoSuchElementException when uinstalling Bundle
On 2/14/11 5:45, Bigard Olivier wrote:
> Hi all,
>
> We are using Felix 3.0.2 with iPojo 1.6.4 and here is the exception we have
> sometimes when trying to uninstall a Bundle ("bundle.uninstall();"):
>
Hi all,
We are using Felix 3.0.2 with iPojo 1.6.4 and here is the exception we have
sometimes when trying to uninstall a Bundle ("bundle.uninstall();"):
java.util.NoSuchElementException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:796)
at java.util.Has
o:clement.escoff...@gmail.com]
Envoyé : vendredi 28 janvier 2011 17:28
À : Apache Felix - Users Mailing List
Objet : Re: iPojo inner class instrumentation
Hi,
Invalid Bundle Context means that the bundle is stopping or already
stopped, and so is not able to access the service registry anymore.
Invalid Bundle Context means that the bundle is stopping or already
stopped, and so is not able to access the service registry anymore. Is it
your case?
Regards,
Clement
On 28.01.11 17:11, "Bigard Olivier" wrote:
>Hi Clément,
>
>Sorry to answer so late, but we just test yo
strumentation
Hi,
I've tried to reproduce your scenario in:
http://svn.apache.org/viewvc?view=revision&revision=1045175
However, it works for me. I just remove C4 and directly call C3. Could you
highlight the differences ?
Regards,
Clement
On 13.12.10 16:07, "Bigard Olivier"
to disable 'proxy' on c2
@Requires(proxy=false)
C2 c2;
Regards,
Clement
On 13.12.10 15:43, "Bigard Olivier" wrote:
>Hi Clement,
>
>We are using iPojo Core 1.6.4 (with Annotations).
>We are also using the Maven plugin version 1.4.2. Maybe this version is
>too o
Escoffier [mailto:clement.escoff...@gmail.com]
Envoyé : lundi 13 décembre 2010 14:52
À : users@felix.apache.org
Objet : Re: iPojo inner class instrumentation
Hello,
On 13.12.10 11:41, "Bigard Olivier" wrote:
>Hello,
>
>
>
>We have an interrogation regarding iPojo instrumentati
Hello,
We have an interrogation regarding iPojo instrumentation. We read
somewhere in the forum that iPopo can instrument inner classes, but we
are facing a problem when using them in our project.
Here is our use case:
A first component C1 provides a service with a method "callMe()".
Anoth
Hi,
I'm trying to find a way to implement following need with Felix and
iPojo.
Imagine you have an iPojo instance of Bundle A calling an OSGi Service
provided by an iPojo instance of Bundle B.
Imagine this Bundle B iPojo instance is calling an OSGi Service provided
by an iPojo instance of
iPojo "requires.filters"
Hi,
On 08.11.2010, at 09:26, Bigard Olivier wrote:
> Hi,
>
> First, thank you for your answer.
>
> I totally agree with your point regarding the name convention.
> But what I propose is different. The idea is just to have an Array of
> key/val
lement.escoff...@gmail.com]
Envoyé : dimanche 7 novembre 2010 13:57
À : users@felix.apache.org
Objet : Re: iPojo "requires.filters"
Hi,
On 04.11.2010, at 12:55, Bigard Olivier wrote:
> Hi,
>
>
>
> I tried to dynamically update the < filter > value of a <
Hi,
I tried to dynamically update the < filter > value of a < @Requires >
annotation.
The problem is that I'm using ConfigAdmin service to create my instances
and, as Clement explained in the following thread, ConfigAdmin doesn't
support Dictionary class...
http://old.nabble.com/-iPOJO--Filte
ssage d'origine-
De : Clement Escoffier [mailto:clement.escoff...@gmail.com]
Envoyé : mercredi 13 octobre 2010 20:33
À : users@felix.apache.org
Objet : Re: Exception handling in iPojo annotations
Hello,
On 13.10.2010, at 17:06, Bigard Olivier wrote:
> Hi,
>
>
>
> Wh
Hi,
When using iPojo 1.6.4 with annotations, the method you implement can
throw Java exceptions like following:
@Validate
public void validate() throws Exception
{
throw new Exception("My Exception");
}
When executing this method, iPojo will
19 matches
Mail list logo