I think the more important concern is to narrow down which skills actually constitute job readyness.
Without an idea for a reasonable curriculum, it's useless to guesstimate (it's the same with requirements - you cannot tell how long it takes if you don't have the faintest clue about the actual scope...) and the Java ecosystem can be overwhelming for a beginner, since there are multiple options to choose from for nearly aspect you could find useful.
But before you bother yourself with Java EE vs. Spring and the likes, I'd like to suggest that you get yourself a copy of Josh Blochs "Effective Java" (3rd edition) and work through it. When all the 90 items in there are, if not yet second nature, then at least understood by you, I'd consider that as a promising start.
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.
I think the more important concern is to narrow down which skills actually constitute job readyness.
Without an idea for a reasonable curriculum, it's useless to guesstimate (it's the same with requirements - you cannot tell how long it takes if you don't have the faintest clue about the actual scope...) and the Java ecosystem can be overwhelming for a beginner, since there are multiple options to choose from for nearly aspect you could find useful.
But before you bother yourself with Java EE vs. Spring and the likes, I'd like to suggest that you get yourself a copy of Josh Blochs "Effective Java" (3rd edition) and work through it. When all the 90 items in there are, if not yet second nature, then at least understood by you, I'd consider that as a promising start.