Hello John, We use Castor & Struts in our projects. The right way to use Castor is to develop beans to work with entities from the problem domain, develop database structure and mapping configuration. And after that develop your Struts application. Struts' ActionForms are presentation specific classes - a some kind of informational proxy between entity beans and HTML form data from user input. Action classes incorporates business logic and work with Castor to take and store entity beans from/to persistence storage. I think that idea to use ActionForm as beans in Castor mapping is a potential source of problems. ActionForm must store field values between user submits and the best choice for type of properties in ActionForm is java.lang.String. Entity beans can contains any type properties and all values for it you can transfer from the ActionForm with help of BeanUtils.populate() method, which perform automatic conversion of the field values between String values and such types as Data, Integer and so on.
Friday, February 22, 2002, 7:30:12 AM, you wrote: JM> I am considering using Castor as a Persistance mechanism with Struts. Does JM> anyone currently use Castor? Since Castor is desinged to work with any bean JM> like class, to implement castor should I use Castor QQL directly from my JM> ActionForm classes or should there be some kind of redirection from the JM> ActionForm to a more Castor specific class? JM> -john JM> -- JM> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> JM> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- Best regards, Oleg mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
