Hi all,
Michael, if you don't want to introduce redundancy in your URI templates,
you can also use a hierarchy of routers, or maybe use String constants to
compose the URI templates.
Concerning your {id} variable, it is possible to make it match any URI
character.
Template template =
As a third party kibitzer ... I feel like saying Restlet vs. Servlet at
all is a bit semantically inadmissible. It's not an or operation. You
can run Restlet with, without, in, outside, talking to, or being talked to
by Servlet. The scope of the javax.servlet API is intentionally narrower;
all
Hi Jaime,
Since the Restlet vs Servlet topic was touched, please let me
include a related concern that I'm sure n00bs like me will share
Jerome, in that FAQ you mention (this one I assume
http://www.restlet.org/about/faq), in question #3 it says:
Finally, the Restlet API is I/O agnostic
Hi Stephan,
I agree for the documentation improvements. Many methods returning a
modifiable list where already documented so it wasn't a pain to make sure
all the remaining ones were documented as well.
This is done in SVN trunk.
Best regards,
Jerome
-Message d'origine-
De :
On Feb 5, 2008 3:38 AM, Jerome Louvel [EMAIL PROTECTED] wrote:
However, they can't leverage NIO from the socket to the Servlet as the
Servlet API has no provision for NIO as explained above. This is where the
Restlet API makes the difference, by introducing the Representation class
based on
Hi Tim,
Very good point. Now that I've read the Java Concurrency in Practice book
(excellent BTW!), I fully realize how this point is crucial.
Let's tackle it with the on-going Grizzly HTTP and GWT efforts. I've added
your comment here:
Complete Grizzly connector
Thanks. Using Variable.TYPE_URI_ALL works. Though it would be nice to have
something like Variable.TYPE_URI_ALL_WITHOUT_QUERY or something like that since
{id} now includes the query string. That's not an issue in my case, though, so
it works well enough.
Cheers,
Michael
-Original
Hi guys,
I'm using Release 1.0.7 of the restlet API. I see a troubling response when I
set a 401 error response using the API
See here..
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
GET /apiserver/
html
head
titleStatus page/title
/head
Two problems I had
GET /apiserver/
should have been
GET /apiserver/ HTTP/1.1
I found that using the
response.setChallengeRequest(new
ChallengeRequest(ChallengeScheme.HTTP_BASIC,APIServer));
Very helpful, that seems to have solved my little problem. I would still LOVE to
see my raw http
Hi Mark,
Thanks for following up with the solution to your issue.
To see the raw headers, please check this FAQ entry:
http://www.restlet.org/documentation/1.0/faq#01
Best regards,
Jerome
-Message d'origine-
De : news [mailto:[EMAIL PROTECTED] De la part de Mark
Envoyé : mardi 5
Hey, isn't semantic inadmissibility the basis for thought crimes and
fundamentalism?
:)
I want to thank you Rob for the detailed answer, I get your point
about the higher abstraction level giving you more freedom from the
implementation. That's definitively a good thing.
When you say callbacks,
Exactly ...
In my case, I'm working on Restlet API support in Google Web Toolkit using
XmlHttpRequest as the Client. As this is idiomatically an asynchronous
facility -- regardless of whether your response is short lived (AJAX style)
or long lived (Comet style), the API needs ways of handling
Thanks for your answer Jerome.
The introductory paper was what triggered the question in my mind -- I
guess I need to read Java Concurrency in Practice.
Cheers
Jaime
On Feb 5, 2008 3:38 AM, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Jaime,
Since the Restlet vs Servlet topic was touched,
How are you loading the spring config?
On Feb 5, 2008 2:21 PM, dev dev [EMAIL PROTECTED] wrote:
We have spent a bit of time on this and we cannot seem to find ways to get
this to work for such a simple configuration. We are using version 1.1-M2.
Simple method to start the server.
public
I found the problem . It works after we make the following changes (server
first then component).
// Start the Restlet component
Server server = (Server) SpringContextLoader.getBean(server);
logger.debug(value1:: + server.getContext
().getParameters().getFirstValue(key1));
Finally got every integrated to our maven 2 build. However, we got this
exception when running one of our test cases (mvn test -Dtest=testjibx). We
define the jiBX binding in our pom.xml. What did we do wrong?
plugin
groupIdorg.jibx/groupId
What's the status of Atom/APP support in Restlets? Issue 72 [1] (Atom
and APP client support) indicates 1.1 M3 for delivery and the javadoc
[2] warns of its experimental status. What's missing/known to be broken?
Regards,
Michael.
[1] - http://restlet.tigris.org/issues/show_bug.cgi?id=72
17 matches
Mail list logo
