afs commented on PR #2702: URL: https://github.com/apache/jena/pull/2702#issuecomment-2341461351
> if hypothetically we had two Jena extensions that both wanted to modify these fields :smile: Best I can think of is to check the current value of a slot against the initial system setting. That detects possible conflict. Testing object identity is good enough. Automatically resolving is problematic in the general case with adds and removes of the offer lists because the two subsystems may be have conflicting requirements. Additions could be merged reasonably safely. The Jena initialization mechanisms (Jena System init, Fuseki modules) are both sequential so no concurrent overwrite problems. They can be ordered by level if needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
