Have you been running with DS debugging on in Equinox? Put the
following on your VM args
-Dequinox.ds.print=true
This dumps all manner of very useful information.
Also, you might like the "ls" and "comp" console commands. Run with -
console and use those to explore your components.
Jeff
On 4-Sep-09, at 6:51 AM, Heiko Waldschmidt wrote:
Thanks for your help.
The Equinox-Console show only one Bundle - Bundle-SymbolicName:
the.name;singleton=true doesn't solve the problem. We will try to
get our Bundles running with Felix to get a better Idea what's the
reason of our problem. Maybe we get some more Information when we
use Felix.
Felix Meschberger <[email protected]> 09/04/09 10:40 >>>
Hi,
Heiko Waldschmidt schrieb:
New Day, new Ideas about my Problem. The framework starts more than
one
instance of my component ... this is the real cause - so
synchronization
couldn't work.
What's the state of the art way to get a singleton component?
Hmm, the SCR does not by itself create multiple instances of the same
component -- unless the component is created due to factory
configuration instances being created and configured. [ or the
component
is a component factory and some code calls
ComponentFactory.newInstance(), but this is probably not the case
here ].
The only other explanation I have is, that your bundle is installed
multiple times, which is perfectly possible. To prevent this set the
singleton parameter on the Bundle-SymbolicName header:
Bundle-SymbolicName: the.name;singleton=true
Regards
Felix
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev