I can't seem to get an automatic checking of authentication happening for my
resource. Maybe I do not understand it correctly.
I've built my SharedSecretHelper, and SharedSecretGuard. In my
SharedSecretHelper my constructor is:
public HttpSharedSecretHelper() {
Hi Barrie,
How are your restlets wired up? It sounds like the guard is not in
the chain that leads to the UserResource.
Rhett
On Apr 6, 2008, at 4:02 PM, Barrie Selack wrote:
I can't seem to get an automatic checking of authentication
happening for my resource. Maybe I do not
Rhett,
That's what I believe as well... except I'm not sure how to do the wiring in
the UserResource.
Does the UserResource need to define something, or do I need to make a call to
force the check of the authentication for it to happen?
Regards,
Barrie
(guess I'll have to write a short Wiki
Hi Barrie,
That's what I believe as well... except I'm not sure how to do the
wiring in the UserResource.
You don't wire in the resource -- you create a chain of restlets that
leads to the resource. Take a look at section 9 of the tutorial.
Rhett,
Thanks. I've been through all the examples and tutorials. But I'm lost on the
relationship of Restlet, Router, Resource, Guard, etc. The tutorial attaches
Guards to a Restlet, but I'm attaching Resources to a Route (which is also show
later in the tutorials, but not in the context of a
Hi Barrie,
Restlet is the base class for all the stateless request handling
aspects of the framework, including Router and Guard. Resource is the
base class for the stateful handling of a single request. The
configured restlets determine which Resource winds up handling a
particular
6 matches
Mail list logo
