Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Templates/Transformers + thread safety???

Templates/Transformers + thread safety???

2007-02-27       - By Tom Fennelly
Reply:     1     2     3     4     5     6     7  

Thanks Erin.

I've updated that test download to include testing against stream
source/result instances.  Still getting unexpected results on these
(stream source/result) when not synschronizing on the template
instance.  Zip available at
http://milyn.codehaus.org/xalan/xalan-test-v2.zip (zip also includes the
milyn jar).

Thanks again Erin.

Regards,

Tom.


Erin Harris wrote:
>
> Hi Tom,
>
> I couldn't run your test case as I don't have the milyn classes.  Have
> you tried using StreamSource and StreamResult to see if you get the
> same problem?
>
> Thanks.
>
>
> Erin Harris
>
>
>
>
> *Tom Fennelly <tom.fennelly@(protected)>*
>
> 26/02/2007 02:29 PM
>
>  
> To
>   xalan-j-users@(protected)
> cc
>  
> Subject
>   Templates/Transformers + thread safety???
>
>
>
>  
>
>
>
>
>
> Hi.
>
> While running some tests I noticed something strange - applying
> transformations concurrently + unsynchronized using the same template
> instance *appears* to be yielding unexpected results i.e. if I
> synchronize transformations across the threads (synchronize on the
> template instance) I have no issues.  I'm quite sure I'm doing
> something wrong here but haven't found the answer.
>
> I packaged up the test in a maven2 project
> (_http://milyn.codehaus.org/xalan/xalan-test.zip_).  If you run the
> junit test from the download you'll not see any errors because the
> transform step is synchronized on the template instance
> (XsltConcurrentTest.java, line 168).  If you remove the
> synchronization, you start getting errors.
>
> My understanding was that I should be able to load a stylesheet into a
> single instance of javax.xml.transform.Templates and then, on each
> Thread, create and use new Transformer instance through a call to
> Templates.newTransformer().transform(...).  Is this wrong??
>
> Environment:
>
>     * Windows XP
>     * jdk1.5.0_10
>     * Xalan 2.7.0
>     * Xerces 2.7.1
>     * xml-apis 1.3.02
>
> I have taken a look around for an answer to this, but I fear that it
> may be something silly I'm doing, so I apologize in advance :-[
>
> Regards,
>
> Tom.