[ http://issues.apache.org/jira/browse/OFBIZ-149?page=all ]
Chris Howe updated OFBIZ-149:
-----------------------------
Attachment: necessaryChangeLog.txt
file: necessaryChangeLog.txt
After really thinking it over, I've concluded to myself that a polynary
relationship or a binary relationship where one party acts in multiple,
specific roles or a combination thereof is in fact something different from a
party group. While it is possible to hack OFBiz for my current business needs,
I don't feel that will always be the case as my users become more and more
creative in their uses of OFBiz as an ERP system and will only cause more
dificult integrations in the future. Additionaly the complexity that is shown
throughout the code and the use of an unknown, inconsistantly followed and
apparently arbitrary convention warrants getting rid of the direction
associated with relationships. However, there will be a field present to allow
for this constraint if necessary (PartyRelationshipRole.directionId) and will
be used in the applications that are currently calling for it in specific
instances (ie TaxAuthorityServices.getTaxAdjustments) These services will most
likely drop the need for direction, but I feel that is outside the scope of
this proposed improvement as it requires business logic consideration.
Outlined is the result of files and sections that would need to be looked at
closer as to how they would need to interact with the proposed change. This
was compiled by doing a search of the Applications directory for
"PartyRelationship" (case insensitve) and ignoring results of
PartyRelationshipType by hand. Each of these TODOs need to look a step lower
in the hierarchy (and then again lower if necessary) to ensure a change made
won't effect their functionality. If there are any that someone feels I
missed, please let me know.
> Better describe complex party relationships
> -------------------------------------------
>
> Key: OFBIZ-149
> URL: http://issues.apache.org/jira/browse/OFBIZ-149
> Project: OFBiz (The Open for Business Project)
> Issue Type: Improvement
> Components: party
> Reporter: Chris Howe
> Assigned To: David E. Jones
> Attachments: necessaryChangeLog.txt, PartyRelationship.patch
>
>
> Change to the party data model to support relationships where parties act in
> several capacities (roles) and allowing polynary relationships.
> If someone could describe a situation where the direcition of the role
> matters (partyIdTo/partyIdFrom) and where the roleType is insuficient to
> understand the direction I will try to come up with a solution. I'm trying
> to understand if simply better role designations would alleviate ambiguity or
> if there is a real need to support direction.
> I began a discussion on this topic, there has yet to be any response
> http://mail-archives.apache.org/mod_mbox/incubator-ofbiz-dev/200608.mbox/[EMAIL
> PROTECTED]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
