Hello Lee,
This problem has been fixed (see
http://restlet.tigris.org/issues/show_bug.cgi?id=316) and is available
in the svn repository.
best regards,
Thierry Boileau
I'm not sure if this is a bug or a feature but...
In the org.restlet.resource.DomRepresentation class, the write method is
Hello Jim,
I couldn't really explain. :)
The handle method of the Application class already detect if the
Appplication is started or not.
As Irfan provides this sample code from a real application, he may have
forgotten to remove this method that can be usefull for some
initializations stuff.
Hi sync,
an application has its own tunnelfilter ready to work. If you want to
use it, there is nothing to do at all.
Could you explain us what you want to do?
The behaviour of the Tunnel Service is specified in the Restlet API (see
[1]) and implemented in the reference implementation (the
Hi Jim,
as a workaround, you can define 2 routes like this :
//Serves only http://localhost:6080/appcontext/version
route = [...]attach(/version, ...);
route.getTemplate().setMatchingMode(Template.MODE_EQUALS)
//Serves only http://localhost:6080/appcontext/version?
// and
Thanks for the quick fix!
On 21-May-07, at 6:43 AM, Jerome Louvel wrote:
Hi all,
I've added support for client authentication in the SVN trunk
(upcoming 1.1). Only Simple connector has support to retrieve the
client certificates,
These two features are working well for me in 1.1b1.
More specifically, as
cool, i'll give it a go today.
cheers
/jima
Thierry Boileau wrote:
Hi Jim,
as a workaround, you can define 2 routes like this :
//Serves only http://localhost:6080/appcontext/version
route = [...]attach(/version, ...);
route.getTemplate().setMatchingMode(Template.MODE_EQUALS)
//Serves only
Thierry,
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 following status code
I'm interested in adding a unit test for certain aspects of the behavior of my
REST service, one that can execute outside the confines of a Web server. It
would be sufficient if there were merely a way for me to call the Restlet
classes directly, then examine the response.
What's not obvious to
Bryan,
I know this isn't directly answering your question, but how we do
testing is by integrating with the Spring Framework. With Spring, you
get various DAO and service layer support classes which are easily testable.
Essentially, if you make your Restlets as dumb as possible by
10 matches
Mail list logo
