; --
> http://www.restlet.com
> http://twitter.com/#!/jlouvel
>
>
> -Message d'origine-
> De : Michael Henderson [mailto:dillius at gmail dot com]
> Envoyé : mercredi 21 mars 2012 21:41
> À : discuss at restlet dot tigris dot org
> Objet : RE: Re: ConverterService be
The main thing that caught me off guard was the lack of real consideration of
the HTTP headers for determining the converter to be used. Though I may be
incorrect in this belief, as I have not gone through the Restlet code base
enough to know for sure that it is not being considered for the purp
I have managed to resolve the issue with a customization to the JAXBConverter.
I would suggest this change being considered for the main extension:
Current version:
@Override
public float score(Representation source, Class target,
Resource resource) {
float result =
A quick correction:
Not Restlet 2.1m3 but 2.1RC3
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2938280
I am using Restlet v2.1m3.
I recently began working on adding JSON as an available media type on top of
existing XML functionality through JAXB. While I have had no real issues with
GET calls Accepting application/json, PUT calls seem to be ignoring the
availability of the Jackson converter.
E
Found that this issue has actually been reported before, though it was not
acknowledged as being all of the parameters.
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2712238
Downgrading to a 7.2.X version of Jetty resolves the issue. Will have to look
to updating my Res
I have been working to update an application to make use of HTTPS instead of
HTTP and am having a difficult time getting Jetty to cooperate with me. It
seems to be ignoring my SSL Parameters.
Component comp = new Component();
Server server = comp.getServers().add(
7 matches
Mail list logo
