Thanksinadvance for the attention. It should be an easy fix, I
As for the new version of the httpclient, we got the "old"
http transport when we started consuming p2 and basically this
is what was included along with p2.
Hmmm. We've been including the httpclient provider to p2/Platform
for a couple of major Eclipse releases now (3.6, 3.7 at least), but
maybe it's not included in some (Equinox sdk?) distribution of p2.
It's definitely been in Eclipse for at least two years now.
My assumption is that when p2 starts bundling with the new
ECF version and httpclient we would automatically get these when
we update our p2 version to a newer milestone.
That should work just fine...as you indicate with bug below the
Equinox/p2 team is moving to using the latest release build (3.5.4)
of ECF filetransfer. But given what you say above, I'm not sure
what distro of p2/ECF filetransfer you are using to create nano...as
it seems that maybe whatever you are using doesn't by default
include the httpclient-based provider? I know that for Eclipse the
httpclient-based provider is included/used.
Currently we are using M03 and I saw in bug367794
that the update of the httpcleint and ECF in p2 will happen in
Right...it's actually happening right now (this week's integration
build) is my understanding.
So it will be in Eclipse...but if you are not using the Eclipse
distro of Equinox/p2/ecf filetransfer then you might not get it (I
don't control how/what's included in various Equinox distros).
I corresponded with Thomas Watson about this resolution
problem with httpclient 3.1 in virgo, and he said:
A bundle that expresses a Bundle-RequiredExcecutionEnvironment: J2SE-1.2
must be able to run on J2SE-1.4 and higher. I would like to understand
what issue you see when the bundle does not also list J2SE-1.4.
<I explained what I was seeing>
Hmmm, it is possible Virgo is using a custom java profile that does not
list J2SE-1.2 in the property org.osgi.framework.executionenvironment.
That would be a bug in Virgo, if that is the case.
[Scott] Should I open a bug for this against Virgo
nano?...as it seems that given this the Orbit folks are
not going to change the httpclient ee.
On 1/3/2012 9:19 PM, Scott Lewis wrote:
On 1/3/2012 9:03 PM, Scott
One thing that I noticed
while trying to install the httpclient 3.1 bundle
from Orbit with a new feature...the httpclient
bundle from Orbit wouldn't resolve:
org.osgi.framework.BundleException: The bundle
" could not be resolved. Reason: Missing
I've verified that if I add J2SE-1.4 to the set of
required execution environments for the
org.apache.commons.httpclient bundle, then it will
install in Virgo just fine. Unfortunately, this
bundle (httpclient 3.1.0) is currently maintained by
Orbit committers...not be me or the ECF project.
I've sent a note to the Orbit dev mailing list, to
find out if j2se 1.4 can be added to the httpclient
3.1.0 min ee.
Does this make sense to you? Does Virgo Nano not
provide these execution environments?
Anyway...hopefully we can jointly work these
things out. Please let me know what you think.
On 1/3/2012 9:28 AM, Borislav Kapukaranov wrote:
Sure, you can find it on
the Virgo milestones download page, under the
Virgo Nano name.
You can access telnet via "telnet localhost
2401", the p2 commands are available there.
On 9/23/2011 1:02 AM,
should come out
of the box with
Virgo as p2 has
dependency to it
notice the bug
much content –
that will change
once I push the
baseline of the
and build from
then on for the
and it’s looking
good, e.g. the
startup time on
than twice… but
I’m waiting on
enhancements  to get resolved. Without them the code won’t be
the end if it
turns out these
are taking a lot
of time to
just update EBR
with the working
build is ready
you have the
update site of
the ECF's remote
services? I’d be
happy to try it.
Sure. ECF's 3.5.2 release
repo . In this repo
there are a few
features...the one that is
of interest for this use
case (instead of Eclipse),
is entitled 'ECF Remote
Components'. Here  is
a detailed description of
adding this feature to
one's target platform.
Also see  for a
'getting started' tutorial
(with examples, etc).
In a previous note, Lorie
referenced this wiki page
 (thanks Lorie). The
one thing that I wanted to
add was that I think that
much of what's described
on this page  is now
changes for ECF's
implementation of the
Remote Service Admin
spec. This wiki
programming than is now
strictly necessary. I
will try to update it and
simplify it when I can.