Hi Cliff,
you can also update the type of the declared variable in your URI template:
Route route = router.attach(/foos/{foo}/bar, sth);
Template template =
route.getTemplate().setMatchingMode(Template.MODE_EQUALS);
template.getVariables().put(foo, new Variable(Variable.TYPE_WORD));
You can
Hi guys,
I've replaced all catch(final strings with catch(... Checked in SVN
trunk.
There is even a regular expression feature in Eclipse search/replace feature
that we could have leveraged... Eclipse developers can find good workarounds
sometimes ;-)
Best regards,
Jérôme Louvel
--
Restlet
Wow!! So many great news and shiny projects built on top of Restlet, that
make us at Noelios feel really happy.
Rob, I will definitely blog about those projects when GoGoEgo is publicly
released!
If others in this list want to share how they leverage the technology in the
real world
Hi Mark,
Thanks for this feed-back. We realize that the Spring extensions still lack
a comprehensive documentation. We even have a RFE for that where I've just
added your comments:
Improve Spring documentation
http://restlet.tigris.org/issues/show_bug.cgi?id=614
I won't make any promise but we
Hi Sanjay,
I can confirm that Client instances have been designed to be reused
concurrently by several threads. The code should be thread-safe (I've just
fixed the issue Tim noticed).
But, nothing prevents you from having several instances of them if that
makes sense, for example for
Sanjay,
I agree with your idea. See the new RFE for details:
Support connection timeout for Apache HTTP client
http://restlet.tigris.org/issues/show_bug.cgi?id=622
Best regards,
Jérôme Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~
Hi Cliff,
In combination with MODE_EQUALS, you could also add a variable for your
extensions like: /foos/{foo}/bar.{ext}. That could reduce the number of
alternative routes you would have to attach.
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Hi Tim,
Thanks for checking this part of the code. I've just fixed all the points
you have reported in SVN trunk.
Regarding the last point you mentioned, I've entered a RFE:
Handlers don't nest consistently when setting current objects
http://restlet.tigris.org/issues/show_bug.cgi?id=621
Hi Kevin,
Thanks for suggestion. For tracking purpose, here is the link to the RFE you
created with your patch:
Add SpringEngine
http://restlet.tigris.org/issues/show_bug.cgi?id=620
In fact, the current plan for Restlet 1.2 is to move the
com.noelios.restlet.* packages into
Hi Richard,
Option 3 seems the best to me. Note that when you do a PUT you shouldn't
send a partial representation as the entity sent is expected to fully
replace the existing representation.
Another option you could consider is to give an URI to each modifiable field
and update them
Hi John,
We should indeed provide a better support for this use case. Your
suggestions sounds good. I've entered this RFE:
Allow DTD/XSD validation to be turned off
http://restlet.tigris.org/issues/show_bug.cgi?id=623
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~
I'm posting my take on the Spring config detailed on the wiki.
Previously I had been using a subclass of Application, with multiple
invocations of router.attach() (per the FirstResource app) to get
routing done to specific restlets.
Hope this helps someone out there get over the hump. In
On Friday 2008.10.17, at 04:01 , Jerome Louvel wrote:
[...]
In combination with MODE_EQUALS, you could also add a variable for
your
extensions like: /foos/{foo}/bar.{ext}. That could reduce the
number of
alternative routes you would have to attach.
Yes and no. I use that trick but I still
This is an example of the general need to validate all input. IMHO,
if you look at it that way then you basically need to do Option #3
anyways since good input validation practice is to default deny +
accept only known good input patterns.
Depending on the depth and complexity of the full
I followed the code in this tutorial:
http://www.restlet.org/documentation/1.0/tutorial#part09
But when the authentication fails, I'm getting a 403 error, rather
than a 401 error as the code suggests. This is with Restlet v1.0.11 -
any ideas?
Regards,
Ian.
--
Ian Clarke
CEO, Uprizer Labs
Hi Mark,
You might also consider using SpringBeanRouter. If you only have one
URI mapping per resource, it allows your URIs to be mapped directly in
the bean definitions. Your example would be like this using
SpringBeanRouter (note: not tested):
!-- server bean as before --
bean
John and Jérôme,
Thanks much, this is *exactly* what I need!
Cliff
-Original Message-
From: John D. Mitchell [mailto:[EMAIL PROTECTED]
Sent: Friday, October 17, 2008 7:54 AM
To: discuss@restlet.tigris.org
Subject: Re: uriPattern exactness
On Friday 2008.10.17, at 04:01 ,
I agree with everything you've written. It seems to me that while there is
a theoretical benefit to having the engine and RI separated, it doesn't see
much practical use.
The end result of this patch is that I can configure the Engine to use the
connectors I want via Spring without using the
Hello Mark,
I've updated the sample application and its description:
http://wiki.restlet.org/docs_1.1/13-restlet/28-restlet/144-restlet.html
Best regards,
Thierry Boileau
--
Restlet ~ Core developer ~ http://www.restlet.org http://www.restlet.org/
Noelios Technologies ~ Co-founder ~
19 matches
Mail list logo