Well, what I got from the "error" description was that if the servlet registers to "/" and a requests calls "/"+"a/b/c" it ends up with a error as described in http://issues.ops4j.org/browse/PAXWEB-108, which I just fixed yesterday, following the proposal from the attached mailing list. It works now (haven't uploaded the latest version to the repo yet). For me it is OK since I did fix a previously known bug. If it is still an issue it might be an issue with CXF then.
regards, Achim 2011/2/2 Niclas Hedhman <[email protected]>: > On Sun, Jan 30, 2011 at 5:02 PM, Rice Yeh <[email protected]> wrote: >> Hi, >> Hi, >> I just find that registering servlet from apache cxf, CXFNonSpringSerlvet, >> to alias "/" will cause problem when running on Pax Web. The problem is that >> the method getBaseAddress(Message) in org.apache.cxf.jaxrs.utils. >> HttpUtils class will wrongly return the the request address ("a/b/c") >> appended with "/", that is ("a/b/c/"), instead of the correct servlet path >> ("/"). I think that this is more likely a bug of Pax Web because there is >> no such probem when running on felix's own http service implementation >> org.apache.felix.http.bundle. > > Don't be too quick to compare with Felix own Http service, since one > of the reasons Pax Web was created was because Felix http service did > not follow the OSGi Http Service specification (which may or may not > have been corrected). > > Also, I don't understand the 'problem'. How can a method call in CXF > be a bug in Pax Web? > > > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/3xugrbk > I work here; http://tinyurl.com/24svnvk > I relax here; http://tinyurl.com/2cgsug > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
