Guten tag, Thorsten! On Thu, Jan 22, 2015 at 10:41 AM, Thorsten Schöning <[email protected]> wrote:
> Hi all, > > I have some AutoComplete Ajax component which I need to integrate with > Wicket. The component mainly gets configured an URL as target of it's > request and expects the server to provide some JSON structure. > > One important thing to note is, that this component is part of a > larger JS app consisting of many more components, with it's own build > tools and integration into the site. So I can't extract that one > component and build a Wicket component or such around it. Instead I > want to keep all like it's is and just want to configure a Wicket > entry point for the component, which than handles the requests and > provides the response. > > From my currently limited knowledge of Wicket I thought of simply > using a ResourceReference which gets mounted to a special URL, > implementing the search logic needed. Because I won't use any > templates or such and just need to provide some JSON. > This is the best approach for your use case! Another way is to create a Component and use it as a context to decide what response to return. See https://github.com/wicketstuff/core/tree/master/jdk-1.7-parent/autocomplete-tagit-parent for such approach. > > Or is there any better approach I should have a look into for any > reason? > > Thanks for your ideas! > > Mit freundlichen Grüßen, > > Thorsten Schöning > > -- > Thorsten Schöning E-Mail: [email protected] > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > Telefon...........05151- 9468- 55 > Fax...............05151- 9468- 88 > Mobil..............0178-8 9468- 04 > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln > AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
