you "Walsh, Eric" <[EMAIL PROTECTED]> wrote
> For the record I say you just throw the old routines back
> in and call it even, especially since very little of my
> XPath queries are XSLT originated.
I know there are definite issues with our XPathAPI performance, but I
think this is actua
>Does anyone know of a way to transform a valid XML file into a
>word doc?
Step 1: Ascertain which formats Word can import
Step 2: Look at the list of formats FOP can produce at
http://xml.apache.org/fop/index.html
If there is a good choice that is common to the two lists, then
Step 3: Get Xalan
>Does anyone have any good suggestions about a GUI tool for generating
>XSLT.
>TIA
>Anamitra
There are a couple tools on IBM AlphaWorks. Go to
http://www.alphaworks.ibm.com
and type "XSLT" in the search bar at the top of the page.
.David Marston
Does anyone know of a way to transform a valid XML file into a word doc?
Is there a transform engine available for this or do I have to start from
scratch?
Regards
Charles Horan
Title: RE: XPathAPI performance problems
For the record I say you just throw the old routines back
in and call it even, especially since very little of my
XPath queries are XSLT originated.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 1
H. We knew we might be deoptimizing DOM performance in exchange for
better SAX performance, and in order to optimize for the needs of the XSLT
processor... but I agree we should pause and think carefully about this.
One possible approach: Pre-analyse the XPath to see if it's going to need
to
Hi! I have been using Xalan 2.1.0 and I have a couple of questions about
the changes made in Xalan 2.2.0.
1.) In xalan 2.1, when you have compiled translets in a jar file, you can
just load the translets and get a transformer by casting the translets to
javax.xml.transform.Transformer. Now that t
Just as Eric (Walsh) stated, not only is the perfomance drastically
degredated, I found that it becomes increasing bad as I query farther down
the document, and performance degredates at a fairly steep rate.
I found that the Xalan 2.1 release is almost as fast as the previous release
we were using
Title: RE: XPathAPI performance problems
Thanks for the info. Reading the explaination of DTM on
apache.org, it seems funny that this was done to speed up
XPath Querying, it seems querying an object model you already
have would be much more effecient than building a new one.
Your CachedXP
> takes about 20ms. It seems like the XPath routine is starting
> from the top of document, no matter if you give it a parent or
> not.
That may in fact be true in the current code.
Your XPath may want to search upward/backward from the starting node
(ancestor or previous axes). That means thos
Hi Guys
Does anyone have any good suggestions about a GUI tool for generating XSLT.
TIA
Anamitra
Hi !
I construct an XML tree into memory.
I'm doing a transformation with a transformer that is created
by reading the xsl file from disk :
transformer.transform(new
javax.xml.transform.dom.DOMSource(node),
new javax.xml.transform.stream.StreamRes
Title: RE: XPathAPI performance problems
I am also having XPath performance problems (which I
submitted to the dev group). The problem seems to have
nothing to with querying a document multiple times.
In my case, I am parsing an XML schema file by first getting
the complexType nodes then
Simplest solution is to process the documents separately and then run a
fourth stylesheet that reads the results (via document()) and merges them
appropriately. The pipelining extension may be useful for this purpose,
since that would allow it all to happen as a single call to Xalan.
You could tr
Most likely an environment problem on that machine. Can you provide
full details of that machine's setup - specific NT, JVM, xalan
versions, complete environment that your JVM is run in, etc.?
See http://xml.apache.org/xalan-j/faq.html#faq-9 and run the
EnvironmentCheck utility from within your a
If you're going to query a single document multiple times, see the class
CachedXPathAPI. If I remember correctly, its javadoc summarizes the issues
involved.
Correct behavior. The "default template" is applied in this case, as
required by the XSLT spec.
Manish -
Here's how I have transformed multiple input files of differing document
types into one output:
The first input file is the handled by templates with no mode attribute. The
other files are transformed by a set of templates with mode="type2", etc.
These templates
Hi
We need to process three different input sources and apply an XSLT
(different rules for each input source) to generate one single
output. Does anyone know if this is possible with Xalan? If not are there
any other alternatives besides writing XPath to extract the data and
custom code to build t
> Using the first releases of Xalan 1.x and Xerces 1.x , this feat was
> accomplished in under 3 seconds. Using the current releases, noted above,
> this takes up to 10 minutes!.
> The individual calls to selectSingleNode() take up to a half-second each!
Wow.
> Using cachedXPathAPI only reduces
I am having some serious performance issues with XPathAPI processing using
the latest releases of Xalan and Xerces (Xalan j 2.2.0 and Xerces 2 D14).
I have tried a very simple test case which attempts using a DOM document
which consists of about 1000 sibling elements directly beneath the documen
21 matches
Mail list logo
