[
https://issues.apache.org/jira/browse/WICKET-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889708#action_12889708
]
bernard commented on WICKET-2881:
---------------------------------
Thanks Juergen.
Your suggestion works. The outcome is that we get complete separation of
concerns between HTML markup and Java source code which is a great step forward.
Previously this was not possible where one would have to either break resource
links at design time or break the association between markup and java files
which in both cases is terrible for tooling.
Now I can think of writing an IDE plugin that lets me switch between markup and
HTML with a keystroke.
There are plugins that do this, but they work on the assumption that markup is
in the same directory as the Java files. That is a special use case scenario -
most useful for components such as used in the framework itself, where markup
is managed by the Java developer who writes the framework.
> 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, HomePage.html
>
>
> 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.
