[xwiki-devs] PROPFIND on /xwiki/ fails. - xwiki-devs@xwiki.org

Asiri Rathnayake

30 Sep 30 Sep

3:04 p.m.

Hi, Tried many things but still can't find a solution. One thing possible is to make xwiki-webdav a separate servlet. Then we would have, webapps | |--root (for redirecting) |--xwiki (xe) |--xdav (xwiki-webdav) This way we can keep xwiki-webdav and it's configuration separate from xe, yet providing access to XE repository via hibernate configuration file. I haven't deeply looked into this approach yet though. Any other ideas ? - Asiri On Tue, Sep 30, 2008 at 4:02 PM, Asiri Rathnayake < asiri.rathnayake(a)gmail.com> wrote:

...

Hi Devs, Ludovic, I'm faced with the following problem, Currently xwiki-webdav is deployed under /xwiki/webdav/*. And for this to work, we need PROPFIND method to work correctly on following locations { "/" , "/xwiki/" , "/xwiki/webdav/*". } For "/" i have written a separate xwiki-rootwebapp and it works fine. For "/xwiki/" and "/xwiki/webdav/*" I had defined the following servlet mapping elemnts : <servlet-mapping> <servlet-name>xwiki-webdav</servlet-name> <url-pattern>/</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>xwiki-webdav</servlet-name> <url-pattern>/webdav/*</url-pattern> </servlet-mapping> Everything was working fine but lately i discovered that none of the static content is being served correctly. This is because of the first mapping on "/", this seems to overrride the default servet of the container (which serves static files). Without the first mapping some webdav clients fail because they think the url is not a webdav one. I'm really stuck here and can't think of a solution, if you have any ideas please let me know. Thanks a lot. - Asiri

Reply

Asiri Rathnayake

1 Oct 1 Oct

7:31 p.m.

Hi All, I was finally able to get around this problem by using a Filter. For some reason I refused to use a filter earlier. But mighty vincent came to the rescue and cleared my head! ;) Now everything is working fine and i'm back on track :) Also, it seems like i have been a little ambiguous with the presentation of the problem itself. I will do my best to make sure this doesn't happen agian :) Thanks. - Asiri On Tue, Sep 30, 2008 at 11:22 PM, Asiri Rathnayake < asiri.rathnayake(a)gmail.com> wrote:

...

Hi All, As suggested by Sergiu, i looked into writing a custom DefaultServlet that would let us serve the static resources (super.service()) while being able to respond to requests at webapp root as we prefer. I have contacted Lilianne about this issue and he seems to have a proof-of-concept DefaultServlet implementation ( http://markmail.org/message/snu2zxda464oyshv) and he is willing to provide us the source :) But having said that, i'm bit unsure if we should use a custom DefaultServlet or not. One reason is that Lilianne's implementation is not complete (no caching of static resources according to him) and it would take more time to get it upto production level. And i'm generally worried about the fact that there is no widely used such DefaultServlet that works across all containers (There might be a good reason for this). Anyway, i would like to know if there are negative impacts on having a separate webdav servlet as i proposed. If you have any comments please enlighten me :) Thanks. - Asiri On Tue, Sep 30, 2008 at 6:34 PM, Asiri Rathnayake < asiri.rathnayake(a)gmail.com> wrote:

Hi, Tried many things but still can't find a solution. One thing possible is to make xwiki-webdav a separate servlet. Then we would have, webapps | |--root (for redirecting) |--xwiki (xe) |--xdav (xwiki-webdav) This way we can keep xwiki-webdav and it's configuration separate from xe, yet providing access to XE repository via hibernate configuration file. I haven't deeply looked into this approach yet though. Any other ideas ? - Asiri On Tue, Sep 30, 2008 at 4:02 PM, Asiri Rathnayake < asiri.rathnayake(a)gmail.com> wrote:

Hi Devs, Ludovic, I'm faced with the following problem, Currently xwiki-webdav is deployed under /xwiki/webdav/*. And for this to work, we need PROPFIND method to work correctly on following locations { "/" , "/xwiki/" , "/xwiki/webdav/*". } For "/" i have written a separate xwiki-rootwebapp and it works fine. For "/xwiki/" and "/xwiki/webdav/*" I had defined the following servlet mapping elemnts : <servlet-mapping> <servlet-name>xwiki-webdav</servlet-name> <url-pattern>/</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>xwiki-webdav</servlet-name> <url-pattern>/webdav/*</url-pattern> </servlet-mapping> Everything was working fine but lately i discovered that none of the static content is being served correctly. This is because of the first mapping on "/", this seems to overrride the default servet of the container (which serves static files). Without the first mapping some webdav clients fail because they think the url is not a webdav one. I'm really stuck here and can't think of a solution, if you have any ideas please let me know. Thanks a lot. - Asiri

Reply

Asiri Rathnayake

11:07 a.m.

On Thu, Oct 2, 2008 at 12:27 PM, Vincent Massol <vincent(a)massol.net> wrote:

...

On Oct 1, 2008, at 7:31 PM, Asiri Rathnayake wrote:

Hi All, I was finally able to get around this problem by using a Filter. For some reason I refused to use a filter earlier. But mighty vincent came to the rescue and cleared my head! ;) Now everything is working fine and i'm back on track :)

