[DTM] DTMDocumentImpl and DTMBuilder unused?

Hi, I finally found some time to sit down and start migrating my source information patch from the stree model to the new DTM model. As I've been looking at the source code, I stumbled across DTMDocumentImpl and DTMBuilder classes, which don't seem to be used anywhere in the code. Is my understan

cvs commit: xml-xalan/java/src/org/apache/xalan/transformer TransformerHandlerImpl.java

sboag 01/06/26 22:52:17 Modified:java/src/org/apache/xalan/transformer TransformerHandlerImpl.java Log: If the incremental flag is off, then don't use threads at all... tweak stuff in clearCoRoutine so that we call waitTransformThread, so we don't exit

cvs commit: xml-xalan/java/src/org/apache/xalan/transformer TransformerImpl.java

sboag 01/06/26 22:47:47 Modified:java/src/org/apache/xalan/transformer TransformerImpl.java Log: Don't do printStackTrace in run() exception handler... this should be handled elsewhere. Revision ChangesPath 1.104 +2 -1 xml-xalan/java/src/org/apache/xalan/tr

cvs commit: xml-xalan/java/src/org/apache/xml/dtm/ref DTMManagerDefault.java

sboag 01/06/26 22:46:40 Modified:java/src/org/apache/xml/dtm/ref DTMManagerDefault.java Log: Comment out || ((null == reader) && incremental) ... I've changed my mind about this. If incremental is off the TransformerHandlerImpl shouldn't be threaded at all. Revision Ch

cvs commit: xml-xalan/java/src/org/apache/xalan/trace PrintTraceListener.java

sboag 01/06/26 20:54:51 Modified:java/src/org/apache/xalan/trace PrintTraceListener.java Log: For the select event, print node handle and node name (DOM style) instead of java toString on node proxy!! Revision ChangesPath 1.10 +6 -1 xml-xalan/java/src/org/

cvs commit: xml-xalan/java/src/org/apache/xml/dtm/ref DTMManagerDefault.java

sboag 01/06/26 20:52:45 Modified:java/src/org/apache/xml/dtm/ref DTMManagerDefault.java Log: Use && instead of || for ((null == reader) && incremental)... (regression from previous version). Revision ChangesPath 1.12 +1 -1 xml-xalan/java/src/org/apache/xml/

cvs commit: xml-xalan/java/src/org/apache/xml/dtm/ref/sax2dtm SAX2DTM.java

sboag 01/06/26 20:51:40 Modified:java/src/org/apache/xml/dtm/ref/sax2dtm SAX2DTM.java Log: Fix bug where getNodeName doesn't work properly for non-named elements. Revision ChangesPath 1.6 +3 -3 xml-xalan/java/src/org/apache/xml/dtm/ref/sax2dtm/SAX2DTM.java

cvs commit: xml-xalan/java/src/org/apache/xml/utils DefaultErrorHandler.java

sboag 01/06/26 20:03:49 Modified:java/src/org/apache/xml/utils DefaultErrorHandler.java Log: Send the errors to System.err instead of System.out. Have the SAX handler functions go ahead and print the error message. I think the ErrorListener functions should do this also, bu

cvs commit: xml-xalan/java/src/org/apache/xalan/transformer TransformerHandlerImpl.java

sboag 01/06/26 20:01:05 Modified:java/src/org/apache/xalan/transformer TransformerHandlerImpl.java Log: Send the errors to the error listener instead of trying to do a println to System.err. This is still a bit funky, but I think it will do for now.

[Bug 2343] New: - typecheck error invoking name(...) with template parameter arg

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2343 *** shadow/2343 Tue Jun 26 19:51:19 2001 --- shadow/2343.tmp.27855 Tue Jun 26 19:51:19 2001 *** *** 0 --- 1,58 + ++ + | typecheck error in

cvs commit: xml-xalan/java/src/org/apache/xalan/transformer TransformerHandlerImpl.java

sboag 01/06/26 19:08:36 Modified:java/src/org/apache/xalan/transformer TransformerHandlerImpl.java Log: Oops! Left a debug statement in. Revision ChangesPath 1.5 +1 -1 xml-xalan/java/src/org/apache/xalan/transformer/TransformerHandl

cvs commit: xml-xalan/java/src/org/apache/xalan/transformer TransformerHandlerImpl.java

sboag 01/06/26 18:47:08 Modified:java/src/org/apache/xalan/transformer TransformerHandlerImpl.java Log: If we are in a condition where the parser threw an exception, we have to make sure that doMore doesn't call to wait on the other thread, so in this c

