Hi Paul,
This is exactly what the Directory class does. You might also want to have a
look at the DirectoryResource class in the com.noelios.restlet packages to
understand the full behavior of Directory, especially if you have to
subclass it.
Best regards,
Jerome
2007/11/18, Paul J. Lucas
Hi Justin,
The usage of interfaces is discouraged in public APIs because they prevent
changes in later releases (breaking existing implementation classes).
I'm not familiar with EasyMock, but isn't it possible to generate mock
objects that are subclasses of other classes, like a MockRequest
Hi all,
Considering that we are late for the 1.1 M1 release, I think the timeline
should be shifted of one quarter : 1.1 final in Q1 2008 and 1.2 M1 in Q2
2008. I will update the roadmap accordingly. Note that we now plan to
release 1.1 M1 at the end of the month.
Also, one of the goal of 1.1 is
Jerome Louvel contact at noelios.com writes:
Hi Takasho,
Did you have a look at the Spring extension javadocs in the 1.1 snapshot?
There are some XML config snippets in them that you can use in your Spring
configuration file, like:
bean id=application
Jerome,
In my noodling with DAV method support, COPY and MOVE are especially
challenging to implement. By extending Directory and friends, you
can model a COPY as a GET and a PUT, and a MOVE as a GET, DELETE, and
PUT, but this is messy, not atomic in the right ways, and not very
performant.
Just wanted to report that my team has started using an updated
trunk for active development and it's successfully purged a
number of our hacks.
The optimized internal calls are working better than
our version, and the fixes to the behavior of clap: have made
a big difference in our ability to
Jerome, I know you've made this statement before (interfaces in public
APIs), and since it is your project, I've not pressed you about it,
but I'd still like to see some evidence that this is more than just
personal opinion.
As for unit testing Restlets, I've found them much easier to test than
great!!
best regards,
Thierry Boileau
On Nov 19, 2007 3:56 PM, Rob Heittman [EMAIL PROTECTED] wrote:
Just wanted to report that my team has started using an updated
trunk for active development and it's successfully purged a
number of our hacks.
The optimized internal calls are working
On 11/18/07, Justin Makeig [EMAIL PROTECTED] wrote:
I'm curious if and how others are writing unit tests for Restlet
applications. In previous J2EE web apps I've written I've made heavy
use of Easy Mock http://www.easymock.org/ for mocking collaborators
and replaying scripts to validate
Thanks for the quick improvement to Finder! That will definitely help. I'll let
you know how it goes.
Michael
-Original Message-
From: Jerome Louvel [mailto:[EMAIL PROTECTED]
Sent: 16 November 2007 18:26
To: discuss@restlet.tigris.org
Subject: RE: Resource convention over
Chuck, thanks for the input. In general, yes, Restlets are much
simpler in their dependencies than servlets and thus easier to test.
However, my struggle is extra cost of writing stubs vs. mocks http://
martinfowler.com/articles/mocksArentStubs.html. Mocks allow one to
just implement a test
On Nov 19, 2007, at 6:51 AM, Rob Heittman wrote:
Or maybe Paul can figure out a way to do it without the mess.
Right now, I'm still trying to get my head around all this. It's not
totally clear to me when things should be a Restlet or a Resource;
whether one should derive from Directory
Stian,
I would consider what you've helpfully included below an integration,
not unit test. These are invaluable, but I'm trying to just test
small pieces of functionality in isolation one at a time, not the
whole stack. For example, if I were to test my Resource
implementation's put
I'll add the Resin 3.0 server to that list you have. I found this gem
because I deploy on a shared server where I am not able to restart Resin,
nor am I in a position to debug it. It's been holding onto something for
over 5 days now. I tried redeploying an app with the new 1.0.6 lib and it
On Nov 19, 2007, at 6:51 AM, Rob Heittman wrote:
In my noodling with DAV method support, COPY and MOVE are especially
challenging to implement. By extending Directory and friends, you
can model a COPY as a GET and a PUT, and a MOVE as a GET, DELETE,
and PUT, but this is messy, not atomic
On Nov 19, 2007 3:35 PM, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Chuck,
Jerome, I know you've made this statement before (interfaces in public
APIs), and since it is your project, I've not pressed you about it,
but I'd still like to see some evidence that this is more than just
On Nov 19, 2007, at 8:12 PM, Paul J. Lucas wrote:
I've figured out that to do this right, yes: you do need to extend
DirectoryResource. The problem with that is that Engine insists on
creating an instance of DirectoryResource and not an instance of
one's derived class. So that means one
Hi Takasho,
Were you able to solve this problem ? Otherwise, could you create a bug
report, zip your project and attach it to the issue report ? Here is the bug
tracker to use (need a Tigris.org account):
http://restlet.tigris.org/servlets/ProjectIssues
Best regards,
Jerome
-Message
18 matches
Mail list logo
