User-agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
Hi Boris,
Thanks...I got the virgo nano milestone...very cool!
I noticed, however, that virgo nano currently does *not* include the
httpclient (3.1.0)-based filetransfer provider....which means that
the JRE httpconnection class is used for http/https p2
filetransfer. Not a tragedy, but it might be better to use the
apache httpclient-based file transfer for p2 support, as through a
lot of usage (with Eclipse), we've found the httpclient-based
provider to be more reliable.
Also...it would be better for our consumers (i.e. ECF remote service
folks that may want to use Virgo Nano and OSGi remote services
together) for Nano to include the httpclient provider, because a
couple of our remote services bundles and examples depend upon the
apache httpclient implementation.
The httpclient-based provider uses these three apache bundles...from
Orbit:
I think I'm also going to create and build a new ECF feature that
includes just these Orbit and ECF provider bundles...so that short
of having this in Nano, it will be easy to install. But I think it
would be useful for Virgo to consider adding these to nano...so it
and consumers can also benefit from the more reliable (and
performant) http/https transport impl.
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
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.