CSLA BO design for Dundas charts

CSLA BO design for Dundas charts

Old forum URL: forums.lhotka.net/forums/t/5937.aspx


Jayachandran posted on Thursday, December 04, 2008

Hi,

We are developing DUNDAS charts in ASP.Net MVC using CSLA.Net 3.5v.  We need to return certain data like chart's minimun x, y value, maximum x, y value, legend data, x axis data and y Axis data. These all are aggregated from multiple tables. Earlier in plain ASP.Net application we wrote a BL layer which returned all required datas.

In CSLA how should we design the BO for this requirement? Should we have single BO collecting all these data and returning via single dataportal fetch. This will lead to BO being tightly coupled with a specific UI and we will not be able to reuse for some other chart.

If we split each of these data to seperate BOs then that would lead to multiple calls to Dataportal and increase the number of BOs

How should we go about this?

Thanks

Copyright (c) Marimer LLC