cvs commit: xml-xalan/java/src/org/apache/xml/dtm/ref DTMManagerDefault.java

sboag 01/06/26 18:07:50 Modified:java/src/org/apache/xml/dtm/ref DTMManagerDefault.java Log: If the reader == null, we need to ignore the this.m_incremental flag. This is so we make sure we create a CoRoutineParser from the TransformerImpl. Otherwise we'll not have a CoRoutin

cvs commit: xml-xalan/java/src/org/apache/xml/dtm DTMManager.java

sboag 01/06/26 18:03:17 Modified:java/src/org/apache/xml/dtm DTMManager.java Log: Add getIncremental function. Synchronize both get/setIncremental. Revision ChangesPath 1.3 +11 -1 xml-xalan/java/src/org/apache/xml/dtm/DTMManager.java Index: DTMManager.j

[Bug 2338] New: - test copy09 fails

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2338 *** shadow/2338 Tue Jun 26 13:50:46 2001 --- shadow/2338.tmp.11739 Tue Jun 26 13:50:46 2001 *** *** 0 --- 1,78 + ++ + | test copy09 fails

RE: Xalan Blows Up!

You have an older version of the DOM classes somewhere, or somehow the DOM level 2 classes aren't actually in the classpath when your application is running. The: ERROR.version.DOM=ERROR attempting to load DOM level 2 class: line means it can't find the DOM classes, or it's finding the wrong ver

[Bug 1513] - xml output with ident="yes" not being indented

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1513 *** shadow/1513 Tue Jun 26 13:41:14 2001 --- shadow/1513.tmp.11348 Tue Jun 26 13:44:31 2001 *** *** 2,8 | xml output with ident="yes" not being indented | +---

[Bug 1513] - xml output with ident="yes" not being indented

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1513 *** shadow/1513 Sun May 20 17:26:10 2001 --- shadow/1513.tmp.0 Tue Jun 26 13:41:14 2001 *** *** 1,19 ! Bug#: 1513 ! Product: XalanJ2 ! Version: 2.0.0 ! Platform: Sun ! OS/Version: Solaris ! Status: NEW ! Resoluti

[GUMP] Xalan2 Smoketest Failure

This email is autogenerated from the output from: Buildfile: build.xml prepare: compile: [echo] compile ent

[GUMP] Build Failure - Xalan1

This email is autogenerated from the output from: Buildfile: build.xml prepare: [mkdir] Created dir: /home/rubys/jakart

[Bug 1441] - copy-of @* within a copy template not copying the attributes

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1441 *** shadow/1441 Sun May 20 17:25:47 2001 --- shadow/1441.tmp.10188 Tue Jun 26 13:26:13 2001 *** *** 1,19 ! Bug#: 1441 ! Product: XalanJ2 ! Version: 2.0.0 ! Platform: Sun ! OS/Version: Solaris ! Status: NEW ! Resoluti

RE: Xalan Blows Up!

No problem. As you can see, this flagged an error and pointed you to a link of FAQs. If you go there, under the title "I'm having a problem building or running xalan-java on JDK1.3", you'll find the answer to your problem. Basically, you are pointing to old DOM APIs. Follow the instructions ther

