Hello Jim,
there may be a problem with the web.xml configuration file. If
ProcessManagerApplication is not a Restlet application, you should not
have to implement such constructor, and this kind of error should not
happen...
Could you send us your configuration file?
Best regards,
Thierry
Hi Jim and Adam,
As the connectors in the Restlet API are protocol-neutral (HTTP-centric
indeed but usable for other protocols/schemes like file:// and ftp://) and
as we allow for switchable implementations of those connectors (JDK's
HttpURLConnection, Apache HTTP, etc.), we don't control all
Hi Adam,
The fix I've just checked in SVN should solve your issue. You now can check
whether your request generated an error by solely looking at the response's
status code. In your case, it would return a CONNECTOR_ERROR_INTERNAL
because we don't fully deal with invalid URIs. In the future, we
Hi Jim,
The issue might be coming from the lack of a constructor with a Context
parameter in your ProcessManagerApplication class. As o.r.Application also
has a default constructor, you might have missed this requirement.
Best regards,
Jerome
-Message d'origine-
De : Jim Alateras
The offending code has been fixed in HttpClientHelper like this:
try {
HttpClientCall httpCall = getConverter().toSpecific(this,
request);
getConverter().commit(httpCall, request, response);
} catch (Exception e) {
getLogger().log(Level.INFO,
5 matches
Mail list logo