I'm sorry for not having been in touch in the last days but I was on
vacancy. Yes, MountMapper should take care of placeholders but I think
that there is a problem with it. I've created a new issue to illustrate
the problem and share my thoughts about it.
https://issues.apache.org/jira/browse/WICKET-4686
According to org.apache.wicket.protocol.http.WebApplication#mountPackage()
public final <P extends Page> void mountPackage(final String path,
final Class<P> pageClass)
{
PackageMapper packageMapper = new
PackageMapper(PackageName.forClass(pageClass));
MountMapper mountMapper = new MountMapper(path, packageMapper);
mount(mountMapper);
}
this should be already handled.
MountMapper is the one that deals with the placeholders.
On Mon, Jul 23, 2012 at 4:41 PM, Andrea Del Bene <[email protected]> wrote:
Unlike MountedMapper, PackageMapper doesn't support parameter placeholders.
Was it made like this on purpose? Is there any problem or risk porting this
feature to PackageMapper?
