Skip to content

Resource should be optional in StaxEventItemReaderBuilder #3736

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.

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

Closed
fmbenhassine opened this issue Jun 26, 2020 · 2 comments
Closed

Resource should be optional in StaxEventItemReaderBuilder #3736

fmbenhassine opened this issue Jun 26, 2020 · 2 comments
Assignees
Labels
for: backport-to-4.2.x Issues that will be back-ported to the 4.2.x line in: infrastructure type: bug
Milestone

Comments

@fmbenhassine
Copy link
Contributor

Same as #3731 but for XML files.

@fmbenhassine fmbenhassine added status: waiting-for-triage Issues that we did not analyse yet type: bug in: infrastructure and removed status: waiting-for-triage Issues that we did not analyse yet labels Jun 26, 2020
@fmbenhassine fmbenhassine added this to the 4.3.0 milestone Jun 26, 2020
@fmbenhassine fmbenhassine added the has: backports Legacy label from JIRA. Superseded by "for: backport-to-x.x.x" label Jun 26, 2020
@parikshitdutta
Copy link
Contributor

Hi @benas, would you like to assign this to me? I can give it a try.

Thank you.

@parikshitdutta
Copy link
Contributor

Hi @benas, Please have a look at my submitted PR #3752, I will look forward to your feedback.

Thank you.

@fmbenhassine fmbenhassine added for: backport-to-4.2.x Issues that will be back-ported to the 4.2.x line and removed has: backports Legacy label from JIRA. Superseded by "for: backport-to-x.x.x" labels Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: backport-to-4.2.x Issues that will be back-ported to the 4.2.x line in: infrastructure type: bug
Projects
None yet
Development

No branches or pull requests

2 participants