我有一个包含以下类的 MVC2 应用程序：
-OrderModel
-LineOrderModel
-OrderController
-LineOrderController
在 OrderController 类中，我正在收集 Web 表单的一些值。到目前为止，我在控制器内部创建了每个订单行（LineOrderModel 类）和 OrderClass 的实例。
我试图创建一个 OrderFacade 类，以便封装创建订单时要做的不同事情。
所以在那个类中我创建了一个像这样的方法：
public void saveOrder(int idProvider,decimal? price)
{
// Here I create instances of OrderModel and LineOrderModel
// and assign their properties
}
但我的问题是我不知道如何传递从网络表单捕获的所有订单行。
我认为创建带有 orderLines 类的 List 并将其传递给该方法是没有意义的（因为这样做的目的是与 Facade 一起操作，而不是直接与该类一起操作）
我如何封装不同的行（都带有属性像 numberUnits,idProduct ...) 到一个通用对象列表中，每个对象都具有这些属性？
也许类似于 List> ？
提前致谢！
I have an MVC2 application with the following classes:
-OrderModel
-LineOrderModel
-OrderController
-LineOrderController
In the OrderController class I'm recollecting some values of a web form . Until now, I created instances of each order line (LineOrderModel class) and OrderClass inside of the Controller.
I was trying to create a OrderFacade class in order to encapsulate the different things to do when creating an order.
So in that class I created a method like this:
public void saveOrder(int idProvider,decimal? price)
{
// Here I create instances of OrderModel and LineOrderModel
// and assign their properties
}
but my problem is I don't know how to pass all the order lines captured from the web form.
I think it doesn't make sense to create and pass to that method a List with orderLines class (because the point of this is to operate with the Facade, not with the class directly)
How could I encapsulate the different lines (all with properties like numberUnits,idProduct ...) into a List of generic objects, each one with these properties?
Maybe something like a List<List<object>> ?
Thanks in advance!
发布评论
评论（1）
听起来你不需要门面。如果您在业务逻辑和应用程序逻辑（控制器）之间使用数据传输对象（DTO），Facade 将是一个不错的选择 - 在这种情况下，DTO 也可以是视图模型（我猜正统的 MVC 开发人员不会喜欢这个想法）。 Facade 将采用 DTO 并将它们转换为一些业务或域对象。
但在您的场景中，您只需将数据直接填充到模型类中 - 这是视图模型类在视图和控制器中使用它们的目的。使用任何类型的属性包将数据从控制器传输到业务逻辑都不是一个好的解决方案。
Sounds like you don't need facade. Facade would be good choice if you use data transfer objects (DTOs) between your business logic and application logic (controllers) - in such scenario DTOs can also be view models (I guess orthodox MVC developers will don't like this idea). Facade would take DTOs and convert them into some business or domain objects.
But in your scenario you simply need to fill data directly to your model classes - that is purpose of view model classes to use them in views and controllers. Using any kind of property bags to transfer data from controller to business logic is not a nice solution.