Tim Peierls wrote:
> It's not a huge deal, but superfluous final keywords are clutter that
> distract from the places where final is being used meaningfully. I
> think it's worth cleaning this up incrementally in Restlet.
This would do it:
perl -pie 's/final (?=[a-zA-Z]*Exception)//g' `find . -na
Thank you.
Yes, two routes to the same resource bugs me. It looked a bit strange
when I when I coded it.
On Oct 15, 2008, at 1:30 AM, Thierry Boileau wrote:
Hello Mark,
you can have a look at the Request#getResourceRef() (that returns an
instance of the Reference class) and the Referenc
Hello Aaron,
you can have a look at the documentation page for the connectors
(http://www.restlet.org/documentation/1.1/connectors#server_connectors).
The parameter is set on the server connector, not the application or the
component.
Server server = new Server(Protocol.HTTP, 8182, restlet);
Hi Jerome,
Moving to 1.1 RC2 it is indeed the direction. I however would like to be able
to make a case stating the issue. As bug id 439 had a fix, I was curious what
tests were run to ensure the problem has been eliminated in versions 1.1m4 and
greater.
Thanks,
Sanjay
What are folks thoughts on adding a SpringEngine class to the Spring
extension?
This class would be a helper for configuring an Engine instance. Right now,
the noelios Engine doesn't expose some of the necessary properties through
setters (registeredClients, registeredServers etc) and you must ca
Hello Mark,
you can have a look at the Request#getResourceRef() (that returns an
instance of the Reference class) and the Reference#getLastSegment() methods.
Otherwise, you can wonder why there are 2 distinct routes that point to
the same resource.
Otherwise, you can define the routes as follow
Hello Luis,
if you use the file "protocol", you must provide the absolute path.
Which leads to determine how to get the "current" path.
This info could be passed by the servlet container to the application
via a context property.
In order to achieve this, you can extend the ServerServlet class
I don't suppose we have any Eclipse developers on the list taking notes?
On Wed, Oct 15, 2008 at 3:26 AM, Richard Hoberman <
[EMAIL PROTECTED]> wrote:
> Tim Peierls wrote:
> > It's not a huge deal, but superfluous final keywords are clutter that
> > distract from the places where final is being u
Good day.
I notice that both the FAQ and Wiki have sections treating the use of
the org.restlet.ext.spring package to manage a restlet app in a Spring
container.
Is there a similar example someone might offer on using the
com.noelios.restlet.ext.spring package to manage a restlet app in t
Thierry Boileau noelios.com> writes:
>
>
> Hello Aaron,you can have a look at the documentation page for
> the connectors
> (http://www.restlet.org/documentation/1.1/connectors#server_connectors).
> The parameter is set on the server connector, not the application or
> the component.Server serv
Thierry, good day.
Is there sample code available showing how to use the HTTP Digest
authentication scheme?
On Oct 14, 2008, at 7:08 AM, Thierry Boileau wrote:
Hello Mark,
the current sample GWT application has been updated with
authentication, and usage of JSON and XML representations.
I was wondering if there is some trick way to find the exact matched
pattern. Specifically, I am seeing this (somewhat logical) behavior.
If the uriPattern is "/foos/{foo}/bar"
This of course matches something like "/foos/myFoo/barlksjfljj.xml"
What I want is: If I type in "/foos/myFoo/barlks
Hi Jerome,
I believe I have found the cause of our problem.
We use Restlet Client by instantiating it every time, for example,
for (int i = 0; i < 1000; i++) {
Client c = new Client();
Response response = c.handle(request);
response.release();
}
we end up creating a
I think Client is intended to be thread-safe, but it isn't currently,
because the connectTimeout field is not guarded by a lock (nor is it
volatile) -- sorry Jerome, I just noticed this. This is not likely to cause
any problems, but it *is* wrong.
And there may be other concurrency issues lurking
14 matches
Mail list logo