You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Boris Kolpackov (JIRA)" <xe...@xml.apache.org> on 2009/11/03 10:19:59 UTC

[jira] Closed: (XERCESC-1652) DOMDocumentTypeImpl is not thread safe

     [ https://issues.apache.org/jira/browse/XERCESC-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boris Kolpackov closed XERCESC-1652.
------------------------------------

    Resolution: Won't Fix

Marking this bug as "Won't fix" since there are no plans to make any more releases in the 2-series.

> DOMDocumentTypeImpl is not thread safe
> --------------------------------------
>
>                 Key: XERCESC-1652
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1652
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: DOM
>    Affects Versions: 2.7.0, 2.8.0
>         Environment: Multithreaded programs
>            Reporter: Jesse Pelton
>             Fix For: 2.9.0
>
>         Attachments: DOMDocumentTypeImpl.diff
>
>
> DOMDocumentTypeImpl.cpp uses a static gDocTypeDocument() method to return a singleton doctype document that provides various utility services (allocating named node maps, cloning strings, and so on). Any calls to methods of this static document that can modify its instance data, including calls that allocate memory, must be synchronized to keep the document's state consistent.
> Patch against the trunk to follow, but note that it should be reviewed carefully. First, I pretty much blindly copied the synchronization code from DOMImplementationRegistry.cpp and may have gotten something wrong. Second, the patch is adapted from changes I made to v2.7.0 code and has not been tested (or even compiled) (Updates to the trunk prevent successful application of a patch against v2.7.0 to code from the trunk.) And lastly, it's possible that the trunk updates obsolete my patch, though it still seems relevant.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org