The issue with handling wadl queries has been fixed. Justs would like to describe what exactly has been fixed. If we have a web app listening on http://localhost:8080/myapp and one or more root resources, say with "/1" and "/2" paths, then wadl queries such as
http://localhost:8080/myapp/1?_wadl http://localhost:8080/myapp/2?_wadl work fine. http://localhost:8080/myapp/?_wadl returning a description of all the root resources works (in my own experience) at least and http://localhost:8080/myapp?_wadl does not work on Tomcat but does on Jetty (at least for me). The fix ensures both http://localhost:8080/myapp/?_wadl and http://localhost:8080/myapp?_wadl work fine. cheers, Sergey On Fri, Nov 12, 2010 at 8:46 AM, Jérôme Herry <[email protected]> wrote: > Is there a way to add this context programmaticaly or via a configuration > file? I tried with a web.xml file but it does not seem to read it. > > 2010/11/10 Daniel Kulp <[email protected]> > > > On Wednesday 10 November 2010 1:37:08 pm Sergey Beryozkin wrote: > > > > Yes that was an example. But it says that /services give you a list > of > > > > all available webservices in WADL format. > > > > > > Only if a CXFServlet is used. We do block custom services exposing > their > > > own /services. Note when CXFServlet is used it is possible to configure > > it > > > to let "/services" requests pass through but react to some other path > > > value for displaying the services page. > > > > I kind of keep thinking that someday, it might make sense to re-write the > > Jetty stuff to use the CXFServlet directly which would solve this issue. > > Just > > not something I've had time to really pursue or even spend more than a > > passing > > thought on. > > > > Dan > > > > >
