Xalan parsing usiing Xerces

[Pe...@trilliumsoftware.com]

Hi,

I am having a problem using the nethod.

nt XalanTransfomer::parseSource (const XSLTInputSource &, const 
XalanParsedSource *&, bool useXercesDOM=false)

In particular when I specify the flag useXercesDOM as true then whenever 
the ParsedSource is destroyed
(either explicitly or when the XalanTransfomer is deleted) I get an 
assertion failure.

The assertion would appear to be because an object is being allocated with 
one MemoryManager
and being de-allocated with another.

I have only tested this problem on windows with Xalan 1.9 and Xerces 2.6 
but the nature of the problem
suggests that it's platform independent.

I have re-created the problem with a smaller program.
If you take the TransformToXercesDOM sample and you change the line (192) 
from

                                theResult = 
theTransformer.parseSource(argv[1], theParsedSource);
to
                                theResult = 
theTransformer.parseSource(argv[1], theParsedSource, true);

this reproduces the problem.

Regards,

Perer Marron

Again on compiling Xalan with VC8 (VS2005)

[mauro castelli <ca...@hotmail.com>]

Hi all,
I'm looking at the previous posts to find out how to compile
Xalan/Xerces with VC8 (VS2005 Professional),
but something is still not clear to me:

1. For Xalan-C:
I understood the Xalan version I should use is the one in the trunk
(http://svn.apache.org/repos/asf/xalan/c/trunk/ ).
Something else shold be done? (as an example, for wchar_t ?)

2. For Xerces-C:
Which version of Xerces should I use? 2.7 or the one in the trunk?
(http://svn.apache.org/repos/asf/xerces/c/trunk/ ).

Thank in advance.
Mauro Castelli

_________________________________________________________________
Ricerche online più semplici e veloci con MSN Toolbar! 
http://toolbar.msn.it/

Re: Xalan parsing usiing Xerces

[David Bertoni <db...@apache.org>]

Peter.Marron@trilliumsoftware.com wrote:
> 
> Hi,
> 
> I am having a problem using the nethod.
> 
> nt XalanTransfomer::parseSource (const XSLTInputSource &, const 
> XalanParsedSource *&, bool useXercesDOM=false)
> 
> In particular when I specify the flag useXercesDOM as true then whenever 
> the ParsedSource is destroyed
> (either explicitly or when the XalanTransfomer is deleted) I get an 
> assertion failure.
> 
> The assertion would appear to be because an object is being allocated 
> with one MemoryManager
> and being de-allocated with another.
> 

This is a known problem that was fixed in Xalan-C 1.10.

Dave