You can always register a component instantiation listener (or on before render listener etc) in development mode, and let it set markups ids in any way you want to provide stable ids.
E.g. a configure listener, which listens for Page instances and runs a visitor over all it’s components to set the markup id according to some algorithm. Met vriendelijke groet, Kind regards, Bas Gooren Op 6 februari 2017 bij 17:25:21, Entropy (blmulholl...@gmail.com) schreef: Yes, but we have a whole lot of existing pages and fields and links and buttons. I was kind of hoping I could just get wicket's generated IDs to be stable from page run to page run, and avoid getting a work request approved to go back and tweak every field. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Generated-IDs-tp4677000p4677002.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
