Provide configurable extensible mechanism for determining the delegate module for a incoming request

[GoogleCodeExporter]

As of r3515:

Currently, the module name is determined using the first part of the URL
after the context path.

For example, in the URL:

http://localhost:8080/mywebapp/mymodule/theRestOfThePath

mymodule is interpreted as the name of the application module.

It would be good to have a chain of responsibility for determining this,
with the chain of responsibility wired in via the Impala configuration.

This would make it easier to support frameworks such as Tapestry which are
more sensitive to how the URL path is interpreted.

Original issue reported on code.google.com by philzoio...@googlemail.com on 8 Jan 2009 at 9:31

[GoogleCodeExporter]

Original comment by philzoio...@googlemail.com on 8 Jan 2009 at 9:31

• Added labels: Milestone-Release1.0M5

[GoogleCodeExporter]

Note that there is already an interface present for this: RequestModuleMapper.

Idea now would be to wire this into the Impala application context, and provide 
a more intelligent 
implementation of this.

Original comment by philzoio...@googlemail.com on 9 Jan 2009 at 9:17

[GoogleCodeExporter]

As of r3544, this is currently set up for tapestry and wicket.

However, does require the prefix to be the full module path of suffix. For 
example, the suffix is tapestry5, which 
means that a Tapestry 5 page must start with the (case insensitive) Tapestry5. 
Would be good if you could start 
it with Tap, for example. However, will leave it there for now.

Original comment by philzoio...@googlemail.com on 14 Jan 2009 at 6:08

• Changed state: Fixed