I am using PipedInputStream and PipedOutputStream to convert a large
OutputStream to StreamResponse, that needs a new thread.
For me, there is no problem with the new approach, just want framework
which is already very great to be perfect.
Yunhua
On Mon, Sep 27, 2010 at 4:57 PM, Howard Lewis Shi
True, there are some leaky abstractions related to the new approach;
there was a different set in the 5.1 version of the page lifecycle.
I've never felt the need to start up a thread from the middle of a
page. I'm curious what your use case is, and whether it wouldn't be
better handled
using Thre
Hi Thiago,
Thanks for your response. Yes, the code looks not nice, however, there
is nothing wrong with it. I knew there was a refactoring of changing
pool to singleton recently, so I was able to come up with a workaround
quickly, but for a Tapestry newbie, he/she might not know what's going
on, t
On Mon, 27 Sep 2010 16:47:38 -0300, Yunhua Sang
wrote:
Hi everyone,
Hi!
The field is always null when printing it out within run method; a
workaround is to define a local variable then access this variable in
new thread.I am wondering whether it's an expected behaviour or not.
It's expe
Hi everyone,
I am using 5.2.1-SNAPSHOT.
I found a new thread in page class has problem to access the persisted
fields, for example:
@Persist
@Property
private String field;
public void onSubmit() {
try {
Thread thread = new Thread() {
public v
