Hi Jerome,
In relation to Issue 80, though not sure if you want it reopened.
I've just got to the point with one of our projects where we are going to
use the Client inside of Eclipse. I tried just dropping org.restlet,
com.noelios.restlet and com.noelios.restlet.ext.net into the plugins
folder and they were discovered nicely. I made a plugin and added these as
dependancies.
When I tried to talk to the server I got the following:
org.restlet.spi.Factory getInstance
SEVERE: Unable to register the Restlet API implementation. Please check
that the JAR file is in your classpath.
So I tracked down the buddy-load info and rebuilt those three jars adding
Eclipse-BuddyPolicy: registered
to MANIFEST.MF of org.restlet
and Added:
Eclipse-RegisterBuddy: org.restlet
to MANIFEST.MF of com.noelios.restlet
When I ran the tests again, I was further along (the buddy loading allowed
com.noelios.restlet to be found by org.restlet, and I got the following
com.noelios.restlet.impl.Factory createHelper
WARNING: No available client connector supports the required protocols:
[HTTP]
Though I'd try pushing my luck a bit more and added Eclipse-BuddyPolcy to
com.noelios as well.
Then tried various combinations of Eclipse-RegisterBuddy for
com.noelios.restlet.ext.net but was not able to get it past this point
using the buddy system.
In the end I moved the code from com.noelios.restlet.ext.net into
com.noelios.restlet, and also added the line
com.noelios.restlet.ext.net.HttpClientHelper # HTTP, HTTPS
into com.noelios.restlet.impl.ClientHelper in com.noelios.restlet
And then it sprang to life and I was able to talk very nicely with the
server.
Wondering if anyone else has done this differently, or at all?
>From my point of viewing adding Eclipse-BuddyPolicy: registered to
org.restlet's MANIFEST.MF would be helpful.
Thanks.
AJ
