Vaadin resource loading does not work with Apache Felix Http Jetty 2.2.0
------------------------------------------------------------------------

                 Key: ACE-156
                 URL: https://issues.apache.org/jira/browse/ACE-156
             Project: Ace
          Issue Type: Bug
          Components: Web UI
    Affects Versions: 0.8.0
            Reporter: Bram de Kruijff
            Priority: Minor


The Vaadin WebUI fails when one used the Apache Felix HttpService 
implementation instead of the OPS4J Pax Web implementation because there is a 
difference in how they translate pathinfo. Strictly speaking not an ACE bug, 
guessing Pax Web is correct (although I'm not sure the spec is conclusive), but 
a simple fix would makes ACE more robust and work with both.

Observed behavior:
-> With Pax Web a call to "/VAADIN/themes/ace/styles.css" results in a call on 
the HttpContext with name "/VAADIN/themes/ace/styles.css" which succeeds.
-> With Felix Http a call to "/VAADIN/themes/ace/styles.css" results in a call 
on the HttpContext with name "VAADIN/themes/ace/styles.css" which fails.

Simply adding a startWith check to the getResource implementation would solve 
the issue. Another consideration could be to skip registerResources altogether 
and register a resourceservlet yourself resulting in a consistent use of the 
whiteboard pattern.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to