On Jan 26, 2009, at 3:09 AM, Jacopo Cappellato wrote:
On Jan 26, 2009, at 7:14 AM, David E Jones wrote:
I think of the BI stuff as being very like where we are going with
themes and portal and such. The framework has infrastructure and
the applications and such plugin to that infrastructure (through
whatever means make the most sense).
For BI that would mean all of the tools (including UI) go in the
framework, as long as they do not depend on anything in
applications, and that data and services and more custom UI and so
on go in the applications or specialpurpose components.
That will probably require splitting some of the POC stuff that
Jacopo did into different components...
David, I totally agree, this is the plan. By the way, I already did
the split, apart for the last service named quickInitDataWarehouse
that I am not sure where to move... but it can be removed as well,
for now it is just easier to test the BI features with it.
That service is a good example of one that is a handy feature, and
that would be nice to always have, but written as-is would have
undesirable dependencies. The first solution that comes to mind is to
parameterize it in a way that higher level components can add to,
preferably without anything changed in any framework component...
which means the database might be most natural place for the info
(like some kind of list of services to run to init data warehouse data).
-David
