Java EE via The Java EE tutorial, a textual PDF format downloaded from Oracle website.
It will take longgggg time... because it has a lot of topics such as servlet, JSF, EJB, CDI, web services (SOAP based and REST), JPA. It is a long term goal, so I would not mind taking long time to learn it.
Spring framework seems to be easier to use than Java EE (currently named to Jakarta EE), but I need to have good grasp on Java EE too.
My ultimate goal is using both Java EE and Spring framework in future projects.
It does, indeed. I have learnt some of those and you are right. With ongoing and changing technology it is harder too.
Learning Java SE 8 (or above) is kind of pre-requisite (as per me) as it requires knowledge of functional programming constructs, streams, etc., and also database programming.
In fact, I am learning Spring Boot programming seriously nowadays (last week I finished a free course from Spring Academy and felt good about it).
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.
Java EE via The Java EE tutorial, a textual PDF format downloaded from Oracle website.
It will take longgggg time... because it has a lot of topics such as servlet, JSF, EJB, CDI, web services (SOAP based and REST), JPA. It is a long term goal, so I would not mind taking long time to learn it.
Spring framework seems to be easier to use than Java EE (currently named to Jakarta EE), but I need to have good grasp on Java EE too.
My ultimate goal is using both Java EE and Spring framework in future projects.
It does, indeed. I have learnt some of those and you are right. With ongoing and changing technology it is harder too.
Learning Java SE 8 (or above) is kind of pre-requisite (as per me) as it requires knowledge of functional programming constructs, streams, etc., and also database programming.
In fact, I am learning Spring Boot programming seriously nowadays (last week I finished a free course from Spring Academy and felt good about it).
Cheers!
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!