ok, thanks for the tip
igor.vaynberg wrote: > > much easier to create a generic page that can contain any component, > add it to there, and render the page > > -igor > > On Thu, Oct 2, 2008 at 6:11 PM, metalotus <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> I would like to return the markup of a rendered wicket component when >> accessing a certain URL. I do not want to return a page, only one single >> component in that page (like how AJAX works, kinda). >> >> Here is my plan: >> - Handle the Request >> - Create a new component >> - Add it to the page >> - Call component.renderComponent(); >> - Somehow get a stream from MarkupContainer.getMarkupStream() >> - Use Response.write(InputStream) to return the component markup. >> >> Will that work in your experience? >> -- >> View this message in context: >> http://www.nabble.com/URL-to-fetch-one-component-tp19790610p19790610.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/URL-to-fetch-one-component-tp19790610p19790766.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
