Thanks for the pointer to using request mappers and the continuing updates to WicketInAction which are very useful.
After some more work I've then solved my next problem of returning an 'on the fly' XML response using extended ResourceReference & ByteArrayResource classes. This is also very different to the solution in 1.4 where I overrode URIRequestTargetUrlCodingStrategy.decode() returning a new ResourceStreamRequestTarget. Can you suggest a way of understanding the relationships of these many classes and the best way of choosing a solution? I apologise for such an open question but at the moment I seem to spend a long time Googling until I get a hint of a way forward. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/What-s-replaced-org-apache-wicket-request-target-basic-URIRequestTargetUrlCodingStrategy-in-1-5-tp4091780p4100321.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
