bug with SpringFinder?

Hi, I believe I may have found a bug with the way SpringFinder works in Restlet 2.1.4. I have two Application subclasses, each with one Router. Call them app1 and app2, mapped in my servlet-based web app to /app1 and /app2. Both apps define a template /metadata mapped to their own private

Re: bug with SpringFinder?

Hi Sean, thanks for submitting this question: I've entered an issue for that point: https://github.com/restlet/restlet-framework-java/issues/797 best regards, Thierry Boileau 2013/11/15 Sean Hogan s...@clixtec.ca Hi, I believe I may have found a bug with the way SpringFinder works in

Re: bug with SpringFinder?

Never mind. Like an idiot I had two beans named metadataResource. I thought Spring would whine about that, but apparently not. :-( (There may still be an issue with SpringFinder, but not from my flawed analysis.) Thanks, Sean On 13-11-15 01:31 PM, Sean Hogan wrote: Hi, I believe I may

Re: bug with SpringFinder?

ok, thanks Sean. I close the issue. Best regards, Thierry Boileau 2013/11/15 Sean Hogan s...@clixtec.ca Never mind. Like an idiot I had two beans named metadataResource. I thought Spring would whine about that, but apparently not. :-( (There may still be an issue with SpringFinder, but

Re: Bug in SpringFinder?

Hello Florian, I think that you need to override the init method in order to intialize properly your resource instance (such as getting from the model all data needed by this resource, check if this resource exists, setting the supported variants, etc). best regards, Thierry Boileau Hi

Bug in SpringFinder?

Hi folks, I think SpringFinder.createResource(...) should be changed from: public Resource createResource(Request request, Response response) { Resource result = createResource(); if (result != null) { result.init(getContext(), request, response); } return result; } }