Re: Javadoc convention suggestion
Roedy Green wrote:
If you encounter a package like JavaMail or JMF. there
will be dozens of classes. It would be very helpful if
there were some sort of class overview that said
something like this;
to send an email, you will probably want to create
objects in this order class1, class2, class3....
to receive and email, you will ...
This gives you a handle on a logical order to approach
studying the classes.
But there is already an overview for JavaMail at
<http://java.sun.com/products/javamail/javadocs/>
that includes one simple example, and links to
<http://java.sun.com/products/javamail/FAQ.html>
and
<http://java.sun.com/products/javamail/>
From the latter there are links to
<http://java.sun.com/products/javamail/reference/techart/index.html>
which in turn links to a couple of articles on how to use JavaMail.
If you keep following links from these places, you will encounter
<http://java.sun.com/developer/onlineTraining/JavaMail/index.html>
and
<http://java.sun.com/products/javamail/JavaMail-1.4.pdf>
I really do not see how much more of an overview one could hope for.
"Donkey Hottie" wrote:
I will propably follow you in short order, as I have just decided to lear=
n
JavaMail and Java Severe Faces
Good one!
Fortunately for you, Sun has long since granted Roedy's wish for an
overview of these technologies.
and create a WebMail product without OpenSource [sic] kits in it.
Well, except the Java, that is ;D
Why do you seek to avoid open source "kits"?
I am aware of two libraries for Java Server Faces (JSF), both of which
are open source, but not of any proprietary JSF implementations. Good
luck with that. You might just be stuck with having to use a free (as
in beer), open-source version. Poor you.
--
Lew