It really depends on how you are using your model...So, it looks like you are using a transient object model for form submission and then doing something with the input afterwords to persist the changes? In that case, I would just create a ThemeForm object to submit your data to as opposed to binding directly to a transient model. I really prefer not to model as parameters on controllers.
If you are looking to update your model directly from the form input, you could use the ARDataBinder which will load nested types. I assume that it works with abstract classes assuming you are using a discriminator or joined subclass because all it would need is the ID to know which object to instantiate, but I don't know that for sure as I have not used it. On Sep 10, 9:54 pm, "Jan Limpens" <[EMAIL PROTECTED]> wrote: > On Wed, Sep 10, 2008 at 10:35 PM, Eric Hauser <[EMAIL PROTECTED]> wrote: > > Can't you use the null object pattern to have an object there already? > > You mean, that (in this case) I would instantiate Theme.Kit with new > Concrete1Article(), even if it could be Concrete2 or 3... > While this may work it has 2 disadvantages: 1) it seems like a hack > and 2) most probably NHibernate would want to insert it somehow. Or do > you mean an unmapped class NullArticle? This could somehow work... > > -- > Jan > ___________________www.limpens.com > +55 (11) 3082-1087 > +55 (11) 3097-8339 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
