[
https://issues.apache.org/jira/browse/OFBIZ-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17441017#comment-17441017
]
Michael Brohl commented on OFBIZ-5980:
--------------------------------------
A first step could be that you refrain from distracting commiters by opening so
many sidelines, accusations etc., just look at the comment history in this Jira
alone.
Second, provide more quality-assured code and be open to rework it if asked by
a committer.
Third, be patient and less offensive. Putting pressure onto committers does not
help to deliver quality-assured code to the codebase. In the worst case, they
are simply not willing to work on those issues.
These are my personal views and suggestions, maybe not complete but coming to
my mind first. Maybe they help to reflect. I do not intend to discuss them
further. Thanks.
> Have the ability to revoke (expire) roles of a party
> ----------------------------------------------------
>
> Key: OFBIZ-5980
> URL: https://issues.apache.org/jira/browse/OFBIZ-5980
> Project: OFBiz
> Issue Type: Bug
> Components: party
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Pierre Smits
> Priority: Major
> Labels: roles
> Fix For: Upcoming Branch
>
>
> Currently it is only possible to delete a PartyRole record from a party.
> Which leads to error messages, when that particular Partyrole record is
> associated with records in other entities where the PartyRole entity is set
> as a relation (through <relation rel-entity-name="PartyRole"> which is
> applied as a foreign key relation in the underlying dbms ).
> Examples of such related entities that are:
> * entity-name="MarketingCampaignRole"
> * entity-name="BudgetRole"
> In order to avoid such, it is better to revoke the PartyRole record by
> setting an expiration date (end date) on the record.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
