Hi, I have two projects now. One with working StreamResponse returned from event handler and another project which throws that weird exception.
There is Tapestry version 5.3.6 in both projects. It does not seem to be an issue of a particular servlet container. It's Jetty 6.1.26 in both cases. Moreover, I reproduced the exception with Tomcat 6.0.36. I have tried to move all relevant differences in web.xml from the working project to the broken one. It does not help either. I am not sure if it's worth to create a JIRA issue as it is probably not a bug in Tapestry. It's rather a bad configuration of my project. To be honest, I have no idea what to try next. (I have already made some workaround. However, I am instrested in the purpose anyway.) Cimlman ______________________________________________________________ > Od: Thiago H de Paula Figueiredo <thiag...@gmail.com> > Komu: Tapestry users <users@tapestry.apache.org> > Datum: 26.09.2013 18:43 > Předmět: Re: StreamResponse an EventLink > >On Thu, 26 Sep 2013 11:35:57 -0300, Jaroslav Ciml <ci...@centrum.cz> wrote: > >> Hi, > >Hi! > >> I am using Tapestry version 5.3.6. > >I tested it on 5.4-alpha-22. > >> This exception is thrown if I return a StreamResponse instance from an >> event link handler (i.e. the request URL contains something like >> :eventname). Everything is OK if I return the same StreamResponse >> instance from onActivate method. >> >> It also occurs only for "short" responses. The response is sent with >> Content-Encoding: chunked. >> The chunks have 0x6000 bytes. If the total byte count returned by >> StreamResponse.getStream() is less than 0x6000, this exception occurs. >> No exception is thrown for 0x6000 bytes or more. >> >> In ImmediateActionRenderResponseFilter.handle, the call >> response.isCommitted() returns true for "long" response but it returns >> false for "short" response. > >Weird. JIRA please? :) > >> Well, I tried to paste the event handler to completely different project >> with the same Tapestry version ...and it works. > >Weird. Which other version? > >> It can be some configuration issue. > >Yeah, that's what I was thinking. Different servlet container? > >-- >Thiago H. de Paula Figueiredo > >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
