gmane.comp.java.restlet

AW: Problem with delete method in my client application

Stephan Koops — 2013-05-25T09:55:19

Hi,

Your application design is not restful. You don't have to use the representation data to identify your business object. You identify your business object only with the URL.

The representation contains only the business object, not the information to locate it.
For that reason a delete request has on entity.

But this does not allow a NullPointerException :-). An IllegalArgumentException would be better.

Best regards
   Stephan

Problem with delete method in my client application

Sergio — 2013-05-23T10:30:12

Hi all! I'm a newbie with Restlet and I have a problem. I created a service that works perfectly but my client application does not. It fails when I invoke the DELETE method. GET, POST and PUT works fine.

This is the code from my client application:

    JSONObject object = new JSONObject();

    object.put("name", "a name");

    Request request = new Request(Method.DELETE, reference);

    request.setEntity(new JsonRepresentation(object.toString()));

    Client client = new Client(Protocol.HTTP);
    Response response = client.handle(request);
    String text = response.getEntity().getText();

The code from the ServerResource class:

public class MyResource extends ServerResource {

    < at >Delete
    public Representation deleteUser(Representation entity) {
        try {
            String jsonString = (new JsonRepresentation(entity)).getJsonObject().toString();
            Map map = (Map) (new JSONParser()).parse(jsonString);

            if(map.size() > 0) {
                String message = dbc.deleteUse

Possible bug in AuthorizationBaseServerResource

Andie Similon — 2013-05-22T15:34:46

I have noticed that in some usecases that the function getAuthSession() in AuthorizationBaseServerResource returns null because the cookie has not been set yet. Althought it is set before a redirect in the Attributes of the request. Wouldn't it be more logical to change the getAuthSession() method to:

    protected AuthSession getAuthSession() {
        // Get some basic information
    String sessionId = (String) getRequest().getAttributes().get(
                ClientCookieID);
    
    if (sessionId == null)
            sessionId = getCookies().getFirstValue(ClientCookieID);
    
        getLogger().fine("sessionId = " + sessionId);

        getRequest().getAttributes();
        
        AuthSession session = (sessionId == null) ? null
                : (AuthSession) getContext().getAttributes().get(sessionId);
        return session;
    }

So first verifying the the sessionId is in the request and only then checking if it is in the cookie?

I see that they did this in 2.1 version of restlet, but no

HTTP_DIGEST authorization in android client

Mateusz Zakład — 2013-05-21T00:07:44

Hey All,

Got following problem with HTTP_DIGEST authorization via Restlet framework on Android.

05-20 18:39:14.623: W/System.err(4584): Challenge scheme HTTP_DIGEST not supported by the Restlet engine. 

05-20 18:39:17.498: W/System.err(4584): Couldn't find any helper support the HTTP_Digest challenge scheme.


Part code that is executed on client and gives above error

clientResource =new ClientResource("http://example.com/position");
try{
clientResource.wrap(MailResource.class);
ChallengeResponse challengeResponse = new ChallengeResponse(ChallengeScheme.HTTP_DIGEST,
"1671046999",
"tiger");      
clientResource.setChallengeResponse(challengeResponse);
clientResource.get();
}
catch (Exception e)
{
e.printStackTrace();
}

Checked that resource via browser and authorization seems to be fine.

Any advices?:)

Google doesn't brought up anything except solution
"I was still missing the DigestHelper. But I found a post about Engine.setUserClassLoader which fixed that
(I'm running in an eclipse plugin/OSGI enviro

Re: latest on push technology

Jerome Louvel — 2013-05-20T15:36:17

Hi Pieter,

Good question.

For 1) you might want to try implementing HTML5 Server-Side Event which
relies on streaming representations as well.
For 2) you should indeed try streaming representations. Some have
experienced issues with network buffering though, but it should work.

Another RESTful way moving forward will be to rely on HTTP/2.0 server-side
push
http://tools.ietf.org/html/draft-ietf-httpbis-http2-02#section-4.3

Otherwise, you will have to rely on another technology such as WebSockets
and integrate it with RF. Maybe there is space for a WebSockets extension
based on HTTP/2.0 semantics. It would probably require an evolution of
Restlet API though,

Best regards,
Jerome
--
http://restlet.org
http://twitter.com/#!/jlouvel




2013/5/11 Pieter Martin <pietermartin< at >lavabit.com>


------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3055973

Cannot find a copy of sample MyNtlmHttpClientHelper.java

Travis Ferguson — 2013-05-16T05:09:07

Document:
http://restlet.org/learn/guide/2.0/core/security/authentication/ntml


References a sample NTLM Client Helper for usage with the Apache HTTPClient.  

Does anyone have a copy of the MyNtlmHttpClientHelper.java file that this article references?   Every link I can find appears to point directly back to the main wiki/tutorial pages.

from: http://restlet.org/learn/guide/2.0#/363-restlet/version/default/part/AttachmentData/data/MyNtlmHttpClientHelper.java

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3055657

Re: endless "Too many open files" exceptions

Robert Dodier — 2013-05-15T17:22:13

OK, thanks for the advice.
I don't suppose it makes much difference, but
I'm curious to know whether the particular
kind of error which I observed is anything which
has been observed before. Also whether the
"too many open files" error is a consequence
of some known weakness. What I'm trying to
find is some assurance that the problem will
go away if I use some other classes.

Thanks for your help, I appreciate it very much.

Robert Dodier

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3055617

Re: endless "Too many open files" exceptions

Jerome Louvel — 2013-05-14T07:37:23

Hi Robert,

You should try to use the Jetty or Simple connector extensions instead,
they are more stable at this point.

Best regards,
Jerome
--
http://restlet.org
http://twitter.com/#!/jlouvel




2013/5/14 Robert Dodier <robert.dodier< at >gmail.com>


------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3055472

endless "Too many open files" exceptions

Robert Dodier — 2013-05-13T22:20:19

Hi,

I am working with Restlet 2.1.2, using both client and server
code as parts of a larger applications.

After working correctly for some time (maybe days),
a GET request causes an endless succession of
"Too many open files" exceptions. As it happens,
those are being written into a log file (by nohup) and
eventually exhaust all available disk space -- it appears
the exceptions just keep pouring out, one after another.
Maybe the failed connection is retried immediately, so that
fails again with the same error? Just guessing. I looked at
the source code but I can't tell what's going on.

Here is one such exception. The message is printed by
ServerConnectionController.onSelected.

  Unexpected error while accepting new connection

  java.io.IOException: Too many open files
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:163)
at org.restlet.engine.connector.ServerConnectionController.onSelected(ServerConnectionController

Re: Serving static files using Directory and CLAP from a jar

Robert Brewer — 2013-05-11T04:41:55

Hello Thierry B. My dissertation is finished, so I can finally get
back to debugging this problem :)

Your sample code & project were quite helpful, however, it differed
from my code in one way: my static files are contained in a
subdirectory of the jar file. So I made 2 tiny modifications to your
sample: the path to the directory is now "/stat", and I created a
"stat" directory in the jar file that contains the index.html file.

Once I made these changes, it replicates the problem I am having. The
modified sample code behaves just like my application: if I go to
http://localhost:8182/stat/ my browser downloads a zero-length file,
but localhost:8182/stat/index.html works fine.

Am I misunderstanding something, or is this a bug?

I have attached a zip file with my modified version of the project.
There are two jar files: testRobert.jar is the original jar file,
while newTestRobert.jar is my modified version so one can see the
differences easily.

Thank you for your assistance with this bedeviling problem.

On

latest on push technology

Pieter Martin — 2013-05-11T08:05:40

Hi,

What is the current recommended strategy with restlet to implement some 
form of a server side push in a browser environment.

In our case we have 2 use cases for this.

1) A standard publish/subscribe requirement for sending messages to the 
client.
2) We need to simulate a server side ssh or telnet terminal session via 
the browser.

