David Sean Taylor wrote:
> Raphael Luta wrote:
>
>>I guess either Jason or David can tell you more on this.
>>
>
> Sorry, I don't know about the patch from Santiago. We are working on getting
> Jetspeed working with the new TDK.
I sent it on May the first. Jon asked me to resubmit following the
coding conventions (I *hate* starting braces in the next line :) ) next
day. I'm resubmitting right now, since I have been reading turbine's
lists very little lately :(
It is just putting a try{} catch () {} around the setBufferSize call in
the turbine.modules.pages.JspPage.java file
An alternative hack could be to set the default buffer size big enough,
so that response never gets committed (something like 100K or 200K
should do). This could be a temporary fix until we get a fixed
turbine.jar in Jetspeed.
OTOH, the error he is seeing is different. In his case, the Servlet
engine does not allow us to retrieve the writer. The patch I sent is for
the case where we are aggregating turbine pages, which try to set the
buffer size after the response is committed (by us).
> We are trying to remove the JetspeedTemplateService and only use the
> TurbineTemplateService.
> Haven't had much time this week (my new contract), but we hope to have it
> fixed over the weekend
>
> -- David
>
>
>>-----Original Message-----
>>From: Raphael Luta [mailto:[EMAIL PROTECTED]]
>>Sent: Friday, May 18, 2001 6:54 AM
>>To: [EMAIL PROTECTED]
>>Subject: Re: Jetspeed (CVS of today) and Orion 1.4.8
>>
>>
>>Andreas Heckwolf wrote:
>>
>>>Hello all,
>>>
>>>I am trying to get Jetspeed running on Orion 1.4.8. Got
>>>
>>latest version of
>>
>>>Jetspeed from CVS this morning. Orion claims that the
>>>
>>Outputstream already had been
>>
>>>retrieved when EcsScreenTag.doStartTag calls getWriter. So
>>>
>>where else
>>
>>>could getWriter get called ? Any hints on how to trace this
>>>
>>would be greatly
>>
>>>appreciated. Below the stack trace. Thanks in advance.
>>>
>>>Andreas
>>>
>>> Exception: java.lang.IllegalStateException:
>>>
>>OutputStream already retrieved
>>
>>If I remember correctly, this was an issue that occurs in the
>>JSP template service
>>in Turbine and Santiago sent a patch to the Turbine list for
>>integration, so I guess
>>this issue will be fixed when the Jetspeed codebase is
>>upgraded to support Turbine 2.1
>>
>>I guess either Jason or David can tell you more on this.
>>
>>--
>>Raphael Luta - [EMAIL PROTECTED]
>>Vivendi Universal Networks - Paris
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
