Re: XSLTC Translet calls System.exit() ???

Glenn, Please bear in mind that our TrAX support for XSLTC is not complete or stable - even though there is a preliminary implementation in Xalan 2.1. You can nothing but expect to get into problems, like the one you described, unless you wait until our TrAX support is complete before you attempt

Are keys applied when document() is called?

Does Xalan-Java apply keys to additional source documents loaded using the document() function? In an article at http://www-106.ibm.com/developerworks/library/ws-trans/index.html?dwzone=ws, Uche Ogbuji states that "every time an additional source document is loaded with the XSLT document() functi

STLPort

Hi, Is there an alternative to using STLport for building Xalan 1.1?? Please let me know if there are any other STL libraries that I can use. Thanks, Nikita begin:vcard n:Sawant;Nikita x-mozilla-html:FALSE org:iPlanet Group adr:;; version:2.1 email;internet:[EMAIL PROTECTED] x-mozilla-cp

RE: [ANNOUNCE] Xalan-J 2.2.D9 Released! Having strange problems

Hello, What has changed since D7? Almost none of my stylesheets /* which work fine with Xalan 2D7, Xalan 1.2.2 */ work any more. Any ideas? I am getting no error messages whatsoever Thank you very much Alex > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] >

Re: extension functions and Tomcat

Glad this worked out. We should include these Tomcat issues in some sort of FAQ. I'll try to write something up. Gary Dmitry Beransky wrote: > > It works! It works! > > I sneaked a peek at the source code of the interceptor, and it looks like > its purpose is to fix the context class loade

Re: extension functions and Tomcat

It works! It works! I sneaked a peek at the source code of the interceptor, and it looks like its purpose is to fix the context class loader property of the request thread. So I guess I was on the right track with my suspicion, I just didn't know there was already a fix. Thanks a lot! Dmit

[DO NOT REPLY: Bug 3112] New: - "tokenize extension fails with DTM"

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3112

