[
https://issues.apache.org/jira/browse/WICKET-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169128#comment-14169128
]
Andrea Del Bene edited comment on WICKET-5724 at 10/13/14 9:44 AM:
-------------------------------------------------------------------
As side note: I see that there are some classes (like
RelativePathPrefixHandler) that implement both IMarkupFilter and
IComponentResolver. Although this is not a problem per se, I thing it can be
confusing and might lead to future problems because IMarkupFilter
implementations don't need to be thread safe while IComponentResolverS have to
(they are registered at application level inside Application#internalInit()).
was (Author: bitstorm):
As side note: I see that there are some classes (like
RelativePathPrefixHandler) that implement both IMarkupFilter and
IComponentResolver. Although this is not a problem per se, I thing it can be
confusing and might lead to future problems because IMarkupFilter
implementations don't need to be thread safe while IComponentResolverS have to.
> Queueing component in autocomponent
> -----------------------------------
>
> Key: WICKET-5724
> URL: https://issues.apache.org/jira/browse/WICKET-5724
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.0.0-M3
> Reporter: Palancher aurélien
> Assignee: Andrea Del Bene
> Attachments: queueing-problem.zip, queueing-solution.zip,
> wicket5724.patch
>
>
> There is an exception when a component is added to queue when its parent is
> an auto component
> <body>
> <a href="panier.html">
> <span wicket:id="inlink"></span>
> </a>
> </body>
> Last cause: Unable to find component with id 'inlink' in
> [TransparentWebMarkupContainer [Component id = wicket_relative_path_prefix_1]]
> Expected: 'wicket_relative_path_prefix_1:inlink'.
> Found with similar names: ''
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
