What

Problem

Two related bugs when using oneOf/anyOf/allOf with $ref references and rule executors:

Bug 1: AttributeError: 'Resolver' object has no attribute 'resolving'

• Occurs when schema has oneOf with $ref + rule executor
• Code passed new referencing.Resolver to validate(resolver=...) but jsonschema expected old RefResolver API
• This was fixed by Remove resolver param passed to validate() in JSON schema  #2186

Bug 2: PointerToNowhere: 'xxx' does not exist

• Occurs when oneOf subschemas contain nested $refs (e.g., Account → PaymentMethod)
• After resolving $ref, we lost resolver context needed for reference resolution for the nested subschema

Solution

Use referencing library's intended pattern - lookup() returns both contents AND resolver:

# Get both contents and context-aware resolver:
lookup_result = resolver.lookup(ref)
subschema = lookup_result.contents
subschema_resolver = lookup_result.resolver  # Maintains context!

# Create validator with proper resolver context
cls = validator_for(subschema)
validator = cls(subschema, registry=registry, _resolver=subschema_resolver)
validator.validate(message)

Checklist

• Contains customer facing changes? Including API/behavior changes
• Did you add sufficient unit test and/or integration test coverage for this PR?
  • If not, please explain why it is not required

References

JIRA: https://confluentinc.atlassian.net/browse/INC-8778

Test & Review

Add several unit tests to cover oneOf, anyOf, allOf $ref, including the nested schema case

Open questions / Follow-ups