Re: Got me the extension blues :-( still dumping !

Gary, thanks for the information for what to include in the bugzilla report..and glad to be of service to Apache and Xalan! Glad to have you entering your first bug!! I hope it will be my last ;-) We all learn by sharing what we know Robert A. DiBlasi >From: Gary L Peskin <[EMAIL P

Re: Got me the extension blues :-( still dumping !

I know what's wrong. We just need to have it in bugzilla to track it. Please add in your stylesheet and XML and the stack trace. The title should be "tokenize extension fails with DTM" Go for it. Glad to have you entering your first bug!! Gary zalan zalan wrote: > > Gary, > > Just downloa

Re: Got me the extension blues :-( still dumping !

Gary, Just downloaded the xalan-j_2_2_D9 and ran the programsad to say ...it did not work again.but ;-) it did give me a new dump :-) maybe you could zero in on something in the process that is not correct before I hall off and report to the bugzillaand what is the importaint inform

Xalan and Xerces 1.5.1

Hi, When is the versiom of Xalan compatible with Xerces 1.5.1 due to be released ?? Thanks, Nikita begin:vcard n:Sawant;Nikita x-mozilla-html:FALSE org:iPlanet Group adr:;; version:2.1 email;internet:[EMAIL PROTECTED] x-mozilla-cpt:;0 fn:Nikita Sawant end:vcard

Re: [xsl] Xalan, errors and ErrorListener

>Actually I don't see how I can do that. A TransformerException is pretty >much immutable, so I guess I must throw the one that was passed in without >altering it. Or generate a new one based on the one that was passed in ... though that's how we're winding up with the hard-to-read multiplyh nes

Re: ICU 1.8.1

Xalan 1.1 is not compatible with ICU1.8.1, due to API changes in the ICU. Xalan 1.2, which should be released within the next couple of days, will be compatible. Dave

[ANNOUNCE] Xalan-J 2.2.D9 Released!

We have just posted Xalan-Java version 2.2.D9 (a Developer's release) to xml.apache.org.To get a complete build with samples, sources, and documentation, download and unzip either of the following from http://xml.apache.org/dist/xalan-j/. xalan-j_2_2_D9.zip xalan-j_2_2_D9.tar.gz The so

cvs commit: xml-xalan/test/tests/capi/extensions extensions01.xsl

pauldick01/08/13 14:21:37 Modified:test/tests/capi/extensions extensions01.xsl Log: Commented out generate-id(rtf$). Revision ChangesPath 1.3 +2 -2 xml-xalan/test/tests/capi/extensions/extensions01.xsl Index: extensions01.xsl ===

cvs commit: xml-xalan/test/tests/capi-gold/extensions extensions01.out

pauldick01/08/13 14:21:18 Modified:test/tests/capi-gold/extensions extensions01.out Log: Commented out generate-id(rtf$). Revision ChangesPath 1.2 +0 -1 xml-xalan/test/tests/capi-gold/extensions/extensions01.out Index: extensions01.out =

Re: extension functions and Tomcat

I never saw this arrive so I'm resending. Also, I should mention that it applies only to Tomcat 3.2.x running on Java 2 JDK 1.2 or higher. What version of Tomcat are you on? What version of Java? Gary Gary L Peskin wrote: > > Hi, Dmitry -- > > Can you please try this to help us out? > > 1.

Re: Got me the extension blues :-( ...the big dump!

This is a bug in XalanJ 2.2.x in the tokenize extension function. Please add it into bugzilla. Thanks, Gary zalan zalan wrote: > > Gary, > > Nice to write and read ya :-)...anyway > > Here is the dump you requested.. > > javax.xml.transform.TransformerException: > at > or

Re: [xsl] Xalan, errors and ErrorListener

Scott wrote: > > Well, the problem is, I think, that the creation of the new exception in > > fatalError will create a new stack trace, which I don't think is what you > > want. I replied: > You're right; I should modify the incoming exception. Actually I don't see how I can do that. A Transform

ICU 1.8.1

Hi, I am using Xalan 1.1(Xerces 1.4.0) with ICU. Is ICU 1.8.1 compatible with this version of Xalan /Xerces. If it is not compatible then what are the technical incompatibilties that I should expect. Any reply is welcome. Thanks, Nikita begin:vcard n:Sawant;Nikita x-mozilla-html:FALSE org:

RE: extension functions and Tomcat

> ancestors -- that hasn't changed. So in Tomcat 3.3 the normal > thing to do is to put Xalan and all extension classes in the > common classloader, ${tomcat_home}/lib/common, just as in ... or in ${tomcat_home}/lib/apps, which is the same except that the Tomcat servlet container classes can't se

RE: extension functions and Tomcat

Hi Dmitry, Sorry, everyone, if this seems to be slanting a little off-topic, but I think Xalan's extension loading merits an attempt to understand this stuff to the dot ... > First, how a class loader finds classes is completely up to the particular At second glance, I guess that's right ... th

Re: extension functions and Tomcat

Hi, Dmitry -- Can you please try this to help us out? 1. Be sure you have the following: as the LAST RequestInterceptor in your conf/server.xml file. 2. Place xalan.jar ONLY in ${tomcat_lib}/lib 3. Place your extension ONLY in ${web_app}/web-info/lib 4. Stop/Start Tomcat 5. Tell us i

Re: Got me the extension blues :-( ...the big dump!

Gary, Nice to write and read ya :-)...anyway Here is the dump you requested.. javax.xml.transform.TransformerException: at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1151) at org.apache.xalan.transformer.TransformerImpl.transform

Re: Got me the extension blues :-(

If you are running this from the command line, please include the -edump switch. Otherwise, please provide a stack trace from where you catch the error and we'll have a look. Gary zalan zalan wrote: > > Hello, > >I have run into a little problem.I'm pretty sure the solution is > simpl

Got me the extension blues :-(

Hello, I have run into a little problem.I'm pretty sure the solution is simplehere is the scoop: OS: Win NT Xalan build: xalan-j_2_2_D6 Problem: Extension...getting error using the "tokenize" extension error code: XSLT Error (javax.xml.transform.TransformerException): Description: J

Re: XSLTC Translet calls System.exit() ???

There must be more code than what you are showing below. Using the translet should be as simple as: /** * Transform XML Data using an XSL stylesheet and send it out * as the HTTP Servlet Response. * * @param Templates xslt XSL Translation template * @param StringWrite

RE: extension functions and Tomcat

Gulli, I will disagree on a couple of accounts, if I may, First, how a class loader finds classes is completely up to the particular classloader. For example, it is my understanding that in Tomcat 3.2 and prior, the classloader would do a postfix traversal of the loader hierarchy, that is, i

Re: extension functions and Tomcat

Gulli -- Thanks for your excellent explanation. However, it is our intention to allow you to place a single copy of xalan.jar in ${tomcat_home}/lib where it is available to all webapps but allow you to place application-specific extensions in the ${webapp}/?.war file or in a ${webapp}/WEB-INF/li

RE: extension functions and Tomcat

Hi, just to clear it up for everyone, the fix makes perfect sense, but no, it isn't necessary to copy xalan.jar into every webapp. It makes sense because you made sure that xalan.jar was found by the same classloader as your extension classes. That is the real requirement. You satisfied this req

cvs commit: xml-xalan/c/Tests Tests.dsw

pauldick01/08/13 12:01:27 Modified:c/Tests Tests.dsw Log: Removed Xdom and Resultarget projects. Revision ChangesPath 1.10 +0 -24 xml-xalan/c/Tests/Tests.dsw Index: Tests.dsw === RCS file:

cvs commit: xml-xalan/java build.xml

dleslie 01/08/13 11:56:07 Modified:java build.xml Log: Update fdist version number to 2.2.D9 Revision ChangesPath 1.123 +2 -2 xml-xalan/java/build.xml Index: build.xml === RCS file: /h

Re: XSLTC Translet calls System.exit() ???

Hi Glenn, I have been using XSLTC from a JSP with our native API, and not TrAX. I've been able to use a string as the XML input as follows:     StringReader inputsr = new StringReader(xmlinput);     InputSource input = new InputSource(inputsr);     reader.parse

Re: extension functions and Tomcat

Well, that will work but it shouldn't be necessary to copy xalan.jar into the web-info/lib directory of every webapp. I'll look into this further but I'm glad that this is working for you now. Gary Dmitry Beransky wrote: > Gary, > > I'm including the environment info at the end of the message.

Re: extension functions and Tomcat

Gary, I'm including the environment info at the end of the message. However, with Gulli's help I was able to fix the problem. It turned out, all I had to do was to move xalan.jar out of ${tomcat_home}/lib and into ${web_app}/web-info/lib. I hope, this is an appropriate fix. Thanks Dmitry

cvs commit: xml-xalan/java/src/org/apache/xalan/res XSLTInfo.properties

mmidy 01/08/13 11:01:02 Modified:java/src/org/apache/xalan/res XSLTInfo.properties Log: Update version for 2.2.D9 build Revision ChangesPath 1.22 +1 -1 xml-xalan/java/src/org/apache/xalan/res/XSLTInfo.properties Index: XSLTInfo.properties =

Re: extension functions and Tomcat

At 10:08 PM 8/11/2001, Gary L Peskin wrote: >Also, in your servlet, please include the following line just before >kicking off the transformation: >... >and let us know what the output is from there. Gary, I'm including the environment info at the end of the message. However, with Gulli's hel

Re: FW: NoSuchMethodError

>Sorry, my bad. The method it cannot find is Node.getNamespaceURI. Which is indeed a DOM Level 2 method. > I just found out we were using version 1.4.2 of xerces not the supported 1.4.1. Odd. That _should_ support DOM Level 2. It's possible you may have other classpath problems as well...

FW: NoSuchMethodError

Sorry, my bad.  The method it cannot find is Node.getNamespaceURI. It's also my fault.  I just found out we were using version 1.4.2 of xerces not the supported 1.4.1.   Sorry for the inconvenience.   Derrick Koes   -Original Message-From: Derrick Koes Sent: Monday, August 13, 2001

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/compiler xpath.cup

tmiller 01/08/13 10:35:48 Modified:java/src/org/apache/xalan/xsltc/compiler xpath.cup Log: bug 2553, fixes AbbreviatedAbsoluteLocationPath, some relative location paths still give duplicates, will need to filter. Revision ChangesPath 1.6 +14 -4 xml-xalan/java

cvs commit: xml-xalan/c/Tests/Transformer TestXalanTransformer.cpp

dbertoni01/08/13 10:29:25 Modified:c/Tests/Transformer TestXalanTransformer.cpp Log: Fixed errors compiling stylesheets. Revision ChangesPath 1.4 +26 -3 xml-xalan/c/Tests/Transformer/TestXalanTransformer.cpp Index: TestXalanTransformer.cpp ==

Re: NoSuchMethodError

>java.lang.NoSuchMethodError >at org.apache.xml.dtm.ref.dom2dtm.DOM2DTM.addNode(DOM2DTM.java:231) >I cannot seem to find the "addNode" method in the source. It's there. In the version currently checked into CVS, it's on line 200; it may be a bit above or below that point in earlier code. prote

cvs commit: xml-xalan/c/Tests/Harness Harness.dsp

dbertoni01/08/13 10:21:00 Modified:c/Tests/Harness Harness.dsp Log: Added missing link libraries. Revision ChangesPath 1.11 +2 -2 xml-xalan/c/Tests/Harness/Harness.dsp Index: Harness.dsp ===

cvs commit: xml-xalan/java commits.xml

dleslie 01/08/13 10:20:04 Modified:java commits.xml Log: Update for 2.2.D9 Revision ChangesPath 1.20 +59 -0 xml-xalan/java/commits.xml Index: commits.xml === RCS file: /home/cvs/xml-xal

cvs commit: xml-xalan/c/src/XalanSourceTree XalanSourceTreeContentHandler.cpp XalanSourceTreeContentHandler.hpp

dbertoni01/08/13 10:14:45 Modified:c/src/XalanSourceTree XalanSourceTreeContentHandler.cpp XalanSourceTreeContentHandler.hpp Log: Make sure comments in DTDs are not passed through to the source tree. Revision ChangesPath 1.8 +49 -10 xml-

cvs commit: xml-xalan/c/src/XPath QName.cpp QName.hpp QNameByReference.cpp QNameByReference.hpp QNameByValue.cpp QNameByValue.hpp

dbertoni01/08/13 10:13:02 Removed: c/src/XPath QName.cpp QName.hpp QNameByReference.cpp QNameByReference.hpp QNameByValue.cpp QNameByValue.hpp Log: Fixed QName collisions with Xerces. --

cvs commit: xml-xalan/c/src/XalanTransformer XalanTransformer.cpp XalanTransformer.hpp

dbertoni01/08/13 10:09:08 Modified:c/src/XalanTransformer XalanTransformer.cpp XalanTransformer.hpp Log: Fixed QName collisions with Xerces. Revision ChangesPath 1.26 +2 -2 xml-xalan/c/src/XalanTransformer/XalanTransformer.cpp Index

RE: Precompiled stylesheet example

I've taken out as much of my application specific stuff as possible. Here are the basic calls. private Templates template_; public void init(ServletConfig config) throws ServletException { super.init(config); try { //for storing a compiled and resuseable style sheet

cvs commit: xml-xalan/c/src/XPath XalanQName.cpp XalanQName.hpp XalanQNameByReference.cpp XalanQNameByReference.hpp XalanQNameByValue.cpp XalanQNameByValue.hpp XPath.cpp XPathEnvSupport.hpp XPathExecutionContext.hpp XPathExecutionContextDefault.cpp XPathExecutionContextDefault.hpp

dbertoni01/08/13 10:08:02 Modified:c/src/XPath XPath.cpp XPathEnvSupport.hpp XPathExecutionContext.hpp XPathExecutionContextDefault.cpp XPathExecutionContextDefault.hpp Added: c/src/XPath XalanQName.cpp Xala

cvs commit: xml-xalan/c/Projects/Win32/VC6/XPath XPath.dsp

dbertoni01/08/13 10:07:31 Modified:c/Projects/Win32/VC6/XPath XPath.dsp Log: Removed old source files and added new ones. Revision ChangesPath 1.27 +24 -12xml-xalan/c/Projects/Win32/VC6/XPath/XPath.dsp Index: XPath.dsp

NoSuchMethodError

I got the following stack trace attempting to use Xalan.     java.lang.NoSuchMethodError at org.apache.xml.dtm.ref.dom2dtm.DOM2DTM.addNode(DOM2DTM.java:231) at org.apache.xml.dtm.ref.dom2dtm.DOM2DTM.(DOM2DTM.java:150) at org.apache.xml.dtm.ref.DTMManagerDefault.getDTM(DTMManagerDefault.java:

Precompiled stylesheet example

I am trying to find a lightweight sample that shows how to read an XSLT file, "precompile" it once, and then use it over and over again with different XML files. Such a sample in a servlet context would be faboo. I've looked through the archives but have only found references to problems, or mes

Re: Shift-JIS output from Xalan-J?

http://xml.apache.org/xerces-j/faq-general.html#faq-8 Sean Forde wrote: > > Hi friends, > > Is it possible to output with Shif-JIS encoding from either Xerces-J or > Xalan-J? > > Thank you > > -Sean > > Sean Forde > Software Architect > LizardTech, Inc

Shift-JIS output from Xalan-J?

Hi friends, Is it possible to output with Shif-JIS encoding from either Xerces-J or Xalan-J? Thank you -Sean Sean Forde Software Architect LizardTech, Inc

Re: What outputs

>Joe is right about the startDTD() and endDTD() calls. But they're in >org.xml.sax.ext.LexicalHandler, not DeclHandler. Oops. Looked at both, misremembered which I'd seen these in. Sorry!

Re: What outputs

Morten -- Joe is right about the startDTD() and endDTD() calls. But they're in org.xml.sax.ext.LexicalHandler, not DeclHandler. Gary [EMAIL PROTECTED] wrote: > > I believe the SAX2 DeclHandler.startDTD() call carries that information. > Note that there's an endDTD() call too. Morten Jorgense

Re: What outputs

I had trouble finding this too. Make sure you set a DTDHandler as well as a LexicalHandler even if you don't override anything in the DTDHandler class else startDTD doesn't get called. Paul Emberson >I believe the SAX2 DeclHandler.startDTD() call carries that information. >Note that there's

Re: What outputs

I believe the SAX2 DeclHandler.startDTD() call carries that information. Note that there's an endDTD() call too.

cvs commit: xml-xalan/test test.properties

curcuru 01/08/13 08:33:04 Modified:test test.properties Log: Updated smoketest.conf.embedded to include 3 embedded files; update excludes with excluded tests that have bugzilla bugs for them Revision ChangesPath 1.9 +5 -0 xml-xalan/test/test.properties

cvs commit: xml-xalan/test/tests/conf-gold/sort sort13.out

dmarston01/08/13 08:26:13 Modified:test/tests/conf-gold/sort sort13.out Log: Add the zero case Revision ChangesPath 1.2 +1 -1 xml-xalan/test/tests/conf-gold/sort/sort13.out Index: sort13.out ==

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/runtime AbstractTranslet.java DefaultSAXOutputHandler.java TextOutput.java

morten 01/08/13 08:25:56 Modified:java/src/org/apache/xalan/xsltc/runtime AbstractTranslet.java DefaultSAXOutputHandler.java TextOutput.java Log: A start on a fix for output DOCTYPE declarations based on the attributes of the eleme

cvs commit: xml-xalan/test/tests/conf/sort sort13.xml

dmarston01/08/13 08:25:44 Modified:test/tests/conf/sort sort13.xml Log: Add the zero case Revision ChangesPath 1.2 +1 -0 xml-xalan/test/tests/conf/sort/sort13.xml Index: sort13.xml === RC

cvs commit: xml-xalan/test/tests/conf-gold/numbering numbering91.out numbering87.out numbering88.out numbering89.out numbering90.out numbering86.out

dmarston01/08/13 08:23:23 Added: test/tests/conf-gold/numbering numbering91.out numbering87.out numbering88.out numbering89.out numbering90.out numbering86.out Log: New cases involving namespaces, position, id, key Revision Cha

cvs commit: xml-xalan/test/tests/conf/numbering iddata.dtd numbering86.xml numbering86.xsl numbering87.xml numbering87.xsl numbering88.xml numbering88.xsl numbering89.xml numbering89.xsl numbering90.xml numbering90.xsl numbering91.xml numbering91.xsl

dmarston01/08/13 08:22:01 Added: test/tests/conf/numbering iddata.dtd numbering86.xml numbering86.xsl numbering87.xml numbering87.xsl numbering88.xml numbering88.xsl numbering89.xml numbering89.xsl numbering90.xml

What outputs

I am trying to find a fix for a bug in XSLTC, and I need to know what handler I should use to output the declaration. Should this be passed to a org.xml.sax.ext.DeclHandler, a org.xml.sax.DTDHandler, or passed to the basic SAXHandler (in some what I fail to see). Thanks, Morten

[Bug 2864] - conf test node06 fails, name() without args prefixed name with ns URI

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2864

cvs commit: xml-xalan/java xsltc_todo.xml

dleslie 01/08/13 07:59:11 Modified:java xsltc_todo.xml Log: Revised email address for Jacek Ambroziak. Revision ChangesPath 1.6 +1 -1 xml-xalan/java/xsltc_todo.xml Index: xsltc_todo.xml ===

cvs commit: xml-xalan/java/xdocs/sources/xalan faq.xml

dleslie 01/08/13 07:56:32 Modified:java/xdocs/sources/xalan faq.xml Log: Added faq from Gunnaluger Thor Briem on loading extension element/function classes in a servlet. Revision ChangesPath 1.10 +13 -1 xml-xalan/java/xdocs/sources/xalan/faq.xml Index: faq

[Bug 3047] - Xalan failing to escape non UTF-8 characters

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3047

RE: Xerces into Xalan ...

The problem with the name clash with QName will be fixed in the next release of Xalan. The Xerces team has promised that, in the future, they will add a prefix to such common names to avoid future collisions. Xalan will do the same thing. As far as the following construct being an error: > DO

[Bug 3047] - Xalan failing to escape non UTF-8 characters

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3047

[Bug 3106] - incorrect discover of SAXParser

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3106

Re: XPathAPI .... full implementation of XPath?

I think we'd need to see your XML in order to understand the problem. Gary Etienne Deleflie wrote: > > Hello, > > I am using the XPathAPI in Xalan 2 j , and there are some cases where a > legal XPathString should return something but does not. > > eg > > "/dataset1/table/row/column[@Date

[Bug 2839] - xsltc fails conf test namespace01 with omitted line feeds

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2839

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/compiler Parser.java

morten 01/08/13 06:33:14 Modified:java/src/org/apache/xalan/xsltc/compiler Parser.java Log: A small fix that will allow top-level elements of an unknown URI. XSLTC now ignored the element(s), while it previously reported an error of an unsupported XSLT extension. PR:

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

>I changed a sign-extended shift to a non-sign-extended shift Thanks, Gary. We should probably do a global search for >> throughout Xalan and check them; I suspect that 99.9%+ of the remaining instances really should be >>>.

[Bug 1397] - apply-imports shouldn't invoke built-ins to process children

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1397

[Bug 2939] - xsltc fails conf test match16 not doing position numbering relative to the child axis

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2939

[Bug 2838] - xsltc fails conf test namedtemplate10 not doing numeric comparison

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2838

[Bug 2749] - xsltc fails conf test impincl10 on apply-imports

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2749

[Bug 2553] - xsltc fails test axes83 selecting nodes without children

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2553

[Bug 1397] - apply-imports shouldn't invoke built-ins to process children

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1397

[Bug 2664] - de.fub.bytecode.generic.ClassGenException: Branch target offset too large for short throwen when Transforms reach a size certain complexity... In this case 65K

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2664

Re: Access violations

Dave, thanks for your help. It still didn't work with the service pack and dinkumware patches alone, but it did when I rebuilt the libraries. Paul At 13:56 10/08/01 -0400, you wrote: >Hi Paul, > >Some comments: > >1. Did you patch the Microsoft library with the Dinkumware patches as >

[Bug 2864] - conf test node06 fails, name() without args prefixed name with ns URI

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2864

[Bug 2864] - conf test node06 fails, name() without args prefixed name with ns URI

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2864

[Bug 2863] - conf tests namespace72,85,91,93, and 94 fail in creating elements with namespace attributes

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2863

[Bug 1411] - namespace-alias not outputting XSL URI in stylesheet element

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1411

[Bug 2857] - xsltc fails conf test namespace23

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2857

[Bug 2840] - xsltc fails conf test namespace16 not ignoring top-level element in unknown namespace

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2840

[Bug 2839] - xsltc fails conf test namespace01 with omitted line feeds

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2839

[Bug 1504] - xsltc ignores doctype-system attribute of xsl:output

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1504

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/compiler UnionPathExpr.java

morten 01/08/13 03:49:52 Modified:java/src/org/apache/xalan/xsltc/compiler UnionPathExpr.java Log: Added a small fix that orders the expressions inside a union in such a way that expressions with an attribute axis or attribute node type will be put first. PR: bugzilla

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/compiler Parser.java

morten 01/08/13 03:33:37 Modified:java/src/org/apache/xalan/xsltc/compiler Parser.java Log: I added a flag to the compiler/Parser class that is set if the outermost element in the stylesheet contains a definition of the XSL namespace. The parser already has a global variable '_

[Bug 3106] - incorrect discover of SAXParser

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3106

RE: Xerces into Xalan ...

Benoit, I have this problem as well. I'm forwarding this to the xalan-dev list: the QName class is used in their XPath processing. Regards, Peter. > -Original Message- > From: Benoit Lefevre [mailto:[EMAIL PROTECTED]] > Sent: Monday, August 13, 2001 7:31 PM > To: [EMAIL PROTECTED] > Su

[GUMP] Xalan2 Smoketest Failure

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

[Bug 3106] New: - incorrect discover of SAXParser

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3106

Re: XSLTC Translet calls System.exit() ???

Glenn, We are just after finishing an initial implementation of the entire TrAX API for XSLTC. We decided to separate the TrAX implementation and the native XSLTC APIs, and this is why the AbstractTranslet class no longer implements the Transformer interface. All TrAX code is located in the

XPathAPI .... full implementation of XPath?

Hello, I am using the XPathAPI in Xalan 2 j , and there are some cases where a legal XPathString should return something but does not. eg "/dataset1/table/row/column[@DateAndTime]" returns nothing. If I am not wrong, this XPath should return all elements called column (in /dataset

  1   2   >