portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott T Weaver (JIRA)" <jetspeed-...@jakarta.apache.org>
Subject [jira] Created: (JS2-183) Improve the usability of the JetspeedPowerTool
Date Tue, 04 Jan 2005 15:54:12 GMT
Improve the usability of the JetspeedPowerTool

         Key: JS2-183
         URL: http://issues.apache.org/jira/browse/JS2-183
     Project: Jetspeed 2
        Type: Improvement
  Components: Layout  
    Versions: 2.0-dev/cvs, 2.0-M1, 2.0-M2    
    Reporter: Scott T Weaver
 Assigned to: Scott T Weaver 
     Fix For: 2.0-dev/cvs, 2.0-M2, 2.0-FINAL

Currently, the JetspeedPowerTool has to do some very odd things when working with layouts.
 One of the worst is the need to call flush() on the target outpuststream at arbitrary points
in the both the template and the tool itself.  Most of this stems from the way the aggregation/rendering
process works.  The current approach in this process is buffer the rendered content from dispatched
portlet requested to a PrintWriter, which works great.  However, the buffered content is written
straight into the portals outputstream/writer.  This is the main reason why we have to call
flushes as to make sure content gets placed in the correct location.

I have refactored the agg/Render process to write the buffered content into the Fragment object
via a setRenderedContent() method.  To access the rendered content, all that needs to be done
is to call Fragment.getRenderedContent().  This makes developing layout and portlet decorations
easier in that there is no longer a requirement to flush() content.

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: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

View raw message