Good news.

New xwiki-webdav test installation is available at : http://91.121.237.216/xwiki/bin/view/Main/ Thanks. - Asiri

...

Thanks -Vincent

Also, it seems like i have been a little ambiguous with the presentation of the problem itself. I will do my best to make sure this doesn't happen agian :) Thanks. - Asiri On Tue, Sep 30, 2008 at 11:22 PM, Asiri Rathnayake < asiri.rathnayake(a)gmail.com> wrote:

Hi All, As suggested by Sergiu, i looked into writing a custom DefaultServlet that would let us serve the static resources (super.service()) while being able to respond to requests at webapp root as we prefer. I have contacted Lilianne about this issue and he seems to have a proof-of-concept DefaultServlet implementation ( http://markmail.org/message/snu2zxda464oyshv) and he is willing to provide us the source :) But having said that, i'm bit unsure if we should use a custom DefaultServlet or not. One reason is that Lilianne's implementation is not complete (no caching of static resources according to him) and it would take more time to get it upto production level. And i'm generally worried about the fact that there is no widely used such DefaultServlet that works across all containers (There might be a good reason for this). Anyway, i would like to know if there are negative impacts on having a separate webdav servlet as i proposed. If you have any comments please enlighten me :) Thanks. - Asiri On Tue, Sep 30, 2008 at 6:34 PM, Asiri Rathnayake < asiri.rathnayake(a)gmail.com> wrote:

Hi, Tried many things but still can't find a solution. One thing possible is to make xwiki-webdav a separate servlet. Then we would have, webapps | |--root (for redirecting) |--xwiki (xe) |--xdav (xwiki-webdav) This way we can keep xwiki-webdav and it's configuration separate from xe, yet providing access to XE repository via hibernate configuration file. I haven't deeply looked into this approach yet though. Any other ideas ? - Asiri On Tue, Sep 30, 2008 at 4:02 PM, Asiri Rathnayake < asiri.rathnayake(a)gmail.com> wrote: > Hi Devs, Ludovic, > > I'm faced with the following problem, > > Currently xwiki-webdav is deployed under /xwiki/webdav/*. And for > this to > work, we need PROPFIND method to work correctly on following > locations { "/" > , "/xwiki/" , "/xwiki/webdav/*". } For "/" i have written a > separate > xwiki-rootwebapp and it works fine. For "/xwiki/" and "/xwiki/ > webdav/*" I > had defined the following servlet mapping elemnts : > > <servlet-mapping> > <servlet-name>xwiki-webdav</servlet-name> > <url-pattern>/</url-pattern> > </servlet-mapping> > > <servlet-mapping> > <servlet-name>xwiki-webdav</servlet-name> > <url-pattern>/webdav/*</url-pattern> > </servlet-mapping> > > Everything was working fine but lately i discovered that none of > the > static content is being served correctly. This is because of the > first > mapping on "/", this seems to overrride the default servet of the > container > (which serves static files). Without the first mapping some > webdav clients > fail because they think the url is not a webdav one. > > I'm really stuck here and can't think of a solution, if you have > any > ideas please let me know. > > Thanks a lot. > > - Asiri >

_______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Reply