[jira] Updated: (WICKET-2881) Cannot substitute RelativePathPrefixHandler

["bernard (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

bernard updated WICKET-2881:
----------------------------

    Attachment: DirectoryStructure.gif

screen shot of directory structures java and markup

> Cannot substitute RelativePathPrefixHandler
> -------------------------------------------
>
>                 Key: WICKET-2881
>                 URL: https://issues.apache.org/jira/browse/WICKET-2881
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.8
>         Environment: All
>            Reporter: bernard
>         Attachments: DirectoryStructure.gif
>
>
> In IPageSettings
> Get the (modifiable) list of IComponentResolvers.
> List<IComponentResolver> getComponentResolvers();
> This looks very useful and easy indeed, and in Application.init() one can find and remove
> RelativePathPrefixHandler and replace it with a different AbstractMarkupFilter implementation e.g. XRelativePathPrefixHandler.
> But even while the List.remove(Object o) returns true, and the handler appears to be removed, it is still active.
> I don't know why and what holds on to it or what creates a new RelativePathPrefixHandler.
> If I add my XRelativePathPrefixHandler, it is not used.
> Consider
> public class MarkupParser
> public final void appendMarkupFilter(final IMarkupFilter filter)
> {
>     appendMarkupFilter(filter, RelativePathPrefixHandler.class);
> }
> So RelativePathPrefixHandler seems to be something special and I am afraid of other potential complications in case replacement would work.
> Can Wicket be fixed to make a replacement as easy as it appears to be?

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