Re: Issue with a framework dependency on the Party component

[Jacopo Cappellato]

On Jan 29, 2009, at 11:56 PM, Adam Heath wrote:

I am a few days behind, but here is my take on this problem.

Move Party/PartyType to framework; leave Person/PartyGroup in
applications/party(along with the seed data).  The framework then just
deals with some abstract party, it has no idea what the exact kind of
party it is dealiing with.

Party is a *very* low-level critical entity; I don't think we can get
away from not requiring it in framework.

I'd suggest to try to live without it, and postpone the decision.


Jacopo

This is an interesting idea, but I am not sure we will have to go in this direction. In the meantime we may move the common "ERP-oriented" resources to an "applications/appcommon" (another name could be "commonext", to use the same pattern used for security/securityext and entity/entityext) component and leave the common "framework-oriented" ones in the "framework/common" component. Well, initially we should just move to the "applications/appcommon" component the resources that are causing a dependency from the framework to the applications.

smime.p7s
Description: S/MIME cryptographic signature