[Bug 1532] - problems with /*[] in steps, also [1] and position()=1 not equivalent

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1532 *** shadow/1532 Sun May 20 17:26:15 2001 --- shadow/1532.tmp.9614Tue Jun 26 13:16:15 2001 *** *** 1,19 ! Bug#: 1532 ! Product: XalanJ2 ! Version: 2.0.0 ! Platform: Sun ! OS/Version: Solaris ! Status: NEW ! Resoluti

[Bug 1511] - predicate fails if union not at end [ (Z or V) and X and Y ]

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1511 *** shadow/1511 Tue Jun 26 12:49:53 2001 --- shadow/1511.tmp.9124Tue Jun 26 13:07:38 2001 *** *** 2,8 | predicate fails if union not at end [ (Z or V) and X and Y ] | +---

RE: Xalan Blows Up!

Myriam, Pardon my ignornace, I am new to Xalan. I am trying to see if it is a good fit for the product I am developing. Here is the output of the EnvironmentCheck program: # BEGIN writeEnvironmentReport($Revision: 1.3 $): Useful properties found: java.version=1.3.0 # BEGIN Listin

RE: Xalan Blows Up!

Hi Jim, I didn't mean for you to check the versions, just the classpath to make sure that you are actually running what you think you are running. If you need help with this, try running the EnvironmentCheck program which ships with xalan (in package org.apache.xalan.xslt). Myriam

[Bug 1511] - predicate fails if union not at end [ (Z or V) and X and Y ]

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1511 *** shadow/1511 Tue Jun 12 10:35:00 2001 --- shadow/1511.tmp.8079Tue Jun 26 12:49:53 2001 *** *** 2,9 | predicate fails if union not at end [ (Z or V) and X and Y ] | +---

[Bug 1499] - xsltc outputs tags with method=text

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1499 *** shadow/1499 Tue Jun 26 12:36:23 2001 --- shadow/1499.tmp.7503Tue Jun 26 12:39:39 2001 *** *** 2,8 | xsltc outputs tags with method=text| +---

[Bug 1499] - xsltc outputs tags with method=text

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1499 *** shadow/1499 Sun May 20 17:26:05 2001 --- shadow/1499.tmp.7314Tue Jun 26 12:36:23 2001 *** *** 1,19 ! Bug#: 1499 ! Product: XalanJ2 ! Version: 2.0.0 ! Platform: Sun ! OS/Version: Solaris ! Status: NEW ! Resoluti

[Bug 1989] - runtime error with document function

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1989 *** shadow/1989 Tue Jun 26 12:28:58 2001 --- shadow/1989.tmp.6956Tue Jun 26 12:30:10 2001 *** *** 2,8 | runtime error with document function | +---

[Bug 1989] - runtime error with document function

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1989 *** shadow/1989 Mon Jun 4 11:18:03 2001 --- shadow/1989.tmp.6879Tue Jun 26 12:28:58 2001 *** *** 2,9 | runtime error with document function | +---

Re: Provision in Xpath to get a handle to the parent???

No, there is no way to say "give me the parent where it would go if you don't find it". Perhaps you just want to search for name elements without the attribute? For example: /person/name[count(@serialid) = 0] or /person/name[not(@serialid)] would work. Dave

[Bug 1403] - xsltc has problems with output escaping

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1403 *** shadow/1403 Tue Jun 26 12:19:11 2001 --- shadow/1403.tmp.6169Tue Jun 26 12:19:35 2001 *** *** 2,8 | xsltc has problems with output escaping| +---

[Bug 1403] - xsltc has problems with output escaping

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1403 *** shadow/1403 Tue May 22 07:35:53 2001 --- shadow/1403.tmp.6087Tue Jun 26 12:19:11 2001 *** *** 2,9 | xsltc has problems with output escaping| +---

Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: [Bug2124] - Status of SAXSource is changed in Xalan 2.1.0

Thomas, I just checked in a fix for this. A very simple problem: if there were no parameters being passed to the template, the variable slot wasn't being nulled, and so the default xsl:param wouldn't execute, and you would get the old param value. It's amazing this problem slipped by 1400 tests

cvs commit: xml-xalan/java/src/org/apache/xalan/templates ElemApplyTemplates.java

sboag 01/06/26 12:00:00 Modified:java/src/org/apache/xalan/templates ElemApplyTemplates.java Log: Remove check for nParams > 0 in transformSelectedNodes in the loop where we're setting the params, because otherwise the param won't be nulled out, and xsl:param won't execute the

Re: Removal of XalanJ1 source on Tuesday, 6/26

Shane wrote: >*All* Xalan-J 2.x code, documentation, builds, etc. is contained >under xml-xalan/java. I contend that there is documentation which should be considered common between Xalan-J and Xalan-C (and Xalan-other, if someone wants to do another language). The sensible place to put it is xm

RE: Xalan Blows Up!

Here are the version I am running: 05/23/01 08:45a 732,330 xalan.jar 05/23/01 08:43a 904,030 xerces.jar Jim Urban -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 26, 2001 1:49 PM To: [EMAIL PROTECTED] Subject: Re: X

Re: Xalan Blows Up!

Please check your classpath. Make sure your are pointing to the correct versions of xalan and xerces and that you are not pointing to any old jars. Myriam "Jim Urban"

Re: Removal of XalanJ1 source on Tuesday, 6/26

> Maybe it's just me; if no-one else > cares, then just ensure the last few distros are backed up. Well, I don't care. Maybe somebody else does. > Why whack the 1.x at the filesystem level instead of Attic'ing in the repository? Yes, this was my question, not the other. I doubt if it will ma

Re: Removal of XalanJ1 source on Tuesday, 6/26

Answers Dave's easy one to head off potential confusion: you [EMAIL PROTECTED] wrote > quotes Shane: > >-- I'd like to see a decent vote/comment period go by, and then unless > >anyone complains, a backup...removal > >Note that this includes each of the following areas in > >/home/cv

Xalan Blows Up!

Whenever I run Xalan 2.1.0 from the command line I get the following exception: java.lang.NoSuchMethodError at org.apache.xpath.DOM2Helper.getLocalNameOfNode(DOM2Helper.java:326) at org.apache.xalan.templates.TemplateList.getHead(TemplateList.java:471) at org.apache.xalan.

Re: Removal of XalanJ1 source on Tuesday, 6/26

Answers to Scott's easy ones: you [EMAIL PROTECTED] wrote > [EMAIL PROTECTED] wrote: > > -- I'd like to see a decent vote/comment period go by, and then unless > > anyone complains, a backup of the full Xalan-J 1.x CVS repository (not > just > > the files, but the whole repository) made,

Provision in Xpath to get a handle to the parent???

Hi, In my application i may need to add/insert attributes in a xml_tree. Eg: If the doc looks like Dave 20 Male But would like to add an attribute: serialid Dave 20 Male I therefore use the xpath with /person/name/@serialid to traverse the tree. But whe

Re: Removal of XalanJ1 source on Tuesday, 6/26

[EMAIL PROTECTED] wrote: > I think we should retain anything that applies across all flavors of > Xalan. Maybe some of the docs belong here? How about source files for > the flavor-independent Web pages? I suppose that has implications for > CVS, but is it really a problem or an opportunity? I d

Re: Removal of XalanJ1 source on Tuesday, 6/26

[EMAIL PROTECTED] wrote: > Only > giving people on the mailing list one day to review a major change like > this is wy to short a vote period. I gave the initial notice for this over two months ago. > -- Do any users really want to see more Xalan-J 1.x builds? If so, are > some of our user

Re: Removal of XalanJ1 source on Tuesday, 6/26

> quotes Shane: >One admitted difficulty with xml-xalan is that the 1.x code was >rooted at the top level, which makes it hard to separate from other >bits of Xalan. A great example of how poor planning hurts you down the road. I am adamantly opposed to saying "Let's just do it; we can fix it l

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/trax TrAXFilter.java TransformerFactoryImpl.java TransletTemplates.java

tmiller 01/06/26 10:20:00 Added: java/src/org/apache/xalan/xsltc/trax TrAXFilter.java TransformerFactoryImpl.java TransletTemplates.java Log: moved from runtime subdir to its own trax subdir Revision ChangesPath 1.1 xml-xalan/ja

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/trax - New directory

tmiller 01/06/26 10:17:42 xml-xalan/java/src/org/apache/xalan/xsltc/trax - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/runtime TrAXFilter.java TransformerFactoryImpl.java TransletTemplates.java

tmiller 01/06/26 10:13:30 Removed: java/src/org/apache/xalan/xsltc/runtime TrAXFilter.java TransformerFactoryImpl.java TransletTemplates.java Log: in process of moving these to new subdir -

Re: How to help with XSLTC development

>> is Erwin Bolwidt, > is Morten Jorgensen >>* Change in XslAttribute; an xsl:attribute is allowed anywhere and adds >> the attribute to the nearest containing result element. The check in >> XslAttribute is not needed. >I am not sure if I agree 100% here. Section 7.1.3 of the XSLT 1.0 spec >st

Re: How to help with XSLTC development

Wow! Neat to see more people getting into xsltc internals. Don't forget about the long term plans to merge common parts of code betwixt the xalan and xsltc engines (Scott, Morten, do we have basic plans posted on the web anywhere? Obviously this might take a little while...) --- > > * C

cvs commit: xml-xalan/test/java/src/org/apache/qetest/xalanj2 TestXPathAPI.java

mmidy 01/06/26 09:45:49 Modified:test/java/src/org/apache/qetest/xalanj2 TestXPathAPI.java Log: remove system.out Revision ChangesPath 1.3 +1 -1 xml-xalan/test/java/src/org/apache/qetest/xalanj2/TestXPathAPI.java Index: TestXPathAPI.java

Re: Removal of XalanJ1 source on Tuesday, 6/26

Here's Shane's -0 vote for this (Scott's proposal to remove all Xalan-J 1.x source). Only giving people on the mailing list one day to review a major change like this is wy to short a vote period. Heck, I don't even check xalan-dev every single day myself. Other topics: -- Do any users reall

Re: xerces version

The version of the included xerces.jar file is always clearly stated in the Xalan-J documentation set, which is available either in the distro or on the website. Note to committers: to-do is to checkin the newest xerces.jar from the actual 1.4.1 distro into xml-xalan/java/bin CVS tree: I hope to

Re: : Performance question : what is the fastest way ?

One idea: parse the XML into a DOM Document object. Then simply create a Transformer for each XSL file you have. Then simply do: transformer1.transform(new DOMSource(xmlDOM), new StreamResult("one.out")); transformer2.transform(new DOMSource(xmlDOM), new StreamResult("two.out")); transformer3.t

[Bug 2332] New: - TransformerFactoryImpl.getAttribute() is not implemented

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2332 *** shadow/2332 Tue Jun 26 09:22:57 2001 --- shadow/2332.tmp.704 Tue Jun 26 09:22:57 2001 *** *** 0 --- 1,22 + ++ + | TransformerFactoryImpl.get

Re: How to help with XSLTC development

Erwin Thanks for all your work. It seems like you have gained quite and insight into the inner workings of XSLTC. Impressive! Please pass me any diffs you have ('diff -u' is fine with me), and I'll review the changes and merge them with our current CVS tree. A few comments: > * don't give an er

cvs commit: xml-xalan/test/java/src/org/apache/qetest/xalanj2 TestXPathAPI.java

mmidy 01/06/26 09:18:25 Modified:test/java/src/org/apache/qetest/xalanj2 TestXPathAPI.java Log: Added more xpath api tests Revision ChangesPath 1.2 +10 -1 xml-xalan/test/java/src/org/apache/qetest/xalanj2/TestXPathAPI.java Index: TestXPathAPI.java ===

Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: [Bug2124] - Status of SAXSource is changed in Xalan 2.1.0

Great, thanks. I'll start with this one right now instead of the one you sent me offline. -scott

Re: numberformat07.xsl failure on gump

This test case involves the "currency character" mentioned in the spec. As I read the spec (12.3, first paragraph), this pattern should throw an error, but nobody does. They just treat the character as they do all other non-special characters, making part of the fixed prefix string. Anyone want

cvs commit: xml-xalan/c/src/XPath XToken.cpp XToken.hpp XTokenNumberAdapter.cpp XTokenNumberAdapter.hpp XTokenStringAdapter.cpp XTokenStringAdapter.hpp

dbertoni01/06/26 09:00:38 Modified:c/src/XPath XToken.cpp XToken.hpp XTokenNumberAdapter.cpp XTokenNumberAdapter.hpp XTokenStringAdapter.cpp XTokenStringAdapter.hpp Log: Added new str() overloads. Made XToken::operator=() more efficie

cvs commit: xml-xalan/test/tests/conf/mdocs terms.xml

dmarston01/06/26 08:54:07 Added: test/tests/conf/mdocs terms.xml Log: Oops! Another missing file! (Data for MDOCS16) Revision ChangesPath 1.1 xml-xalan/test/tests/conf/mdocs/terms.xml Index: terms.xml

Re: Help, Build XalanC1_1 samples on Solaris,

We don't currently support Workshop 5.0. You should use 4.2 to build Xalan. If you're going to try to use 5.0, you do not need the STLport, so you'll have to change the Makefile so that it is not included. There are likely other code changes you'll need to make as well. Dave

Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: [Bug2124] - Status of SAXSource is changed in Xalan 2.1.0

Hi Scott, it may that it is a problem with Expressions or Parameters because I found a new very similar bug. This is the template which does not work correct: # Siehe ...   Tabelle Abbildung

cvs commit: xml-xalan/test/tests/api-gold/xalanj2 - New directory

mmidy 01/06/26 08:31:44 xml-xalan/test/tests/api-gold/xalanj2 - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: How Can I get New Xalan Source Code(XalanTransformer class) .

Well, it looks like the command line is too long. Try using a symlink so that the path to the .o files is shorter. Dave "Avula, Raj"

Re: numberformat07.xsl failure on gump

I believe that that's what we do too. Myriam Morten Jorgensen cc: (bcc: Myriam Midy/CAM/Lotu

Help, Build XalanC1_1 samples on Solaris,

system SunOS lab4sun 5.7 Generic_106541-08 sun4u sparc SUNW,Ultra-5_10 compiler Sun WorkShop Compiler C++ (CC) 5.0 STLport4.0 with #define __STL_NO_SGI_IOSTREAMS If I want to compile : gmake SimpleTransform CC -O -I/work/bmatiu/build/STL/stlport/SC5 -KPIC -mt -xs -ptr/work/bmatiu/build/xml-

Re: Help with Extension Functions

You can ignore the warning. You can solve the link errors by linking with the Xalan library. Dave Paul Grinberg

Re: numberformat07.xsl failure on gump

Scott, I don't know how the format-number() function is implemented in Xalan, but I know that we used a standard Java 1.1 class to do the work for us on XSLTC. We did this because the rules for number formatting in the XSLT spec and the Java 1.1 API spec are very close. But, this means that the a

numberformat07.xsl failure on gump

(see http://nagoya.apache.org/~rubys/gump/xml-xalan2-smoketest.html) numberformat07.xsl succeeds fine on my machine. I can't tell why it didn't succeed on the gump machine. Is this a precision problem? Should we exclude this test from the smoketest? mdocs16 is a new test and is missing a ref

Re: AW: [C2.1] Xalan problems?

This bug should be fixed. Stuart reported on the Cocoon list that it is. -scott "Carsten

Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: [Bug 2124] - Statusof SAXSource is changed in Xalan 2.1.0

Yes, thanks. I will try to replicate the problem today. -scott Thomas2.Maesing

[Bug 2267] - XPathAPI seems to apply queries always at the whole document

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2267 *** shadow/2267 Thu Jun 21 07:51:00 2001 --- shadow/2267.tmp.25718 Tue Jun 26 07:03:19 2001 *** *** 2,9 | XPathAPI seems to apply queries always at the whole document | +---

FW: [xsl] Non-hierarchy XML -> hierarchy XML

Mike, Thanks for your suggestion, but what is it look like this stylesheet then ? Any XSLT code that you can show us ( for others who may interested with my problem ) ? Benoit Aumars > -Original Message- > From: Michael Kay [mailto:[EMAIL PROTECTED]] > Sent: 26 June 2001 14:10 > To: [E

Re: Performance question : what is the fastest way ?

Hi, You may want to try the recently donated XSLT Compiler (XSLTC). You can compile your stylesheets into translets and cache a specialized DOM built once from the XML file and optimized to work with the the compiled translets to perform the fastest transformation. Take a look at ...\xml-xa

cvs commit: xml-xalan/java build.xml

dleslie 01/06/26 05:53:18 Modified:java build.xml Log: Updated version property to 2_2_D4 and year to 2001. Revision ChangesPath 1.113 +3 -3 xml-xalan/java/build.xml Index: build.xml ===

Re: FYI: Xalan2 Smoketest hangs on Solaris

Scott Boag wrote: > > I made a fix to CoroutineSAXParser at 03:46 PM my time, which solved a hang > bug. The CVS log lists this as 01/06/24 12:46:40, which I assume is PDT? > The gump xml-xalan2 page list the build at Sun Jun 24 12:17:07 PDT 2001, so > I think you would have missed it. Also I pa

XPointer?

I am trying to extract a NodeList from a Document using XPointer. I see XPointer support in Xalan 1, but I'm using Xalan 2.0.0 (and Xerces 1.4.0, for what it's worth). I understand that XPath was moved out of the actual xalan package in Xalan 2, so I suspect the same is the case with XPointer, but

Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: [Bug 2124] -Status of SAXSource is changed in Xalan 2.1.0

Hi Scott, I have sent the complete source to your private email. Do you get it? Regards Thomas

Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: [Bug 2124] -Status of SAXSource is changed in Xalan 2.1.0

Hi Scott, I have sent the source to your private email. Do you get it? Regards Thomas

Non-hierarchy XML -> hierarchy XML

Hi all, I would like to transform a node into a hierarchy node using a pattern, i.e into . Assume the non-hierarchy source : I need your help please and the pattern as follows : : : : : : Applying that pattern against the above source, give this hierarchy res

Re: xerces version

> If no, can I use xerces 1.4.1 Yes, you can use Xerces 1.4.1 with Xalan-J 2.1.0. Works fine for me. Regards. -- Bjoern Martin[EMAIL PROTECTED]

Re: File paths (was: Complete newbie in Xalan using Xalan c++!!!)

Ok thanks to you, I will try to fix this problem... - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 25, 2001 5:20 PM Subject: File paths (was: Complete newbie in Xalan using Xalan c++!!!) > > Hergert writes: > >what is wrong if i tell Xalan as