For 2 I think it might be better and simpler to use restlet's current 
streaming representation support.

BTW, really enjoying working with the restlet api.

Thanks
Pieter

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3055303

Re: Assistance with persisting objects

Jerome Louvel — 2013-05-10T13:47:53

Hi Graham,

The shortened links don't resolve correctly in Chrome.

Could you send them in full?

Best regards,
Jerome
--
http://restlet.org
http://twitter.com/#!/jlouvel





2013/5/9 Graham Hunter <graham-hunter< at >live.com>


------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3055266

Assistance with persisting objects

Graham Hunter — 2013-05-09T04:02:36

I have asked two questions on StackOverflow and was just awarded the "Tumbleweeds" badge because of the low view count and no answers.  I have also searched the web multiple times and don't see anything that answers these questions.

Could someone on this list please take a look at these and let me know how application and request persistence works in Restlet?

http://tinyurl.com/bmhoxvm

http://tinyurl.com/d2xkw8k

Thanks!

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3055155

Re: CookieAuthenticator and redirect

Pieter Martin — 2013-05-09T11:45:57

Ok, not sure how this worked but using wireshark I could see the zero 
width spaces prepended to the targetUri.
It seems as tho the name "targetUri" is special somewhere. Changing that 
to anything else makes the zero-width-spaces not appear.
So now I am using redirectUri and all is fine.

