Karl,
Thank you for the fix. Yes, it (the maven snapshot) does seem to have
worked.
When is the next release of Felix? If it is soon, it might be better for
Tuscany to wait for the release rather than switch to using the snapshot
builds.
Thank you...
Regards,
Rajini
On 1/15/08, Karl Pauls
Thank you, Karl. That is very promising.
Thank you...
Regards,
Rajini
On 1/16/08, Karl Pauls [EMAIL PROTECTED] wrote:
Karl,
Thank you for the fix. Yes, it (the maven snapshot) does seem to have
worked.
Great :-)
When is the next release of Felix? If it is soon, it might be
Karl,
Thank you for the fix. Yes, it (the maven snapshot) does seem to have
worked.
Great :-)
When is the next release of Felix? If it is soon, it might be better for
Tuscany to wait for the release rather than switch to using the snapshot
builds.
Felix 1.0.2 will be out end of next
Hello,
I have a test case in Apache Tuscany which fails intermittently when run
along with a lot of other OSGi-based tests under Felix.
I have three bundles A, B and C with distinct packages contained inside
them.
BundleA exports PackageA.
BundleB imports PackageA.
I use the system
Strange.
Off the top of my head I can think of two ways for this to happen:
1. PackageA is actually available from more than one place.
2. Felix' service filtering test has a bug in it.
Perhaps you could add some debugging printlns to your code to determine
which class loaders are being
Richard,
I dont think this is the problem in the filtering test because I can see
from the logs that the class used by the service object is different from
the class used by the bundle when the lookup is done. I have a list of print
statements taken from a segment of code in Tuscany when the
Is it possible that the class has been loaded from the bundle before
this test by a different thread? It looks like we could have a
visibility issue because the classloader is created lazily outside of
a any synchronized block...
regards,
Karl
On Jan 15, 2008 9:07 PM, Rajini Sivaram [EMAIL
Karl,
Yes, I think it is possible that the class was loaded from the bundle on
another thread, because there is a bundle listener which does some
processing when the bundle moves to resolved state. Should I avoid
classloading in other threads, or is it something that can be fixed in
Felix?
Rajini,
I just commited a patch that should fix the visibility issue (if that
was the cause of your problems). Could you re-run your tests on the
current trunk and see whether that fixes the issue for you?
Alternatively, you can just use the deployed snapshot of the current
trunk from maven (in
