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.
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.
Currently we are using M03 and I saw in bug367794 that the update of the httpcleint and ECF in p2 will happen in M05.
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.
Tom
<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.
Tom
[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.
Thanks,
Scott
On 1/3/2012 9:19 PM, Scott Lewis wrote:
On 1/3/2012 9:03 PM, Scott Lewis wrote:
Hi Boris,
<stuff deleted>
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
"org.apache.commons.httpclient_3.1.0.v201012070820 [100]" could
not be resolved. Reason: Missing
Constraint: Bundle-RequiredExecutionEnvironment:
CDC-1.0/Foundation-1.0,J2SE-1.2
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.
Thanks,
Scott
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.
Thanks,
Scott
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.
Ok...thanks...I will do this. Sorry I haven't been
keeping up on all the Virgo Nano work...sounds great.
Is there a distribution available? If so...could you
point me in the right direction?
Thanks much,
Scott
On 12/29/2011 5:59 AM, Borislav Kapukaranov wrote:
Hey Scott,
Just tested installing ECF's remote
services on Virgo Nano and, as expected, it
went quite smoothly. The bundles got installed
fine.
If you'd like you can play with Virgo Nano
and the p2 commands to see if there are any
problems with the remote services lurking
around.
On 9/23/2011 1:02 AM, Kapukaranov,
Borislav wrote:
Hey
Scott,
As
of 3.5 equinox.common should
come out of the box with Virgo
as p2 has dependency to it
too.
You’ll
notice the bug
doesn’t provide much content –
that will change once I push
the baseline of the p2
integration and build from
then on for the remaining
features.
I
have the integration prepared
locally and it’s looking good,
e.g. the startup time on
Windows was decreased more
than twice… but I’m waiting on
two p2 enhancements [1][2] to
get resolved. Without them the
code won’t be building and
working properly.
In
the end if it turns out these
are taking a lot of time to
resolve we’ll just update EBR
with the working versions
until an official build is
ready and start producing 3.5
alphas.
Do
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 [1].
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 Services Target
Components'. Here [2] is a detailed
description of adding this feature to
one's target platform.
Also see [3] for a 'getting started'
tutorial (with examples, etc).
In a previous note, Lorie referenced
this wiki page [4] (thanks Lorie). The
one thing that I wanted to add was that
I think that much of what's described on
this page [4] is now actually
*unnecessary*...due to changes for ECF's
implementation of the Remote Service
Admin spec. This wiki page...although
still valid/supported, I
believe...requires more programming than
is now strictly necessary. I will try
to update it and simplify it when I can.