No... I think you will have to enumerate the collection.
Or you could use a DTO, databind to that instead, and wire up the
values yourself when you call update.
On Sep 25, 12:41 pm, JakeS <jakesteven...@gmail.com> wrote:
> I've got an object:
> class BillingInfo
> {
> public string BilledToName{get;set;}
> ...
> [HasMany(typeOf(SystemUser)]
> public IList<SystemUser> PaysFor{get;set;}
>
> }
>
> And I need to let the user edit their basic billing information
> without bothering who it pays for, so my controller has an update
> method:
>
> class BillingController
> {
> public void Edit()
> {
> PropertyBag["BillingInfo"] = CurrentUser.BillingInfo;
> }
> public void UpdateBillingInfo( [DataBind("BillingInfo")] BillingInfo
> info)
> {
> info.Update(); //Except info.PaysFor is empty!
> }
>
> }
>
> I'm sure the info.PaysFor is empty because it's not being passed
> through the view, but there's no simple FormHelper method for storing
> all these values, is there?
>
> Should I forget about databinding for this instance and only deal with
> individual values on the view? Or is there a simple way to keep the
> PaysFor values in a hidden field within the view?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Castle Project Users" group.
To post to this group, send email to castle-project-users@googlegroups.com
To unsubscribe from this group, send email to
castle-project-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---
