2010/11/19 Robert Krüger krue...@lesspain.de:
I'm going through the (so far rather painful) process of trying to deploy my
OSGI app developed within Eclipse 3.6 in a standalone Equinox environment for
the first time.
The main problem is the runtime in PDE simulates the Eclipse
workbench,
Hey Robert,
I think we need some more information here. You should not have to mess with
the system packages settings etc. I've been using javax and org.xml etc for
years and have never had to do this. What Alex says may be required in cases
where you are going for internal/private JRE
Hi all,
the problem here is, that the java profile definitions contained in
the org.eclipse.osgi_x.y.jar define the javax.* packages as
bootdelegated packages, e.g.:
org.osgi.framework.bootdelegation = \
javax.*,\
org.ietf.jgss,\
org.omg.*,\
org.w3c.*,\
org.xml.*,\
sun.*,\
com.sun.*
First of all, thanks a million Alex, Jeff and Gerd!
The boot delegation option solved my immediate problem and I will probably take
a look at the approach Gerd suggested in the long run.
Cheers,
Robert
On 19.11.2010, at 15:40, Gerd Wütherich wrote:
Hi all,
the problem here is, that the
: |
|
---|
|Re: [equinox-dev] How to best simulate standalone Equinox deployment in
Eclipse
Hi Thomas,
of course you are right. We use the custom execution environment I mentioned
to partially include/exclude packages from an (endorsed) JDK, but the
excluded packages are replace by bundles that reside in our target platform.
We completely removed javax.* from bootdelegation (for the
