Originally posted by: rh71
	
	
		
		
			Originally posted by: damiano
Java has much more libraries that already exist to do millions of thing (sessions, mail, XML tools  etc..)
		
		
	 
This is precisely what is keeping me from learning Java as easily as CF (which, by the way, is even easier than PHP).  All these 
pre-existing libraries.  If I want to get something accomplished through Java as my very first experiment, I would have to search through all the libraries to see if something already exists.  These libraries come with JDKs... Right?  If something doesn't exist, I have to create it in such a way that it'd be ready for re-use elsewhere - and package it up.  How does a newbie go about getting started with Java if there's SO MUCH to dig through already?
I understand classes and methods up to this point (was never an OOL programmer)... and even created a simple command-line program that just did a bit of math and spat out the answer at the end.  I'm on like Day 4 of SAM'S TEACH YOURSELF JAVA 2 IN 21 DAYS... I'd like to know how to get over that LIBRARIES hump without having to dig thru it all first.  Know what I mean?  Or maybe I just have to keep reading.   My real question: do I go about learning Java by writing everything from scratch, then start to make use of libraries as I get more familiar with them?
		
 
		
	 
completly right...
Start writting your stuff from scratch (Imean...don't go to reinvent servlets or JSPs with your own way to talk to application servers but for the rest...start doing your own things)
then the more you do it, the more you learn of what's available out there...
I don't even know hlaf of the packages that are out there...
The way I usually go about it is our best friend : "google" just search for classes that do what you need...they might be ij the JDK or not.
The thing is that you have two types of classes : the ones that come nativly with your JDK, and then packages written by people out there that you can just download, setup and use (for free or not...)
example of native packages: EJB's, mail, etc..etc..
other classes that I have downloaded from the web: xml servers, chat servers...and much more.
Now, when you write a class, you do not HAVE TO package it nicely so anyone else can reuse it...
you will actually realize that most of the application you will write are so customized that I actually does not make sense for other people to use them...
This is why your first step is to package it and make reusable your yourself 

Then, you might grow to the point where you can write cool classes that other people might be able to use...
hope this makes sense
cheers
Damiano
ps: I just realized this is the longest post I ever wrote on AT :Q