Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

J2EE vs Core Java

Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello. I would like to get advice about my career. I'm working on web applications using java. I develop both front and back -end. I find this not interesting because it's always receive a request, change/query the DB, return a model, and render the page. When I talk to recruiters they ask me am I looking for J2EE or Core Java. It seems to me that I should be aiming at Core Java. I started to study multi-threading, for example, and I plan to study the Collections framework. So my question is: does this make sense?
author & internet detective
Posts: 40035
Eclipse IDE VI Editor Java
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Some Core Java jobs are what they sound like - JDBC/threading/etc. Some involve Swing. Others are not. I looked at and saw one that lists Spring and Struts as required skills.

I think it is the domain that has to be interesting more so than the type of programming. There are interesting problems out there. Or making a form of a project interesting - improving quality, getting something done faster, designing a reusable library, etc.
    Bookmark Topic Watch Topic
  • New Topic