Thanks for the input. I was able to get Restlet to recognize my helper. Not
sure I understand the implications of setting the clientSide boolean value to
true but anyway what I'm fighting with now is the line in my overridden
parseResponse method for setting the raw value. Unfortunately when
I feel like an idiot (lol). I just needed to change my setRawValue method line
so that it was using the ChallengeResponse argument in the method itself and
not the HttpRequest adapter's getChallengeResponse(). It's understandable why
that would have created an infinite loop. Anyway thanks again
I had the same problem.
If i remember correctly, i solved it by changing the Constructor of my
Custom scheme.
As you can see, the restlet-Engine automatically adds HTTP_ to your Scheme
name and searches the registered Schemes only for that name. Don't know if
its a bug or intended this way.
Either
Hi Paul,
As Sebastian responded, part of the solution is to match up the ChallengeScheme
name with what Restlet expects. The other part is to register your helper as
being both for client-side and server-side. I'm not sure why this is, but
Restlet[1] always looks for a client-side helper
4 matches
Mail list logo
