[
https://issues.apache.org/jira/browse/WICKET-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680782#comment-14680782
]
Palancher aurélien edited comment on WICKET-5962 at 8/10/15 9:20 PM:
---------------------------------------------------------------------
i've just tried a thing : remove the test of emptyness of queue when detaching
a component (in onDetach() in MarkupContainer.java)
it works.
Even if this solution is not included in next release, i will try it in my Web
application, i don't know if it works in all kinds of components...
i will also try this solution : parsing the IQueueRegion markup to find the
component. if not found => throw exception.
was (Author: darkvadaure):
i've just tried a thing : remove the test of emptyness of queue when detaching
a component (in onDetach() in MarkupContainer.java)
it works.
Even if this solution is not included in next release, i will try it in my Web
application, i don't know if it works in all kinds of components...
> Queuing : test existance of components in markup
> ------------------------------------------------
>
> Key: WICKET-5962
> URL: https://issues.apache.org/jira/browse/WICKET-5962
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 7.0.0
> Reporter: Palancher aurélien
> Priority: Minor
> Attachments: WicketQuickstart2.war
>
>
> In my Web Application, i can have many html files associated to one component
> Java class. eg CompTest.java and CompTest.html, CompTest_1.html.
> Each of html files contains all or only a part of the wicket components
> queued in the Java class.
> In the 7.0.0 version, it seems that this case doesn't work (or i may be wrong
> ?) It would be great to have the possibility to queue a component even if the
> markup doesn't contain it.
> My 6.x Wicket application works fine this way.
> Simple example : a cart component (cart.html) that can show many details
> before validating, or the same Java class with a cart_1.html which is the
> minified version you can see on the top of the site.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
