Great! I agree with this new direction.
Well, for now I will implement your requested feature.
> Hi Tal,
>
> In RF 3.0, we should really give more precise control regarding extensions
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=44
Hi Tal,
In RF 3.0, we should really give more precise control regarding extensions
usage for:
- connectors
- converters
- authenticators
The configuration of a Restlet component or application should be explicit
and fully available programmatically.
I'm even considering fully removing
Actually, it's a feature I would like to see with *all* Restlet extensions: it
would be nice for users to be able select which extensions they want to use,
rather than configure it solely via the classpath.
Possibly with Java properties? I can imagine every extension class having an
"enabled" p
Thanks Tal, this looks great. We might want to add parameters to
disable/enable the client/server connector from the extension as a second
step to allow mixing of several connector extensions.
I've added a note about this to the matching ticket:
https://github.com/restlet/restlet-framework-java/is
I went ahead and also added a Jetty 9 client connector:
https://github.com/tliron/restlet-jetty9
Note that if you add the Jar to your classpath, both the server and client
connectors will be activated.
--
http://restlet.tigris.org/ds/viewMessa
It looks good, thanks Tal!
Jerome
2013/11/9 Tal Liron
> Binaries and API documentation are now available via the GitHub project
> site.
>
> Enjoy!
>
> > https://github.com/tliron/restlet-jetty9
>
> --
>
> http://restlet.tigris.org/ds/viewMess
Binaries and API documentation are now available via the GitHub project site.
Enjoy!
> https://github.com/tliron/restlet-jetty9
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3068157
Excellent. If anyone has comments, here is the GitHub issue:
https://github.com/restlet/restlet-framework-java/issues/793
> That's fine Tal, whatever works best for you. Merging by hand won't be a
> big issue anyway.
>
> You might want to enter an issue in RF repo to let people discover this
> s
That's fine Tal, whatever works best for you. Merging by hand won't be a
big issue anyway.
You might want to enter an issue in RF repo to let people discover this
support and let us communicate over it.
Best regards,
Jerome
2013/11/7 Tal Liron
> Thanks, Jerome.
>
> I picked the Apache License
Thanks, Jerome.
I picked the Apache License 2.0, and am hosting it as a separate project. I'm
assigning joint copyright on it to Restlet S.A.S, per the contributor
agreement, so you are free to merge it should you ever wish to do so:
https://github.com/tliron/restlet-jetty9
Rather than a branc
I suggest that you create a new
/restlet-framework-java/master/incubator/org.restlet.ext.jetty9 extension
by copying then adapting the o.r.e.jetty extension.
You can always have you own branch in GitHub and then merge it back when
master becomes ready for RF 3.0 (Java 7), but from a licensing poin
So, I went ahead and created a Jetty 9 extension for Restlet 2.2:
https://github.com/tliron/restlet-jetty9
It's not much tested (especially SSL), but it does work! There are also 2
helper parameters that I still haven't found how to duplicate on Jetty 9, so
they are just be ignored. Actually, I
The API has indeed subtly changed, so that throwing in the Jars will not work.
And though Restlet doesn't use AJP to communicate with Jetty, it does try to
initialize AJP support, and those classes no longer exist in Jetty 9, thus
another kind of failure. Bottom line, it won't work.
Jerome, Jet
Restlet integration with Jetty (the org.restlet.ext.jetty extension) isn't
based on AJP but on core Jetty APIs, enable support of HTTP/HTTPS and AJP.
I haven't tried but dropping new Jetty JARs might just do it, but likely
they have changed their internal API here and there and some patches will
b
You can always use the servlet extension with Jetty.BryanOn Nov 06, 2013, at 08:45 AM, Tal Liron wrote:The answer, unfortunately, is no: Restlet uses AJP to connect to Jetty, which is unfortunate because it's not a recommended protocol, and has been dropped in Jetty 9. Would it be possible to cha
The answer, unfortunately, is no: Restlet uses AJP to connect to Jetty, which
is unfortunate because it's not a recommended protocol, and has been dropped in
Jetty 9.
Would it be possible to change the Jetty connector so that it would work with
either Jetty 8 or 9? It's very unfortunate that Re
16 matches
Mail list logo
