Its a good question and what I would say is... * no ones objected to the change and it is in the Struts 1.2.4 release which is being voted on now. There are no guarantees for the future but the convention in Struts is that we maintain backward compatibility and IMO someone would have to have good reason to remove it and break compatibility once it has been "released"- at least in the 1.x.x series (Struts 2.0 revolution is another case).
* the critical change for wrapping POJO's was actually before the POJO behaviour was added - it was changing the FormBeanConfig to be effectively a factory class for ActionForms (see revsion 1.14 of FormBeanConfig). What this means is that even in your worst case scenarion (i.e. the POJO behaviour was removed) then it would be simple to create your own custom FormBeanConfig, implement this POJO behaviour in its createActionForm() method and configure Struts to use your custom implementation. Niall ----- Original Message ----- From: "bryan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 17, 2004 3:05 PM Subject: wrapping of POJO's with WrapDyanBean > Hello and sorry to disturb everyone, > > I want to use Niall Pemberton's wrapping on POJO's addition to > struts for my application. > > I personally see it as a great idea that removes one of the main > reasons why I might use spring over struts ie having to inherit > from ActionForm or whatever. > > However before I commit to this approach and start coding > my application arround it I have to ask the question. > > Is it an accepted change and does struts team intend to preserve > this change going forward ? > > --b --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
