Fix private field access error in Aggregation example by adding getter method #121
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hp113
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request resolves a compilation error in the Java Aggregation example.
🔧 Changes Made:
Added a getName() method in the Professor class to properly access the private name field.
Replaced direct field access (professor.name) in the University class with a call to professor.getName().
🐞 Issue Fixed:
In the original code, the showProfessors() method attempted to access professor.name, which is declared private in the Professor class. This violates encapsulation and causes a compilation error.
✅ Outcome:
The updated code now compiles and runs correctly, maintaining object-oriented principles by using proper encapsulation.
Before Changes:
After Changes:
