have a look at the migration page 1.5 $ component rendering
https://cwiki.apache.org/WICKET/migration-to-wicket-15.html#MigrationtoWicket1.5-Componentrendering
François Meillet
Formation Wicket - Développement Wicket
Le 13 févr. 2013 à 15:08, Martin Dietze <d...@fh-wedel.de> a écrit :
> I am currently migrating a project based on Wicket 1.4 to 6.60.
> At some point in that project we have this code:
>
> | class Foo extends Panel {
> | // ...
> | private boolean hasFragment( final String fragmentId, final MarkupStream
> markupStream ) {
> | final boolean found = markupStream.findComponentIndex( null, fragmentId
> ) >= 0;
> | return found;
> | }
>
> This code is used to find if the markup stream for this component
> contains the markup for a fragment with the given id. If found,
> this markup is used for initialising an inner fragment class
> with this markup.
>
> Using a self-defined scheme for defining the Wicket markup ids,
> this is used for allowing our HTML authors to define specialised
> views for a group of model objects (e.g. a creature has a
> generic view while cats and dogs have their own ones).
>
> Now the findComponentIndex method has disappeared from
> MarkupStream.
>
> How can I do what I used to do in Wicket 6.60?
>
> Cheers,
>
> M'bert
>
> --
> ----------- / http://herbert.the-little-red-haired-girl.org / -------------
> =+=
> while (!asleep)
> ++sheep;
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
