Packages listed in "uses" directives for export packages are exposed in
some way by those exported packages (e.g., a method return value or
method parameter types). If you see a package listed in "uses" then it
will either be imported by your bundle or exported by it. The framework
uses this information to make sure that clients of your exported
packages are wired to the same packages your exported package uses, if
necessary.
-> richard
On 5/14/09 3:03 PM, Patrick Forhan wrote:
These are automatically created by bnd, as are the SDK headers. The export
headers of the sdk look a bit different. BND does not explicitly mention
these packages, but wraps them in a 'uses:=' statement. Could this be the
problem?
If I understand it correctly the uses:= clauses are there to give
hints to the container. It basically indicates that you will have to
find those packages somewhere. I would try to instruct BND to export
*at least* all of the javafx.* packages. The configuration I use has
the following packages exported:
com.sun.gluegen.*,
!com.sun.javafx.runtime.adapter,
!com.sun.javafx.runtime.liveconnect,
!com.sun.javafx.runtime.provider,
!com.sun.javafx.api.*,
com.sun.javafx.*,
com.sun.embeddedswing,
com.sun.media.*,
com.sun.medialib.*,
com.sun.opengl.*,
com.sun.scenario.*,
com.sun.stylesheet.*,
javax.media.opengl.*,
org.jdesktop.layout,
!javafx.fxunit,
javafx.*,
I don't remember quite why the com.sun.* stuff is exported and not
private-packaged, but that is working for us at the moment.
Pat.
