You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2016/02/22 14:45:19 UTC

[jira] [Updated] (TAP5-1891) tapestry should include more streamresponse implementations

     [ https://issues.apache.org/jira/browse/TAP5-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-1891:
---------------------------------
    Labels: bulk-close-candidate  (was: StreamResponse)

This issue affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent version of Tapestry (currently 5.4.0, available from Maven Central), please update it as soon as possible and add '5.4.0') to the issue's affected versions.

> tapestry should include more streamresponse implementations
> -----------------------------------------------------------
>
>                 Key: TAP5-1891
>                 URL: https://issues.apache.org/jira/browse/TAP5-1891
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3.2
>            Reporter: Paul Stanton
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> like TextStreamResponse, tapestry should also include other common usages of StreamResponse such as AssetStreamResponse and FileStreamResponse etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)