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
10 matches
Mail list logo