Disclaimer: I have my own POJO solution. I haven't actually used StrutsLive in an application, all I've done so far was read the sample chapter posted on TSS: http://www.theserverside.com/news/thread.tss?thread_id=30690
It seems to me that the author is trying to *change* the way Struts handles requests, as opposed to working *with* it. For one thing, Struts has separate points for validation and conversion, StrutsLive wants to combine these in the name of saving processing cycles. Because StrutsLive is changing the nature of request handling, the changes it implements go much deeper than just your form beans. What worries me is how compatible it will be with future Struts changes/development. On the other hand, Struts is already changing to be much more accomodating to the types of customization that StrutsLive is doing, so this may not be as big an issue as I initially thought it could be. I guess I just didn't agree with the approach he took, but that definitely doesn't mean his approach is wrong or isn't better than mine. It's just a difference of opinion. Since you asked for *opinions*, I'm shared mine. (More of my opinions on the TSS thread, btw.) The way I solved it is with FormDef. It also has a java.net site, which means the page is also down. https://formdef.dev.java.net/ There's another site for it though: http://www.rabago.net/struts/formdef/ FormDef uses standard Struts objects to define form beans that are no different than if you'd defined them yourself using struts-config.xml. You can use them with BeanUtils or FormDef's included converters. Other ways of solving it include using lazy dyna beans and the wrap dyna bean combined with custom date converters for BeanUtils. Now, another project or plugin may not be what you wanted, since you've already integrated it into your app. My advice would be continue to use it since it meets your needs. After all, it may be that none of the existing approaches will meet your needs 100% anyway and carry no risks. IMO we're closer to POJO support being built into Struts Classic than we ever were, and when that point comes, you're gonna be thinking about redoing it all again anyway. Unless of course they decide to just integrate the solution you've already chosen to use. :) Hubert On Wed, 2 Feb 2005 15:17:55 -0600, Jason Long <[EMAIL PROTECTED]> wrote: > The application I am building uses value objects generated from ejbs with > xdoclet in my forms. This was working quite will until I tried to have a > java.util.Date as one of my fields. I recently purchased StrutsLIve. The > project can be found at https://strutslive.dev.java.net/, but it was down at > the time of this email. This addon seems to solve my POJO problem, but I > would like to get others opinions on this. My project is behind schedule > and I cannot afford to have this addon turn out to be limiting after I > integrated it into the many forms I have. I would like any opinions on the > best way to solve this problem. > > Thank you for your time, > > Jason Long > > CEO and Chief Software Engineer Supernova Software > > BS Physics, MS Chemical Engineering > > http://www.supernovasoftware.com <http://www.supernovasoftware.com/> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
