This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Transform Problem Too Much IO


why not use <xsl:param /> and bring in the data that way ?
or maybe just write the raw nodes to a seperate xml file and use the
document() call,

though it is difficult to see why you want to do this, as we do not have any
example xml/xslt



cheers, jim fuller

----- Original Message -----
From: "Scott Purcell" <spurcell@vertisinc.com>
To: <xsl-list@lists.mulberrytech.com>
Sent: Wednesday, June 26, 2002 7:25 PM
Subject: [xsl] Transform Problem Too Much IO


> Hello,
> I have a problem that I could use some input into. I have a xml file which
describes a html document (textareas, selects, form elements).
>
> I have always included a stylesheet in the xml document which points to a
xsl file. Management now wants us to transform in the server using xalan.
And that is their choice and I can do that.
>
> The problem is, I need to insert a few nodes into the xml before
transforming. The nodes I am inserting are describes in the xsl, but in
order for me to insert a string of nodes, I have to open the xml file (file
io), substring the new insert in, then write the file back out to disk(more
file io).
>
> I have the prototype working, but we cannot go live, due to the IO
problem. How can I insert a couple of nodes into a xml file, without beating
up my system? I also looked at xalan where I am transforming the doc, and it
looks like it only likes file ans filestreams.
>
> Could someone shed some light on this?
>
> Thanks,
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]