While I've not used JNA, I agree that wrapping the native library call in
a POJO/proxy that can be the DS component's implementation class would
work well. Good idea Michael.
From:
Michael Mangeng m...@vis.at
To:
Equinox development mailing list equinox-dev@eclipse.org
Date:
11/04/2010 08:42
Declarative Services (DS) is part of the OSGi specification. The
specification has been implemented by Eclipse's Equinox project. The DS
specification is typically implemented as one or more bundles, separately
from the core OSGi framework, which is why it appears to be an
Eclipse/Equinox
Kane
However, the implementation of equinox's ds indeed do the enabling
operation in a work thread.
This is how the OSGi spec requires the enableComponent method to behave:
112.5.1 Enabled
...
The enableComponent and disableComponent methods must return after
changing the enabled state of the
To load a bundle programmatically, use the BundleContext APIs:
public Bundle installBundle(String);
public Bundle installBundle(String, InputStream);
Both APIs return a Bundle object, which you'll want to hold onto if you
wish to be able to stop it at some time, but this is not absolutely
Hi Chris
I would suggest installing the Equinox log service bundle
org.eclipse.equinox.log. The SCR will log exceptions such as these to the
LogService, if available. Since the LogService is purely a message-sink,
you'll either have to add a LogListener to the LogReaderService to dump
log
+1
Sounds good, Jeff.
Simon
Jeff McAffer [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
03/27/2008 01:04 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
'Equinox development mailing list' equinox-dev@eclipse.org
cc
Subject
RE: [equinox-dev] Incubator
+1 for Patrick's proposal.
Patrick Dempsey [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
09/26/2007 03:44 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
Equinox development mailing list equinox-dev@eclipse.org
cc
Subject
[equinox-dev] Moving Service
