[
https://issues.apache.org/jira/browse/WICKET-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645490#action_12645490
]
Igor Vaynberg commented on WICKET-1911:
---------------------------------------
problem with throwing an exception is that it is hard to tell if we need one.
people write their own request targets that do work with ajax, so how do we
know? a possible solution is to have a tagging interface for ajax targets, but
that gets kinda messy imho.
> setRequestTarget(ResourceStreamRequestTarget) doesn't work with AJAX
> --------------------------------------------------------------------
>
> Key: WICKET-1911
> URL: https://issues.apache.org/jira/browse/WICKET-1911
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-M3
> Environment: Win32 / Tomcat or Jetty
> Reporter: Adriano dos Santos Fernandes
> Assignee: Igor Vaynberg
> Attachments: ajax-resource-redirect.zip
>
>
> In test case attached, you see:
> RequestCycle.get().setRequestTarget(new ResourceStreamRequestTarget(
> new MyWebResource().getResourceStream()));
> doesn't work when clicking the AJAX link. The content is displayed inside the
> AJAX Debug Window instead of redirect the page.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
