Hello John, could you provide a sample application? I've just tried with a WadlApplication and WadlResources (having the same routing plan than you) and it works for me: that is to say when I send a request option to the application root URI, I get the description of all resources. The WadlApplication is normally able to walk across filters.
Best regards, Thierry Boileau > > Hi, all- > > I'm using Restlet 1.1.7. I have a situation where my routing chain > looks like: > > router +- filter -- filter -- router +- resource C > +- resource A +- resource D > +- resource B +- etc.... > > My Application and all Resources are Wadl- versions. > > When I retrieve the WADL for my app, I get the information about the > resource A and resource B, but not C, D, and so on. I'm guessing that > I can solve this by using WadlWrapper to wrap the filters I'm using, > but it's not clear to me how that is intended to work. > > Does anyone have any sample code that shows WadlWrapper in action? Or > any hints about how the filters can be wrapped, and the ResourceInfo > initialized and returned? Or am I looking at this the wrong way, and > is there a different way to retrieve the information about the > Resources behind the filters? > > Thanks for your help! > > -------------------------------- > John Wismar ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2442053
