I proceeded to Java EE after having learnt some fundamentals of Java SE such as classes (including lambda expression), interface, inheritance, generics, annotations, packages, basic beans, deployment with Jar, a few concepts of collections and basic IO (streams). I suspended learning JDBC, concurrency and other stuffs because I wanted to start to learn Java EE.
I suspended learning JDBC, concurrency and other stuffs because I wanted to start to learn Java EE.
I think JDBC is important. Though its low level and detailed, thats where one learns the basics of data access using Java. I feel it is a required foundation for JPA, EJB, Spring JDBC, etc. Java Threads and concurrency is another important concept in a similar way. Web and enterprise applications are all about concurrent access. The third one is the network programming.
Yes, Java has a lot to learn about!
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 proceeded to Java EE after having learnt some fundamentals of Java SE such as classes (including lambda expression), interface, inheritance, generics, annotations, packages, basic beans, deployment with Jar, a few concepts of collections and basic IO (streams). I suspended learning JDBC, concurrency and other stuffs because I wanted to start to learn Java EE.
I think JDBC is important. Though its low level and detailed, thats where one learns the basics of data access using Java. I feel it is a required foundation for JPA, EJB, Spring JDBC, etc. Java Threads and concurrency is another important concept in a similar way. Web and enterprise applications are all about concurrent access. The third one is the network programming.
Yes, Java has a lot to learn about!