Try this site: http://mindprod.com/jgloss/jgloss.html

I too am just starting to take a look at java. so far, it seems that what
java is mostly usefull for is graphics (ie images, list boxes, combo boxes
etc) other than that most any scripting language, or even plain old C, will
do. Thats my first take on java. What else is it usefull for? (I'm asking
because I'm looking for ways to use it)
Eric

You can try Sun's "The Really Big Index".
http://java.sun.com/docs/books/tutorial/reallybigindex.html

The "Java Language Specification, Third Edition" for reference.
http://java.sun.com/docs/books/jls/third_edition/html/j3TOC.html

"JavaTM 2 Platform Standard Edition 5.0 Overview for reference.
http://java.sun.com/j2se/1.5.0/docs//guide/

JDK 5.0 Documentation for reference.
http://java.sun.com/j2se/1.5.0/docs

"Java 2 Platform Standard Edition 5.0 API Specification" for reference.
http://java.sun.com/j2se/1.5.0/docs/api/

And along with all of that "The Java Developers Almanac 1.4" for
examples outside the tutorials.
http://javaalmanac.com

Thanks in Advance...
IchBin, Pocono Lake, Pa, USA              http://weconsultants.phpnet.us
__________________________________________________________________________

'If there is one, Knowledge is the "Fountain of Youth"'
-William E. Taylor,  Regular Guy (1952-)

To answer your specific questions:

A servlet is some code that gets run when a web server receives a
request.  It can access the properties of the HTTP request and do
something in response.  A JSP is similar, except that it's HTML at root,
with Java code only sprinkled in.  It's a good idea to combine the two:
have a servlet receive each request first, look it over, then forward it
to a JSP that contains the resulting HTML with a few dynamic things.

An EJB is completely different.  It allows you to put Java code on a
server where others can get to it, and then have client code (which
might include servlets, or normal applications, or whatever) call the
methods of that object.  EJBs can be used in very large scale
applications, but can also make things very complicated if they are used
in the wrong places.  (And some people would tell you there are no
"right" places for EJBs.)  EJBs also provide some other features like
object-relational mapping, declarative security (which is largely
useless in practice due to its limitations), and they prevent you from
doing some useful things like multithreading and security managers (the
marketing literature describes this as "EJBs handle multithreading and
security policies for you so you don't have to worry about it").

JAR files are essentially just zip files containing your Java code, and
an optional manifest that says things like what libraries the code
depends on and what class to start with.  Since every class you write is
compiled into a different class file, JAR files make things a lot more
convenient versus carrying around several hundred individual class
files.

Incidentally, not that you're all excited about this copy of BEA
WebLogic, I will slightly burst your bubble and warn you that it might
be the wrong thing for your organization.  WebLogic is a pretty big
piece of software, and you could easily sink months of effort into
getting it to do what you want, when those tasks could have been
accomplished in simpler ways.  It all depends on the requirements of the
situation... but "small" and "WebLogic" don't normally go together well.  
There are freely available products (like Tomcat) that provide the more
useful pieces of these APIs and frameworks without the complexity of
WebLogic.