   | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
  | |  | Best strategy for caching JDom Document instance and provide | Best strategy for caching JDom Document instance and provide 2004-01-08 - By Bradley S. Huffman
Back "Guillaume Berche" writes:
> Then I wonder whether JDom beta 8 or beta 9, would have problems with > concurrent read accesses. I've haven't yet read the code in details, but I > think I read somewhere that JDom was internally using lazy initialization > when traversing the tree and that concurrent accesses to it might cause > problems. Is this [still] true?
Shouldn't be a problem in 8/9. Pre beta 7 (?) would create the content list (if it didn't exist) whenever getContent was called in anticipation that the user might want to add something through the List interface. This meant the internal structure got modified just from traversal. 7 and above create nothing until require by a actual add operation, so read-only traversal by multiple threads shouldn't be a problem.
Brad __ ____ ____ ____ ____ ____ ____ ____ ____ ____ To control your jdom-interest membership: http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@(protected) .com
Earn $52 per hosting referral at Lunarpages.
|
|
 |