Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: ,NET choking on DocBook stylsheets

From: Martin Honnen <mahotrash@-----.-->
To: NULL
Date: 7/4/2009 12:48:00 PM
pschuller wrote:
> I am transforming a DocBook compliant xml file into html using the DocBook 
> stylesheets distribution.  The transform runs in 2 second when I run it in 
> the oXygen  IDE.    My website is a .NET 3.5 web site.   I am doing the 
> transform programatically using an XslCompiledTransform, a MemoryStream etc.  
> That method works fine for the TOC, Introduction, and Abstract.  For the 
> sections that have <mediaobjects> in them, I immediately get a StackOverFlow 
> error ("the error").  I can display a source file that has one <mediaobject> 
> but get the error if there are two.
> 			
> Below is one of my <mediaobjects>.  There are only two in my test file.  
> (There are 350+) in the file that oXygen processes in 2 seconds.  I only have 
> to comment out the <textobject> <phrase> node to get the transform to run.

Doesn't oXygen use Saxon for XSLT transformations? There is a .NET 
version of Saxon thus you could try to use that instead of 
XslCompiledTransform. See http://saxon.sourceforge.net/
		



-- 

	Martin Honnen --- MVP XML
	http://msmvps.com/blogs/martin_honnen/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent