BTW - the Json Plugin Result has some of this built in without a dependency to beanlib.
On Fri, Feb 15, 2008 at 10:21 AM, Blake Byrnes <[EMAIL PROTECTED]> wrote: > Ok. I think the other nice thing in those stream handlers would be to > handle hibernate objects on the way out. Right now, they just send back the > uninitialized junk that hibernate creates. In my project, I used Beanlib to > run them through a cleaner, but for a slightly different purpose. To really > integrate it with the content handlers though, I think you'd need to be able > to specify properties you want to exclude somewhere. Doing that for a whole > object graph (uses a visitor pattern) is kind of messy in xml though. Which > means you really need something in your models or in some sort of java > package with a config per model object. > > > On Fri, Feb 15, 2008 at 10:11 AM, Wes Wannemacher <[EMAIL PROTECTED]> wrote: > > > On 2/15/08, Blake Byrnes <[EMAIL PROTECTED]> wrote: > > [snip] > > > > > > Just another potential approach. I don't understand the reasoning > > behind > > > the request specs that got posted in the JIRA ticket. > > > > > > > I am not sure about the lengthy discussion either (which was the main > > reason behind not applying my patch earlier). Basically, what I took > > from it is that an IllegalStateException is thrown by the app server > > (Jetty 6.1.6) when the Java/JSP code breaks "the rules" (the spec). > > I've gotten them before when trying to do silly things like redirect > > via HTTP 302 after I've already written to the output stream. In this > > case, I believe that it was tracked down a > > getParameterMap/getParameter call happening before the call to > > getReader. Further digging on google led me to think that if the root > > cause is a call to getInputStream, that a subsequent call shouldn't be > > illegal (or if it is, it does work w/o exception). > > > > Anyhow, I agree that the purpose of the affected code is to > > deserialize JSON/XStream data, so how it happens is probably > > irrelevant. If you want to tweak the code further, patches are always > > welcome. In this case though, start a new JIRA, since the original > > dealt with the exception in Jetty 6.1.6. > > > > > > -- > > Wesley Wannemacher > > President, Head Engineer/Consultant > > WanTii, Inc. > > http://www.wantii.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
