[
https://issues.apache.org/jira/browse/WICKET-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164966#comment-14164966
]
Andrea Del Bene commented on WICKET-5724:
-----------------------------------------
I also worked with ComponentTag.IAutoComponentFactory, which should be the
standard way to enable queueing inside auto component. I've applied the factory
inside RelativePathPrefixHandler#onComponentTag and it solves the problem of
the issue, but it also creates problems with other
TransparentWebMarkupContainer created by this handler that must not be queued.
Today I will have a look to to Palancher's solution.
[~darkvadaure] to create a patch try to run 'git diff' on your working folder
and put the output into a text file.
> 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
>
>
> 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)
