Static mount would work, additional setting might help if it's not an option :)
On Tue, Nov 22, 2016 at 3:24 PM, Pi P314 <[email protected]> wrote: > https://github.com/wicketstuff/core/blob/master/select2-parent/select2- > examples/src/main/java/org/wicketstuff/select2/WicketApplication.java#L29 > https://github.com/wicketstuff/core/blob/master/select2-parent/select2- > examples/src/main/java/org/wicketstuff/select2/HomePage.java#L158 > > On Tue, Nov 22, 2016 at 9:19 AM, Pi P314 <[email protected]> wrote: > > > you can also use selected to in stateless mode > > > > 1- Mount a resource > > 2- Point you select 2 to that resource. > > > > On Tue, Nov 22, 2016 at 9:16 AM, Rob Audenaerde < > [email protected]> > > wrote: > > > >> (question is also on StackOverflow: > >> http://stackoverflow.com/questions/40736742/wicket-and-wicke > >> t-select2-both-use-pageparameter-q-how-to-solve > >> ) > >> > >> I have a set of PageParameters for my page, one is q (for query). This > >> allows for nice URLs like: > >> > >> http://myapplication/search?q=myquery. > >> > >> But when I have a wicket-select2 component on my page, it initializes > the > >> query for the select2 with the same value of the PageParameter q. > >> > >> This causes the select2 to return an empty list of options, while the > user > >> has not even select anything yet. > >> > >> I know I can change the name of my PageParameters (unfortunately, some > >> clients will have to change urls). Or I can override the methods in > >> select2 > >> that use the q parameter. > >> > >> I wondered if there is a better solution? > >> > >> Thanks! > >> > >> -Rob > >> > > > > > > > > -- > > ================================================================ > > > > Regards, > > > > Pi Cuda > > Web Development with Java/Scala > > Wicket Consultant > > > > > > > > > -- > ================================================================ > > Regards, > > Pi Cuda > Web Development with Java/Scala > Wicket Consultant > -- WBR Maxim aka solomax
