JDeveloper documentation concern

Question

Hi, I'm trying to become a java certified programmer, and I had discovered sun java documentation is a mess, you can't compare against oracle documentation for eaxmple, once I finally found it, because it wasn't so easy, the problem I have is you can't print it, some is not enough clear, and definetively there is some dissorder java customer don't complaint,
I didn't understood that sun position, until I read some, I found java's customers see java as a free software, so they don't complaint, instead of that, they feel fortunate of having a class even when it don't work as they expect, because this is like a gift, they don't act like cutomers who pays for something.
What worries me is the fact some Jdeveloper related documentation is going in the same way.
Java has a way to show documentation in html easy to navigate, but doesn't you get the same facility on adobe acrobat?, I'm not telling java api reference html strategy is bad, what I complaint is you don't have a pdf version.
The problem is I use to print the documentation to read it once, and this is simple not possible.
Here is the list of documents only on java.
Business Components Domains Java API Reference     Javadoc
Controller Java API Reference     Javadoc
Model and Business Components Java API Reference     Javadoc
Business Components Generic Domains Java API Reference     Javadoc
Business Components interMedia Domains Java API Reference     Javadoc
Or I'm missing something :)
Thank you

Answer 1

Hi Shay I'm not sure, maybe you could do a survey, to get the database ocp and the developer 6i ocp I printed the reference and read it.
Going to database field several dbas don't read all the database documentation, but this doesn't means there are people who does.
The reason I think you must read at least once the reference manual, is to know what you have to work, this is not about memorizing all the reference manual, because a day after you read, you forget the datails, but you remember there is a function for s,t,w,x task, then one day you need to do that task and you go back to the documentatoin and read that instead of reinventing the wheel.
Or conversely, you need to do a y task urgently, and you know that is not possible, then you don't lose time investigating something does not exists and try to find another solution.
I understand html is more confortable in some situatoins but is true you get the same functionality on pdfs in the bookmark section and you have the facility of the search facility on adobe acrobat listing all the options, it depends on how a person works, even if a person is never going to print a document, work on pdfs is better, how do you do a full search on the api html documentation ? I think it is easier on a pdf.
Thank you :)