Can someone pls provide some information on this exception. I am running
outside the Neolios Restlet Engine. Everything works fine but wondering
whether I actually need to implement this constructor and the purpose of
it.
16:30:32,578 WARN [/procmgr] procmgr: [Noelios Restlet Engine] - The
S
Hi Jim,
I have added the workaround to the bug report, we'll see if it makes sense
to change the core API.
Best regards,
Jerome
> -Message d'origine-
> De : Jim Alateras [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 1 juin 2007 05:16
> À : discuss@restlet.tigris.org
> Objet : Re: URI
I don't necessarily understand where the "first stage" and the "second
stage" are in the code you're referring to. So, I can't guess as to
whether it's a good solution.
Maybe think about a lower level functional class (ie. basically what is
Client right now) throwing checked exceptions out
Thierry,
It works nicely. I create a couple of routes for each resource. Does it
make sense to move some of this back to the core.
cheers
Jim Alateras wrote:
cool, i'll give it a go today.
cheers
Thierry Boileau wrote:
Hi Jim,
as a workaround, you can define 2 routes like this :
//Serve
works for me. Will you create an issue for this.
cheers
Thierry Boileau wrote:
Hello,
we had a discussion with Jerome, and we plainly agree with the fact
there is a problem in HttpClientHelper#handle [1] method as pointed out
thanksfully by Adam and Jim.
This method first builds a call objec
I've done the same but test through the the Router since i'm also
interested that the request gets routed to the appropriate resource.
Some of my resources talk to a DAO so i am thinking of using something
like EasyMock [1] to isolate my resource testing.
cheers
[1] http://www.easymock.org/
On 31-May-07, at 3:52 PM, Chuck Hinson wrote:
Toby,
I'm about to try out the ssl client auth stuff. I looked in javadoc,
but didn't see anything.
What all did you have to do to get client auth working?
I assume I at least have to do (the equivalent of) the following
(on the
command line):
Toby,
I'm about to try out the ssl client auth stuff. I looked in javadoc,
but didn't see anything.
What all did you have to do to get client auth working?
I assume I at least have to do (the equivalent of) the following (on the
command line):
-Djavax.net.ssl.trustStore=arces-ca-trust.jk
As Adam points out, it is a good idea to keep the bulk of your business
logic outside your restlet classes for testing purposes. However, we've
found it very easy to directly invoke various restlet components for
testing purposes - mostly to check return codes and ensure content
negotiation stuff
Hello,
we had a discussion with Jerome, and we plainly agree with the fact
there is a problem in HttpClientHelper#handle [1] method as pointed out
thanksfully by Adam and Jim.
This method first builds a call object then sends this call and gets the
server's response.
The try/catch block is ver
On 30 May 2007, at 22:56, Jim Alateras wrote:
I'm fine with the design choice. I stumbled across a place where
this wasn't happening [1] but it was hard to associate a HTTP
status code with the failure since the request failed to leave the
client. Currently I have patched it to set the fo
11 matches
Mail list logo