Win a copy of Node.js Design Patterns: Design and implement production-grade Node.js applications using proven patterns and techniques this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

J2SE or J2EE

 
Ranch Hand
Posts: 202
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There are two companies. One company asks me to work on J2EE and the other company requires "core Java programming only".

I do not have much core Java programming experience and it is the area I need lots of practices.

But, I know that I am not going to work for a certain company for the rest of my life. Which skill is more marketable (I mean in terms of market demand and therefore easier to find jobs)?
 
Ranch Hand
Posts: 375
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Would you try to run before you can walk? Start with J2SE and move on to J2EE (which is what most jobs demand).
 
Ranch Hand
Posts: 5093
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
without a solid understanding of the core language you'll never be a good J2EE developer...
 
Ranch Hand
Posts: 1071
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Correct me if I'm wrong, but isn't 'J2EE' a very loose term that can mean any number of added Java technologies. Or do I just see the term overused and used in places it shouldn't.
 
Daniel Gee
Ranch Hand
Posts: 202
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Which one is more marketable? Java and only core Java OR J2EE (Java plus Servlets, JSPs, EJBs)?
 
Steven Bell
Ranch Hand
Posts: 1071
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well, you can't do JSP's, EJB's, or Servlets without core Java.
And EJB's are just a bad idea anyways.
 
Daniel Gee
Ranch Hand
Posts: 202
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It is clear to me now. I should take the job that asks me to work on J2EE because I can practise "programming in core Java" plus that I can use Servlets, JSPs, and EJBs - I can do both.

The other job, although reqires lots of practices in core Java programming, will never give me a chance to use Servlets, JSPs, etc.
 
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I learned J2EE before I learned java in depth. If I had it to do over again, I would learn java first. Once you learn java and understand the basics, it helps you to learn J2EE more quickly.

Ben
SCJP 1.4
 
clojure forum advocate
Posts: 3479
Mac Objective C Clojure
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


And EJB's are just a bad idea anyways.


well, I'm not the best person to talk about EJB, but personally I find EJB is great technology ...
think about the services that you got them from the container (tx, disribution, security, multithreading .....)
but EJB is not for all situations, it is not EJB's fault if someone use them uncorrectly ...
(I waiting EJB 3 to be released)
it is just my HMO ...
 
Steven Bell
Ranch Hand
Posts: 1071
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I was halfway joking about the EJB's. While I agree they do have their uses I would say more than half of the projects I've seen use them, shouldn't. Of course I find them to be overly invasive for my taste.
 
Ranch Hand
Posts: 300
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Why wud u want to use EJB when u can achieve the same things using Spring in a significantly simpler way without incurring the cost of a full-blown application server?

Originally posted by Steven Bell:
I was halfway joking about the EJB's. While I agree they do have their uses I would say more than half of the projects I've seen use them, shouldn't. Of course I find them to be overly invasive for my taste.

 
soniya saxena
Ranch Hand
Posts: 300
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think you are taking the right decision Daniel.

Although, it would be a great idea to master core java before moving onto J2EE, practicality demands that u go ahead with J2EE cuz that is what counts on ur resume and what will help u get the next better job.

However, at the same time, do some core java programming by the side so that the u dont get lost in the J2EE technology maze without a solid foundation.

Originally posted by Daniel Gee:
It is clear to me now. I should take the job that asks me to work on J2EE because I can practise "programming in core Java" plus that I can use Servlets, JSPs, and EJBs - I can do both.

The other job, although reqires lots of practices in core Java programming, will never give me a chance to use Servlets, JSPs, etc.

 
Ranch Hand
Posts: 1033
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by soniya saxena:
I think you are taking the right decision Daniel.

Although, it would be a great idea to master core java before moving onto J2EE, practicality demands that u go ahead with J2EE cuz that is what counts on ur resume and what will help u get the next better job.

However, at the same time, do some core java programming by the side so that the u dont get lost in the J2EE technology maze without a solid foundation.



From what I've seen of J2EE jobs, they aren't better than core Java jobs, there are just way more of them. J2SE and J2ME projects are likely to be more interesting, while J2EE projects are just recycled CICS and Cobol, mostly really dull business apps.
 
Jeroen Wenting
Ranch Hand
Posts: 5093
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by John Todd:

well, I'm not the best person to talk about EJB, but personally I find EJB is great technology ...
think about the services that you got them from the container (tx, disribution, security, multithreading .....)
but EJB is not for all situations, it is not EJB's fault if someone use them uncorrectly ...
(I waiting EJB 3 to be released)
it is just my HMO ...



There's only 1 group of people for whom EJBs are good things, and that's consultants from appserver vendors.
Maybe add another group, salespeople from hardware vendors
 
Ranch Hand
Posts: 169
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Kashif Riaz:
Would you try to run before you can walk? Start with J2SE and move on to J2EE.




Incorrect.

J2EE jobs are by no means superior to J2SE jobs.

When it comes to "Core J2SE programmer" job, it usually means advanced Swing or RMI programming.

I've seen many J2EE experts who knows nothing about Swing / RMI -- which is "Core J2SE".
 
Jeroen Wenting
Ranch Hand
Posts: 5093
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Jay Shin:



I've seen many J2EE experts who knows nothing about Swing / RMI -- which is "Core J2SE".



Correct, but many would like to know. They just never got the chance...
That's one reason I'm wanting to do SCJD, to get a legitimate reason to play with all that stuff that my boss won't let me at work
 
peter wooster
Ranch Hand
Posts: 1033
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Jeroen Wenting:

Correct, but many would like to know. They just never got the chance...
That's one reason I'm wanting to do SCJD, to get a legitimate reason to play with all that stuff that my boss won't let me at work



Go for the SCJD, you'll do well, your responses on the SCJD forum are spot on.
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic