Skip to content

Optimise XPATH expression resolving  #8

@metacontext

Description

@metacontext

Currently there are too many places where XPath expressions are resolved. This needs to be cleaned up. Therefore:

  • check if expressionBasedUriResolver and expressionBasedAttributeResolver
    • don't do the same
    • have $repeatIndex and $resourceIndex replaced in all expressions parsed

Then:

  • switch to new function => attributeContentExpressionResolver
  • switch to new function => tagContentExpressionResolver

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions