TapestryFilter throws IllegalArgumentException if request path for non-Tapestry 
page contains '.' or ':'
--------------------------------------------------------------------------------------------------------

                 Key: TAPESTRY-1595
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1595
             Project: Tapestry
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.0.5
            Reporter: Douglas Hauge


For pages not handled by Tapestry, it should pass control along to next filter 
in chain, which it does for paths that do not contain '.' or ':'. For example, 
if '/foo/bar' is not a page recognized by Tapestry, a URI with the path 

/foo/bar/image.gif

will cause an 'IllegalArgumentException' with the message 'Unable to resolve 
page 'foo/bar/image' to a known page name. ...'

while

/foo/bar/image_gif

will be properly forwarded to the filters after TapestryFilter.

The problem seems to be that 'ComponentActionDispatcher' will attempt to 
process any path that contains '.' or ':', unlike 'PageRenderDispatcher' which 
explicitly checks that it recognizes a prefix of the path.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to