Hi, There are few very good integrations between Wicket and JQuery UI. Check https://github.com/sebfz1/wicket-jquery-ui and https://github.com/WiQuery/wiquery Both of them provide autocomplete component.
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Sat, Dec 13, 2014 at 7:50 PM, Andrea Del Bene <[email protected]> wrote: > > Hi, > > I suggest you to use a resource instead of an adapted stateless page. > Wicketstuff has a module with special Wicket resources to implement REST > api: https://github.com/wicketstuff/core/tree/master/ > jdk-1.7-parent/wicketstuff-restannotations-parent. Here you can find > resources that already produce JSON in output. > To configure them you might use a Wicket initializer: > http://wicket.apache.org/guide/guide/single.html#advanced_3 > > Hi all, >> >> I am making an autocomplete component based on jquery-autocomplete. >> >> I have currently implemented the data source using a stateless web page >> which writes the json response. >> >> What I don't like about this is that it is a separate file/class from my >> autocomplete component. But I like that it's stateless. >> >> Could I achieve the same effect (statelessness) using a dynamic resource >> registered/created from within the autocomplete component? In other words >> I >> want the autocomplete component, upon creation, to register a resource >> that >> can be used to serve the autocomplete options. But I want the resource to >> be stateless and lightweight and the requests to return the autocomplete >> options should not have to go through the page that contains the >> autocomplete component. >> >> Furthermore, if I have the same autocomplete component twice in a page, >> the >> resource should be registered only once and server requests for both >> components. >> >> Is this possible? Can you provide some guidelines? >> >> Thanks >> Marios >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
