-
1. Re: For pay docs
darranl Mar 8, 2005 9:22 AM (in response to bmelloni)http://www.jboss.org/docs/index
I think the important line is 'All documentation is now free.' -
2. Re: For pay docs
norman.richards Mar 8, 2005 9:24 AM (in response to bmelloni)The only "pay" documentation is the upcoming SAMS print edition of the JBoss Application Server Guide.
-
3. Re: For pay docs
bmelloni Mar 8, 2005 9:28 AM (in response to bmelloni)I hope free does not mean *out of date* after a few months. I'd be happy to pay for the guarantee of always having up-to-date documentation.
jBoss' habit of improving without preserving backward compatibility gives us great a great product, but it sure causes a lot of pain. -
4. Re: For pay docs
norman.richards Mar 8, 2005 10:59 AM (in response to bmelloni)Why don't you take a look and report back what you think.
-
5. Re: For pay docs
bmelloni Mar 8, 2005 11:22 AM (in response to bmelloni)I read the 4.0 docs (every single one of them) trying to resolve my classloader issue with 4.0.1SP1.
It has a very clear and well written section (a bit hard to find, but it is there) on how to configure 4.0.1 for J2EE 1.4 compatibility and "separate classloading".
Unfortunately, when I followed the instructions and deployed a test EAR that works on 3.2.3 and contains a different version of log4j.jar and commons-logging.jar from the one in jBoss, it experienced a conflict - a clear failure to isolate the class loading. Note that the test app did not even use log4j, it just had the jars present in web-inf/lib.
This is the kind "documentation out of date" issues that I was referring to. -
6. Re: For pay docs
bmelloni Aug 18, 2005 12:05 PM (in response to bmelloni)Note: this classloading problem was solved in the production version of 4.0.2.