You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking up to customize the method moveCursorToNextFragment in StaxEventItemReader and I noticed this method uses isFragmentRootElementName which is currently a private method. In my opinion, if caller is 'protected', the callee should have been made 'protected' as well.
Affects: 3.0.7
The text was updated successfully, but these errors were encountered:
In my opinion, if caller is 'protected', the callee should have been made 'protected' as well.
That's not necessarily true, because if that private method calls another private method which in turn calls yet another private method, we would transitively need to make all of them protected and end up opening the entire class for extension.
As a second example, the jumpToItem is protected and calls readToStartFragment and readToEndFragment which are private. I don't think these two methods should necessarily be made protected.
That said, I see an added value in making StaxEventItemReader#isFragmentRootElementName protected to be able to override the logic in there.
fmbenhassine
changed the title
isFragmentRootElementName method access modifier should be protected [BATCH-2583]
StaxEventItemReader#isFragmentRootElementName method should be protected
Jul 24, 2020
Balan opened BATCH-2583 and commented
I was looking up to customize the method moveCursorToNextFragment in StaxEventItemReader and I noticed this method uses isFragmentRootElementName which is currently a private method. In my opinion, if caller is 'protected', the callee should have been made 'protected' as well.
Affects: 3.0.7
The text was updated successfully, but these errors were encountered: