Hello Mike,
I notice that GWT 2.3 introduces at least one breaking change in the
SerializableTypeOracleBuilder class. The constructor is not the same. This
is the same situation as for GWT 2.2 which leads us, at this time, to let
restlet 2.0 not compatible with GWT 2.2.
I have a look at this.
Bes
Hello Mike,
thanks for reporting this issue. The fix is available in the svn repository.
Best regards,
Thierry Boileau
Hello Mike,
>
> I notice that GWT 2.3 introduces at least one breaking change in the
> SerializableTypeOracleBuilder class. The constructor is not the same. This
> is the same
Hello Roger,
could you precise the version of Restlet?
Best regards,
Thierry Boileau
I still get this trace randomly in my log?
>
> really strange.
>
> does someone ever get the same?
>
> --
>
> http://restlet.tigris.org/ds/viewMessage.do?dsFor
Hello Shj,
For example, when you want to trace the server connector attached to a
component:
Component c = new Component();
Server s = new Server(Protocol.HTTP, 8182);
c.getServers().add(s);
s.getContext().getParameters().add("tracing", "true");
When using a Client
Hello all,
you can also adopt this form:
@Post
public Representation postHandler(Form form) throws ResourceException {
// Rest of the handler here
}
Best regards,
Thierry Boileau
You are welcomed.
>
> One thing I forgot: if you want to add an extra-level of robustness to
> your POST handler,
Hello Ike,
generally speaking, this status is the consequence of an error during the
communication between the client and the server. There could be
interruption, the remote URL is wrong, etc.
You can check the remote URL, use another client connector (for example the
"net" or the "httpclient" ext
Hello Adam,
I notice that the ChallengeResponse object is instantiated with a login
equals to "Authorization:", which is not permitted since a login cannot
contain the ":" character (see http://tools.ietf.org/html/rfc2617#section-2
).
ChallengeResponse cr = new ChallengeResponse(ChallengeScheme.H
Hello Anoop,
I suspect that an exception is thrown between the code that sets the 404
status code and the status filter. Do you notice something strange in the
log?
So in StatusFilter, it was sets it to a 500
>
This code is called when an exception is thrown and not caught by the
resource.
Bes
Hello,
basically, just set the Application's statusService with your own instance:
setStatusService(new StatusService() {
@Override
public Representation getRepresentation(Status status,
Request request, Response response) {
retur
Hello Bruno,
The converters are available via the usage of an Application (ie via the
Appication#converterService).
I suggest that you serve the sample TestServerApplication just as follow:
public static void main(String[] args) throws Exception {
Component c = new Component();
I'm not sure how (even though I think it was jettyson missing), but I got it
working with org.json.jar, jettyson-1.3.jar, org.restlet.ext.json.jar,
org.restlet.ext.xml.jar, org.restlet.ext.xstream.jar,
com.thoughtworks.xstream.jar.
So now I can use:
ClientResource clientResource = new ClientRes
Hi.
My app has now grow to contain different paths with different
authentications scheme and context, like:
/api
/console
/oauth
Then, there is the host:
This happened main
Restlet jar version:
Name: org.restlet
Implementation-Title: org.restlet
Implementation-Version: 2.0.5 (build 1)
Implementation-Vendor: Noelios Technologies
Name: org.restlet.ext.xml
Implementation-Title: org.restlet.ext.xml
Implementation-Version: 2.0.5 (build 1)
Implementation-Vendor: Noelios T
13 matches
Mail list logo