RE: [Tapestry 4.1] UTFDataFormatException in RequestCycle.encodeIdState

2009-08-15 Thread Woozy
In digging into the source of ObjectOutputStream, (1.6.0_11) this appears to be the best option anyway - if writeUnshared() is called with a String, it eventually calls a method writeString() that does the UTF length check and calls a special "writeLongUTF()" method on the backing BlockDataOutputS

Re: [Tapestry 4.1] UTFDataFormatException in RequestCycle.encodeIdState

2009-07-07 Thread Howard Lewis Ship
hip [mailto:hls...@gmail.com] > Sent: Thursday, July 02, 2009 4:27 PM > To: Tapestry users > Subject: Re: [Tapestry 4.1] UTFDataFormatException in > RequestCycle.encodeIdState > > That's an unexpected limitation! > In exceptional cases, you can revert to simpler methods; for ins

RE: [Tapestry 4.1] UTFDataFormatException in RequestCycle.encodeIdState

2009-07-06 Thread Aaron Kaminsky
From: Howard Lewis Ship [mailto:hls...@gmail.com] Sent: Thursday, July 02, 2009 4:27 PM To: Tapestry users Subject: Re: [Tapestry 4.1] UTFDataFormatException in RequestCycle.encodeIdState That's an unexpected limitation! In exceptional cases, you can revert to simpler methods; for instance, using

Re: [Tapestry 4.1] UTFDataFormatException in RequestCycle.encodeIdState

2009-07-02 Thread Howard Lewis Ship
That's an unexpected limitation! In exceptional cases, you can revert to simpler methods; for instance, using a simple rather than a TextField component, and handling that part of the submission inside your listener method much like a traditional servlet. As a stop-gap, you should give explicit j