Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NPE thrown in FHIRPathUtil.getResourceNodes(FHIRPathTree tree, FHIRPathNode node) when FHIRPathNode is not in FHIRPathTree #2518

Closed
JohnTimm opened this issue Jun 16, 2021 · 1 comment
Closed

NPE thrown in FHIRPathUtil.getResourceNodes(FHIRPathTree tree, FHIRPathNode node) when FHIRPathNode is not in FHIRPathTree #2518

JohnTimm opened this issue Jun 16, 2021 · 1 comment
Assignees
@JohnTimm
Labels
bug Something isn't working
Milestone
Sprint 2021-08

Comments

@JohnTimm
Copy link
Collaborator

When the FHIRPath ResolveFunction resolves an internal fragment reference to a resource that is contained (or is a container) it creates a new FHIRPathTree of the resolved resource. This causes an NPE when getResourceNodes is called on a node that is in the new tree but not in the original tree.

https://github.com/IBM/FHIR/blob/cb16c9fcb7d91f1cfd5e1fbf6f9975f8de38e18e/fhir-path/src/main/java/com/ibm/fhir/path/util/FHIRPathUtil.java#L1184-L1188
@JohnTimm JohnTimm added the bug Something isn't working label Jun 16, 2021
@JohnTimm JohnTimm self-assigned this Jun 16, 2021
JohnTimm added a commit that referenced this issue Jun 16, 2021
@JohnTimm
Issue #2518 - update ResolveFunction.resolveInternalFragmentReference
e1e4d0b 
Signed-off-by: John T.E. Timm <johntimm@us.ibm.com>
@lmsurpre lmsurpre added this to the Sprint 2021-08 milestone Jun 17, 2021
@lmsurpre
Copy link
Member

Associated unit test and integration tests are sufficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JohnTimm JohnTimm

Labels
bug Something isn't working
Projects
None yet
Milestone
Sprint 2021-08
Development

No branches or pull requests
2 participants
@lmsurpre @JohnTimm