This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Welcome to JavaRanch. Please look carefully at the official naming policy at JavaRanch & reregister yourself with a proper first & last name, with a space between them. Initials may be used for a first name, but not a last name. Please adhere to official naming policy & help maintain the decorum of the forum. The naming policy can be found at http://www.javaranch.com/name.jsp. You can change your name here.
I think you are splitting hairs with deciding which API to specialize in. I use any number of APIs (EJB's and web services included) to accomplish my tasks. One must be very flexible and continue to learn, not just master one API and claim to be valuable. There's much more to programming than writing code. If I had to say my most valuable skills for my employer, my coding skills would probably be 3rd after being able to communicate well with a variety of technical and non-technical users (you can't code unless you can figure out what people want) and my domain knowledge (I have intimate knowledge of processes that are vital to this organization). I get paid very well, but I have a lot of responsibility.
Originally posted by Peter Parker: There is only hype, no value about SOA & webservices.
Hi Peter, Then what is the real reason behind the hype for Web seervices technologies.. than J2EE..
Joined: Mar 07, 2007
Originally posted by Joe Ess: I think you are splitting hairs with deciding which API to specialize in.
Thats' really ture Joe, in the long run I am planning to learn both the technologies, however in a given time scale I am not sure of which side to continue either in EJB under J2EE or under Web Services...
Well I'd suggest you avoid focussing just on technologies. Build expertise on the different problem domains. And yes if you want to choose a particular technology path, say for example Java,concentrate more on the 'how' of things rather than the 'what'. So if you want to learn say EJBs, channel your endeavours on learning the core RMI based architectural concepts of EJBs rather than simply cramming the EJB APIs. If you want to learn JMS, focus on messaging systems and their implementations ,in general.Once you get these going, mastering APIs/technologies would be a cakewalk.
Coming to your question on SOA and webservices, let me tell you that they are not specific 'technologies'. SOA is an architectural concept and web services is an SOA implemenation methodology.J2EE could be viewed as a technology and you can very much have J2EE under the covers in a web services based application.So if you want to specialise in the Java world, you can't avoid learning core Java and J2EE. Hope that helps
[ November 13, 2007: Message edited by: san ban ] [ November 13, 2007: Message edited by: san ban ]