Hi,
Thanks for sharing these resources. It sure helps. I am glad that you take time to answer my post. In fact, I'm also looking for organizing source kind of stuff. Like in a video, spring tells it is more convenient to create a static class like "StepConfiguration" which has reader/writer declaration, it is more readable for your job configuration class.
And too often, code in video are made for a presentation purpose, so a lot of code is in the same class.
I am new in this subject so I try things maybe I will make a post about this to see what people think (like I hate xml configuration, I prefer the annotation way). Maybe some are really obvious for spring expert but I prefer keep an objective eye on it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi,
Thanks for sharing these resources. It sure helps. I am glad that you take time to answer my post. In fact, I'm also looking for organizing source kind of stuff. Like in a video, spring tells it is more convenient to create a static class like "StepConfiguration" which has reader/writer declaration, it is more readable for your job configuration class.
And too often, code in video are made for a presentation purpose, so a lot of code is in the same class.
I am new in this subject so I try things maybe I will make a post about this to see what people think (like I hate xml configuration, I prefer the annotation way). Maybe some are really obvious for spring expert but I prefer keep an objective eye on it.