tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Wiederkehr (JIRA)" <tapestry-...@jakarta.apache.org>
Subject [jira] Updated: (TAPESTRY-220) InsertText should accept java.io.Reader in addition to String
Date Tue, 02 Nov 2004 14:15:32 GMT
     [ http://nagoya.apache.org/jira/browse/TAPESTRY-220?page=history ]

Markus Wiederkehr updated TAPESTRY-220:

    Attachment: inserttext.patch

> InsertText should accept java.io.Reader in addition to String
> -------------------------------------------------------------
>          Key: TAPESTRY-220
>          URL: http://nagoya.apache.org/jira/browse/TAPESTRY-220
>      Project: Tapestry
>         Type: New Feature
>   Components: Framework
>     Versions: 3.0.1
>     Reporter: Markus Wiederkehr
>  Attachments: inserttext.patch
> In order to display a relatively big text file from a database its entire content has
to be stored in a String before it can be passed to the InsertText component. This is a waste
of time and memory.
> To solve this problem the InsertText component should accept a java.io.Reader in addition
to a String. Then all the user has to do is create an InputStreamReader and pass it to the
component directly.
> I have applied a patch for Tapestry 3.0.1. It changes to type of the parameter value
from String to Object and performs a runtime test to see if it is a String or a Reader. Of
course an additional parameter could be used if this is not desired.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

View raw message