> If you add a Page to AjaxRequestTarget then Wicket will produce a redirect > Ajax response.
I don't do that. Just adding a single component. > You can use getResponse().write(...) to write raw response instead. This was my first try in combination with ComponentRenderer.renderComponent(myComponent). But I get problems with urls. Some image urls are broken with "ComponentNotFoundExceptions". renderComponent(myComponent) also writing logs, its not a good idea, what I'm doing. ;-) So I changed my implementation to the current way using AjaxRequestTarget. Patrick Health AG | Patrick Davids | Softwareentwickler Tel. +49 40 524 709-258 | [email protected] Fax +49 40 524 709-258 | www.healthag.de EOS Health Honorarmanagement AG | Lübeckertordamm 1–3 | 20099 Hamburg | AG Hamburg HRB 93806 Vorstand | Jens Törper, Uwe Schäfer Aufsichtsratsvorsitzender | Klaus Engberding Save a tree – think before you print. -----Ursprüngliche Nachricht----- Von: Martin Grigorov [mailto:[email protected]] Gesendet: Montag, 18. Juli 2016 13:29 An: [email protected] Betreff: Re: Returning pure HTML using AjaxRequestTarget Hi, If you add a Page to AjaxRequestTarget then Wicket will produce a redirect Ajax response. I am not sure how far you can go with AjaxRequestTarget#add() though. You can use getResponse().write(...) to write raw response instead. Or schedule another IRequestHandler to render the response, as in https://github.com/wicketstuff/core/blob/793d2cbaa97d6f2650b9f5ababb7e46226c4b716/autocomplete-tagit-parent/autocomplete-tagit/src/main/java/org/wicketstuff/tagit/TagItAjaxBehavior.java#L50 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jul 18, 2016 at 1:16 PM, Davids Patrick <[email protected]> wrote: > Hi all, > I'm working on a integration of a javascript which does html > replacements by itself. > > So, it expects pure HTML and what I try to achieve is, becoming wicket > returning the HTML via AjaxRequest.add(...). > > I've seen the methods setDataType("html") and > setWicketAjaxResponse(false) of AjaxRequestAttributes. > I thought this would be the solution. Just getting a html snippet not > processed by wickets client-side ajax features. > > My problem now is, I don't get a html part, but an redirect 302 > pointing to a url which returns the entire webpage. > > Where does this 302 come from? > And why does it point the page url? > How can I change that behavior, so just returning the html snippets of > components added to the AjaxRequestTarget? > > Thanx for help! > kind regards > Patrick > > Health AG | Patrick Davids | Softwareentwickler Tel. +49 40 524 > 709-258 | [email protected] Fax +49 40 524 709-258 | > www.healthag.de > > > EOS Health Honorarmanagement AG | Lübeckertordamm 1–3 | 20099 Hamburg > | AG Hamburg HRB 93806 Vorstand | Jens Törper, Uwe Schäfer > Aufsichtsratsvorsitzender | Klaus Engberding > > Save a tree – think before you print. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
