[JSON_PROCESSING_SPEC-10] Clarify default provider class loading semantics Created: 07/Sep/12  Updated: 27/Nov/12  Resolved: 27/Nov/12

Status: Closed
Project: json-processing-spec
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0-pr

Type: Improvement Priority: Major
Reporter: jitu Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


If a OSGi bundle includes both api+impl without META-INF/services entry, the default impl won't be loaded by TCC(since TCC may be webapp classloader)

Comment by jitu [ 27/Nov/12 ]

Not specifying how a default provider is loaded.

  • Also considered specifying a system property for a provider name. The order considered was:
    1) system property
    2) ServiceLoader
    3) default provider

That doesn't work well when a webapp bundles its own provider in a war file (if a system property is already defined).

  • If we define the order to be
    1) ServiceLoader
    2) System property
    3) default provider

then system property doesn't work well(since one of the providers are picked up using ServiceLoader).

so not specifying system property as it is of limited use.

Generated at Tue Feb 21 03:14:57 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.