Chad Michael is a software engineer, primarily working in the Java realm. He believes in doing things the right way, which means following engineering principles of procedure, documentation and design. On a more specific level, he is a proponent of test-driven, agile software development practices, design patterns, automated unit tests and constant refactoring. Above all else, he's committed to a mode of constant learning that sustains his engagement in his profession. He's also the author of two books: Struts 2 in Action and the SCMAD Exam Guide. Chad is a DZone MVB and is not an employee of DZone and has posted 5 posts at DZone. You can read more from them at their website. View Full User Profile

Development Without Constraint

  • submit to reddit
A presentation on developing apps with the JCR as a data storage. This includes an interesting discussion of the general topic of RDBMS verus non-relational ( NoSQL ) database offerings.
Published at DZone with permission of Chad Davis, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Herry Johnson replied on Tue, 2012/06/12 - 2:15pm

When a JVM starts up in the normal way the initial thread will have the standard classloader as the context class loader, and context class loader is inherited by any more threads created.

But when an application (or framework) creates it's own classloader to load classes from somewhere off the standard class path, it should generally set that as the context classloader in threads executing the code thus loaded, whatever kind of classloader is involved (9 time out of 10 it wll be a URLClassLoader).

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.