Pieter

On 08/05/2013 16:46, Pieter Martin wrote:

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3055180

Re: CookieAuthenticator and redirect

Pieter Martin — 2013-05-08T14:46:37

Hi,

I have had time to try the CookieAuthenticator again and have gotten 
further. I override the beforeHandle method to intercept the correct urls.

I am running restlet inside jetty using 
org.restlet.ext.servlet.ServerServlet.

However for some reason the targetUri query parameter name comes back 
from the browser with a zero width string space prepended to it. The 
character is "\u200B".

The following code make the redirection work as then the targetUri is 
found and redirected to.

StringBuilder stringBuilder = new StringBuilder();
stringBuilder.append("\u200B");
stringBuilder.append("targetUri");
authenticator.setRedirectQueryName(stringBuilder.toString());

On calling the logout via <a href="/cm/logout? 
targetUri=cm/rest/tools/dashboard.ftl"> the targetUri has 3 zero width 
spaces prepended to it.

This then breaks the redirect logic as the targetUri is not found to 
redirect to.

Not sure where the zero length space is coming from but perhaps it can 
be parsed out.
Any ideas on this?

Tha

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

Jerome Louvel — 2013-05-06T20:31:19

Thanks Alex for the follow-up, I'm sure it will help other users.

Cheers,
Jerome


2013/5/6 Alex <alexdimo60< at >yahoo.gr>


------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3054999

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

Alex — 2013-05-06T17:48:25

Ok, I found the root cause of the problem.
It had nothing to do with Restlet or my code. It was all a matter of installing correctly the intermediate certificates on AWS. The certificate chain of my CA consists of 4 certificate files, and AWS needs this chain in a very specific order (signing certificate first, CA root certificate last, and all other certificates in between), given in a pem/text format. Unfortunately the AWS documentation is a mess, so I had to dig around and do some trial-and-error before making it work.

Your suggestion about checking the getStatus() stack (and the java.security.cert.CertPathValidatorException exception) of the response was the trigger that lead me to investigate and revise the way I installed my certs on AWS, so thanks for that. :)

So I guess this matter is closed. Thanks for the support, I really appreciate it. :)
Keep up the good work you're doing on Restlet.

br,
Alex



--
View this message in context: http://restlet-discuss.1400322.n2.nabble.com/Android-client-Restl

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

Alex — 2013-05-06T16:27:17

This is what I get from the Eclipse debugger, for the "response" object of the corresponding ClientResource:

Communication Error (1001) - The connector failed to complete the communication with the server
1001
The connector failed to complete the communication with the server
Communication Error
javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
http://www.restlet.org/documentation/2.1/android/api/org/restlet/data/Status.html#CONNECTOR_ERROR_COMMUNICATION

Thanks in advance for any advice. :)



--
View this message in context: http://restlet-discuss.1400322.n2.nabble.com/Android-client-Restlet-2-0-15-cannot-connect-with-HTTPS-SSL-recoverable-error-1001-tp7578771p7578785.html
Sent from the Restlet Discuss mailing list archive at Nabble.com.

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3054990

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

Jerome Louvel — 2013-05-06T15:49:54

Have you tried to debug locally in Eclipse, using the Java SE edition? In
version 2.1 you should get additional debug information by looking at the
getResponse().getStatus() object. It should embed the underlying exception.

Otherwise, could you package a small project reproducing the issue? That
will be easier for us to debug.

Jerome


2013/5/6 Alex <alexdimo60< at >yahoo.gr>


------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3054988

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

Alex — 2013-05-06T15:17:07

This doesn't have the desired result either. :/

br,
Alex

On 6 Μαϊ 2013, at 6:08 μ.μ., "Jerome Louvel-3 [via Restlet Discuss]" <ml-node+s1400322n7578782h10< at >n2.nabble.com> wrote:






--
View this message in context: http://restlet-discuss.1400322.n2.nabble.com/Android-client-Restlet-2-0-15-cannot-connect-with-HTTPS-SSL-recoverable-error-1001-tp7578771p7578783.html
Sent from the Restlet Discuss mailing list archive at Nabble.com.

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3054983

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

Jerome Louvel — 2013-05-06T15:07:47

Alex;

You to put the connector in the first postion doing this:

Engine.getInstance().getRegisteredClients().add(*0, *new org.restlet.ext.net
.HttpClientHelper(null));

Best regards,
Jerome



2013/5/6 Alex <alexdimo60< at >yahoo.gr>


------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3054982