[Bug 2230] - Method newTransformer(javax.xml.transform.Source) should not return null, but does so

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2230 *** shadow/2230 Mon Jul 2 06:01:32 2001 --- shadow/2230.tmp.6216Wed Jul 11 00:21:47 2001 *** *** 2,10 | Method newTransformer(javax.xml.transform.Source) should not return null, | +--

Re: Hack alert

[EMAIL PROTECTED] wrote: > > Gary L Peskin <[EMAIL PROTECTED]> wrote: > > What do you think about creating a _qn field > > in VariableStack that would be a QName array. > > I would rather not. The variable stack itself is very clean now and I > would rather keep it that way. I don't think a pe

[Bug 2175] - non unique method key for java extensions

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2175 *** shadow/2175 Fri Jul 6 11:32:19 2001 --- shadow/2175.tmp.5673Tue Jul 10 23:51:28 2001 *** *** 2,9 | non unique method key for java extensions | +---

Re: XALAN and big files

Hi Scott, thanks for your fast reply. Adding incremental does help so that output is generated from the beginning. But the main problem still exist: All nodes seems to be kept in memory when closing the transformer. I guess what's getting in here is DTM, right? Does DTM has any co

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

garyp 01/07/10 23:49:53 Modified:java/src/org/apache/xpath/compiler Compiler.java Log: Fix bug 2175 by adding the current time to the method key to ensure method key uniqueness. Multiple Compilers were getting the same ha

Re: Addition of a new function

Shruti -- Your XPath expression selects all employee nodes that meet the criteria. The tokenize function has no effect on the output, it's only used to select employee nodes. And the expression you've chosen will basically select any non-empty employee node. It sounds like what you want to do

[Bug 2559] - Problem with ancestor-or-self

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2559 *** shadow/2559 Tue Jul 10 17:30:15 2001 --- shadow/2559.tmp.5594Tue Jul 10 23:18:41 2001 *** *** 77,79 --- 77,83 My results are: a3: b1 b2 b3 b4 b5 b6 + + + --- Additional Comments From [EMAIL PRO

Re: [DTM] [PATCH] file, line, column number information for XML source document

On Wed, 11 Jul 2001 00:19:43 -0400, [EMAIL PROTECTED] wrote: > Sorry this took so long to integrate. My bad. No problem, I saw you were really busy last week. > The changes are now committed. Please check the integration carefully. Yep, I'll do that. > I made one small change. In SAX2DTM m

Re: Addition of a new function

thanks Gary Now i am able to use the tokenize function but i am not getting the correct output ... my input xml looks like - http://xml.apache.org/xalan";> Herbert,Johnny,09/01/1998,95000 Hill,Graham,08/20/2000,89000 and the xpath query is //employee[xalan:tokenize(./,",")]... i am evalua

Re: XALAN and big files

Carsten, please see http://xml.apache.org/xalan-j/dtm.html#settings. You want to set "http://xml.apache.org/xalan/features/incremental"; to true. Be aware that Xalan has a limit of 1,048,575 nodes per document right now. Since you have big documents, I'm curious if your getting close to that.

Re: Nomination of Ovidiu Predescu as Xalan committer

+1 [EMAIL PROTECTED] wrote: > > I would like to nominate Ovidiu Predescu as a Xalan committer. Ovidiu has > done some excellent work with his work with file, line, column number > information for XML source documents, and is interested in having better > tools support for Xalan, and is also int

Re: [DTM] [PATCH] file, line, column number information for XML sourcedocument

Sorry this took so long to integrate. My bad. The changes are now committed. Please check the integration carefully. I made one small change. In SAX2DTM m_sourceSystemId, m_sourceLine, and m_sourceColumn were being automatically created by the variable initializers. I took this out since th

Nomination of Ovidiu Predescu as Xalan committer

I would like to nominate Ovidiu Predescu as a Xalan committer. Ovidiu has done some excellent work with his work with file, line, column number information for XML source documents, and is interested in having better tools support for Xalan, and is also interested in working on processing optimiz

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

sboag 01/07/10 21:00:16 Modified:java/src/org/apache/xalan/res XSLTErrorResources.java java/src/org/apache/xalan/trace PrintTraceListener.java java/src/org/apache/xalan/transformer TransformerImpl.java java/src/org/apache/xalan/xslt Process

XALAN and big files

Hi Folks! I'm impressed by the improvements xalan made since I last tokk a lokk at it! Wow! I have to solve a problem someone may have a hint where to look. An instance in my program is generating megabytes of data by pushing the data into a contenthandler using sax events. It's a list

Re: Hack alert

Gary L Peskin <[EMAIL PROTECTED]> wrote: > What do you think about creating a _qn field > in VariableStack that would be a QName array. I would rather not. The variable stack itself is very clean now and I would rather keep it that way. I don't think a penalty should be imposed for the (forgiv

Re: Hack alert

Scott -- I've been working on the Variable stuff for a couple of days and I had a thought for you to ponder. What do you think about creating a _qn field in VariableStack that would be a QName array. It would go hand-in-hand with _sf and hold the QName represented by the corresponding _sf entry

[Bug 2559] - Problem with ancestor-or-self

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2559 *** shadow/2559 Tue Jul 10 15:33:56 2001 --- shadow/2559.tmp.858 Tue Jul 10 17:30:15 2001 *** *** 2,8 | Problem with ancestor-or-self | +---

repro request for bug 2468

Hi all, Could someone try to repro http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2468 I would greatly appreciate it. To repro the bug you just need to make a 2line change to xml-xalan/test/tests/contrib/xsltc/mk/mk031.xsl I'm concerned that I've been chasing my tail about the problem as a re

[Bug 2465] - Atributes do not work in Xalan XSLTC 2.1.0 and 2.2.x

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2465 *** shadow/2465 Thu Jul 5 14:25:18 2001 --- shadow/2465.tmp.409 Tue Jul 10 16:26:02 2001 *** *** 18,21 sucessful transform but no Attributes are showing up. The interesting thing is that you can do a count or a for-each

cvs commit: xml-xalan/java/src/org/apache/xalan/lib Extensions.java

garyp 01/07/10 16:23:52 Modified:java/src/org/apache/xalan/lib Extensions.java Log: Modify distinct() extension so that it no longer relies on DOMHelper which is deprecated but uses ExpressionContext.toString(). Revision ChangesPath 1.13 +13 -8 xml-xalan/java

[Bug 2559] New: - Problem with ancestor-or-self

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2559 *** shadow/2559 Tue Jul 10 15:33:55 2001 --- shadow/2559.tmp.29463 Tue Jul 10 15:33:56 2001 *** *** 0 --- 1,44 + ++ + | Problem with ances

RE: Notice for 2.2.0 G/A

Has anyone had a look at the patches I've submitted? They resolve problems we've found in xsltc using the xsl we're developing: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2343 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1407 I'm also continuing to track down the following problem (a

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

jkesselm01/07/10 15:23:55 Modified:java/src/org/apache/xml/dtm/ref/dom2dtm DOM2DTM.java Log: Quick patch to handle case where someone wants to build a DTM from an Element rather than from a Document. The Attr handling might want to move down into addNode. This opens several

Re: Transparent caching with JAXP/TrAX

> This suggests serializing the Templates object (including the translet > class(es)), which makes perfect sense. Yes indeed. > If this proves to be just as efficient as instanciating a > translet class then I may be convinced. Since the class should just be holding a string or two, it should

Re: problems with namespce

Check your CLASSPATH or extensions directory for a SAX parser that comes ahead of Xerces. Gary "Sülter, Uwe" wrote: > > Hi, > > I just tried to use the xalan classes for java and somehow, I alwaysget an exception >which says: Namespace not supported by SAXParser > But the only namespace I'm u

Re: Size Limit in Extension Attributes?

Garry- Thanks for responding... Here's the full stack trace (I'm sure some of it will be wrapped): % java org.apache.xalan.xslt.Process -in test_bad.xml -xsl test.xsl file:///export/home/heddings/tmp/test.xsl; Line 16; Column 30; content: javax.xml.transform.TransformerException

Re: Notice for 2.2.0 G/A

Sorry, I dropped the ball on this. I promise I will work on it tonight. -scott Ovidiu

[Bug 1753] - default decimal-format element not used when imported

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1753 *** shadow/1753 Tue Jul 10 12:12:56 2001 --- shadow/1753.tmp.28575 Tue Jul 10 14:04:26 2001 *** *** 26,29 - Try it with the latest posted build 2.2D06? - Attach both of your .xsl stylesheets and an .xml document tha

[Bug 2554] New: - Xalan/Java 1.3 bus error on SGIs

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2554 *** shadow/2554 Tue Jul 10 13:46:11 2001 --- shadow/2554.tmp.28397 Tue Jul 10 13:46:11 2001 *** *** 0 --- 1,48 + ++ + | Xalan/Java 1.3 bus

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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2553 *** shadow/2553 Tue Jul 10 13:32:20 2001 --- shadow/2553.tmp.28253 Tue Jul 10 13:32:20 2001 *** *** 0 --- 1,36 + ++ + | xsltc fails test a

Re: Size Limit in Extension Attributes?

Jason -- What does the complete stack trace look like? Gary jason heddings wrote: > > Hello folks! > > I'm experiencing what appears to be a limit in the size of an attribute > when using extension functions. > > I've attached the Java source (stripped down to expose the problem) as > well a

[Bug 2552] New: - new -PARAMX needed for xslt.Process.main()

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2552 *** shadow/2552 Tue Jul 10 13:17:28 2001 --- shadow/2552.tmp.28158 Tue Jul 10 13:17:28 2001 *** *** 0 --- 1,24 + ++ + | new -PARAMX needed

problems with namespce

Hi, I just tried to use the xalan classes for java and somehow, I alwaysget an exception which says: Namespace not supported by SAXParser But the only namespace I'm using is xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; and that should be ok. Is there anything special thinks I have to take

Re: Problem with

Paresh -- Can you supply the XSLT document that you're having problems with? Gary Paresh Fozdar wrote: > > My xalan version is not able to recognise xsl:document > it says: > UNKNOWN ELEMENT: > Tell me how can I find some extension or something so that my xalan > recognises this tag. > > I kn

Re: Compilation under Borland C++ Builder 5

If you post the errors, perhaps we can help diagnose them. One thing that's likely is you're missing some of the appropriate defines from the compiler definitions file. I assume you copied the Visual C++ definitions file and used it as a model for the C++ Builder one? Why don't you post the co

Re: problems in using javaExtensions

Kusuma -- Did this problem ever get resolved? Gary > kkumari wrote: > > I am using javaExtensions to do some processing on the node. I am > using the abbreviated syntax as my extension is implemented in Java. > I use > xmlns:java="http://xml.apache.org/xslt/java"; > and while invoking the exte

[Bug 2551] New: - xsltc fails tests axes100,101,103-112

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2551 *** shadow/2551 Tue Jul 10 12:43:27 2001 --- shadow/2551.tmp.28041 Tue Jul 10 12:43:27 2001 *** *** 0 --- 1,20 + ++ + | xsltc fails tests

[Bug 2438] - redirect appear not to create a file on solaris 2.7

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2438 *** shadow/2438 Tue Jul 3 09:23:17 2001 --- shadow/2438.tmp.28005 Tue Jul 10 12:32:25 2001 *** *** 107,110 ! --- 107,115 ! ! ! --- Additional Comments From [E

cvs commit: xml-xalan/test/tests/conf-gold/predicate predicate38.out predicate48.out predicate49.out predicate50.out predicate51.out predicate52.out predicate53.out predicate54.out predicate55.out predicate56.out

curcuru 01/07/10 12:31:47 Modified:test/tests/conf-gold/predicate predicate38.out predicate48.out predicate49.out predicate50.out predicate51.out predicate52.out predicate53.out predicate54.out predicate55.out predi

cvs commit: xml-xalan/test/tests/conf/predicate predicate38.xsl predicate48.xsl predicate49.xsl predicate50.xsl predicate51.xsl predicate52.xsl predicate53.xsl predicate54.xsl predicate55.xsl predicate56.xsl

curcuru 01/07/10 12:31:01 Modified:test/tests/conf/predicate predicate38.xsl predicate48.xsl predicate49.xsl predicate50.xsl predicate51.xsl predicate52.xsl predicate53.xsl predicate54.xsl predicate55.xsl predicate5

Re: node-set as param

In XalanJ2, see the evaluate extension function: http://xml.apache.org/xalan-j/extensionslib.html#evaluate Gary > Dmitri Ilyin wrote: > > Hi *, > > how can I select "node set" and set it as param in temlate call?? > > regards > > Dmitri

RE: RelationalExpr doing alpha comparisons?

Thanks Gary, Sorry to make you look into an already fixed problem. I looked for a bug report before reporting this but didn't find one. I'll try it out with 2.2.D06. -Dave -Original Message- From: Gary L Peskin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 10, 2001 4:04 AM To: [EMAIL

Re: Addition of a new function

Yes, you can do this. Declare the xalan namespace on the root node of your document, like this: xmlns:xalan="http://xml.apache.org/xalan"; Gary shruti wrote: > > Can i use this tokenize function in an XPath query .. > if yes, where do i register the xalan namespace in the evaluation > c

Re: Transparent caching with JAXP/TrAX

Hi Gary, Morten,     We were looking at caching a Templates object for reuse with XSLTC but were a little confused in that it is the newTransformer that does the compilation. The class compiled (the translet) seems to be a Transformer. So caching the Template object is not much use.     One cr

[Bug 1753] - default decimal-format element not used when imported

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1753 *** shadow/1753 Sun May 20 17:27:26 2001 --- shadow/1753.tmp.27704 Tue Jul 10 12:12:56 2001 *** *** 1,19 ! Bug#: 1753 ! Product: XalanJ2 ! Version: 2.0.1 ! Platform: PC ! OS/Version: ! Status: UNCONFIRMED ! Resoluti

Re: How to serialize recursively the content of one node into a String with Xalan J2

Vincent -- Since this is a pure XSLT question, you might want to ask this over on the Mulberry XSL-List. They have a lot of folks over there and someone might have done this before. Gary MAHE Vincent FTRD/DIH/REN wrote: > > Is it possible to serialize as a java string the content of one node

Re: AW: [Xalan-J 2.2.0D6]: Strange problems with DOM and XPath

Carsten -- I deserialized your attachment and noticed that it mixes DOM Level 1 nodes (ElementImpl) with Level 2 nodes (ElementNSImpl). Since things work when you serialize and then reparse, I suspect that DOM2DTM is not handling this situation as you expect. The DOM spec does say "mixing both

RE: node-set as param

Hi Dmitri,   just call       You'll get node-set in parameter "nodeset-param" in template "template-with-nodeset-param".   For instance for XML:                       in xsl:   .             ...                   Is that what you need?  

[Bug 2549] New: - xsltc fails conf test attribvaltemplate08 on char with accent mark

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2549 *** shadow/2549 Tue Jul 10 11:32:52 2001 --- shadow/2549.tmp.27215 Tue Jul 10 11:32:53 2001 *** *** 0 --- 1,69 + ++ + | xsltc fails conf t

cvs commit: xml-xalan/test/tests/conf-gold/message message02.out

curcuru 01/07/10 11:23:10 Modified:test/tests/conf/message message02.xsl test/tests/conf-gold/message message02.out Log: Update message02 to output a root element for DOM testing Revision ChangesPath 1.2 +2 -0 xml-xalan/test/tests/conf/message/

cvs commit: xml-xalan/test/tests/conf-gold/mdocs mdocs16.out

curcuru 01/07/10 11:20:07 Modified:test/tests/conf-gold/mdocs mdocs16.out Log: Update mdocs16 to output a root element so -flavor trax.dom passes; no other changes Revision ChangesPath 1.2 +2 -0 xml-xalan/test/tests/conf-gold/mdocs/mdocs16.out Index: md

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

curcuru 01/07/10 11:19:51 Modified:test/tests/conf/mdocs mdocs16.xsl Log: Update mdocs16 to output a root element so -flavor trax.dom passes; no other changes Revision ChangesPath 1.2 +2 -0 xml-xalan/test/tests/conf/mdocs/mdocs16.xsl Index: mdocs16.xsl

cvs commit: xml-xalan/test/tests/conf-gold/idkey idkey09.out

curcuru 01/07/10 11:15:18 Modified:test/tests/conf-gold/idkey idkey09.out Log: Update idkey09 to output a root element so -flavor trax.dom passes; no other changes Revision ChangesPath 1.2 +2 -1 xml-xalan/test/tests/conf-gold/idkey/idkey09.out Index: id

cvs commit: xml-xalan/test/tests/conf/idkey idkey09.xsl

curcuru 01/07/10 11:15:47 Modified:test/tests/conf/idkey idkey09.xsl Log: Update idkey09 to output a root element so -flavor trax.dom passes; no other changes Revision ChangesPath 1.2 +2 -0 xml-xalan/test/tests/conf/idkey/idkey09.xsl Index: idkey09.xsl

Re: -PARAM command line option

IIRC, the API function is setStylesheetParam(). Will single quotes still be necessary for this function? Also, I still don't see how you can now specify numbers, functions, etc with this new behaviour. Maybe a switch can be made that'll specify old vs new behaviour? Thanks, Noel |+--

[Bug 1133] - Extension namespace also used on LRE gets erroneous decls

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1133 *** shadow/1133 Sun May 20 17:24:06 2001 --- shadow/1133.tmp.27130 Tue Jul 10 11:01:09 2001 *** *** 1,19 ! Bug#: 1133 ! Product: XalanJ2 ! Version: 2.0.1 ! Platform: PC ! OS/Version: All ! Status: NEW ! Resolution:

[Bug 2548] - Multiple xsl:attribute-set with identical name incorrect

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2548 *** shadow/2548 Tue Jul 10 10:54:18 2001 --- shadow/2548.tmp.27107 Tue Jul 10 10:55:34 2001 *** *** 17,20 TestID: attribset42.xsl; attribset43.xsl With XalanCVS 10-Jul-01 10:30am these two tests fail; apparently a c

[Bug 2548] New: - Multiple xsl:attribute-set with identical name incorrect

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2548 *** shadow/2548 Tue Jul 10 10:54:18 2001 --- shadow/2548.tmp.27096 Tue Jul 10 10:54:18 2001 *** *** 0 --- 1,20 + ++ + | Multiple xsl:attri

[Bug 1670] - xsl:include behaviour depends on StreamSource constructor

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1670 *** shadow/1670 Tue Jul 10 08:40:34 2001 --- shadow/1670.tmp.27021 Tue Jul 10 10:46:32 2001 *** *** 88,90 --- 88,97 It seems that the systemId is used to create an InputStream or Reader rather than a java.i

RE: Notice for 2.2.0 G/A

Ovidiu wrote: >> 2) Does anyone need to apply for any priority-one bugs being fixed? > How about the source node info patch that I've submitted few weeks > ago? I would like to see it in the next release if it's possible. +1 Though it's not that high a priority for me.

RE: Transparent caching with JAXP/TrAX

> I think that XSL stylesheets should be treated like > JSP's, if the source changes on the "application server" then they should be > recompiled This is absolutely fine at the server level. I just think the mechanism that decides this should be above the processor level. The processor has eno

Re: Notice for 2.2.0 G/A

Sorry, I meant to do it last weekend, but... I'll work on it later today. -scott Ovidiu

Compilation under Borland C++ Builder 5

Hi! I'm trying to compile Xalan under C++ Builder 5 but I have a lot of problems with wide characters in the XalanDOMString implementation. Strange because Xerces 1.4.0 compile well. Did someone has already compile Xalan under C++Builder5 ? or have binaries for it ? Thanks in advance. Christ

Size Limit in Extension Attributes?

Hello folks! I'm experiencing what appears to be a limit in the size of an attribute when using extension functions. I've attached the Java source (stripped down to expose the problem) as well as the XSL document I'm using. I've created files of size ~32K and ~33K (not attached -- I left them o

Re: Transparent caching with JAXP/TrAX

[EMAIL PROTECTED] wrote: > As the main designer of TrAX, I can testify that > TransformerFactory#newTemplates() was always meant as a compilation step, > though hiding the details of whether it compiles into a Java class or it > creates a StylesheetRoot like object. If you can persistently store

cvs commit: xml-xalan/test/tests/conf/impincl impincl12.xsl

curcuru 01/07/10 10:29:01 Removed: test/tests/conf/impincl impincl12.xsl Log: Remove network-specific tests, especially ones to private hosts! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-

Re: -PARAM command line option

It doesn't really matter to me which way this is implemented but now that it's done, I think we should not keep changing it. The advantage of the old way was that it was more flexible because you could pass in XPaths and non-strings. However, this flexibility came at a price of increased confusi

[Bug 2537] - the first attribute is ignored by the XSL parser

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2537 *** shadow/2537 Tue Jul 10 06:57:28 2001 --- shadow/2537.tmp.26415 Tue Jul 10 10:15:46 2001 *** *** 15,18 ++ |

cvs commit: xml-xalan/java/src/org/apache/xpath/axes DescendantIterator.java

mmidy 01/07/10 10:14:26 Modified:java/src/org/apache/xpath/axes DescendantIterator.java Log: Fix problem with descendant-or-self and from root pattern. When from root, descedant or self was not recognized. Revision ChangesPath 1.10 +3 -2 xml-xalan/java/src/o

cvs commit: xml-xalan/test viewResults.xsl

curcuru 01/07/10 10:03:41 Modified:test viewResults.xsl Log: Remove document($bugfile)... since we currently don't use bugs.xml Revision ChangesPath 1.7 +3 -1 xml-xalan/test/viewResults.xsl Index: viewResults.xsl

Re: need help converting from older xalan.jar and xerces.jar to the latest

For Xalan questions, please followup-to: [EMAIL PROTECTED] http://xml.apache.org/xalan-j/ is the full documentation set for the latest Xalan build, which for your purposes is probably close enough to 2.1.0 to use. The XSLTProcessor class is deprecated and going away Very Soon Now. You should co

Re: Transparent caching with JAXP/TrAX

As <[EMAIL PROTECTED]> wrote: > Different environments, and different users, do want > different cache management policies. I think it's clear from just a couple of days discussion here that this is quite true! Personally, I'd like to work on getting xsltc integrated into more of the javax.xml.t

node-set as param

Hi *,   how can I select  "node set" and set it as param in temlate call??   regards   Dmitri

[Bug 1670] - xsl:include behaviour depends on StreamSource constructor

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1670 *** shadow/1670 Thu Jun 14 07:16:57 2001 --- shadow/1670.tmp.25204 Tue Jul 10 08:40:34 2001 *** *** 79,81 --- 79,90 * @param systemId The system identifier as a URL string. */ public void setSys

Re: Notice for 2.2.0 G/A

Scott, On Tue, 3 Jul 2001 07:42:12 -0400, [EMAIL PROTECTED] wrote: > We think we're about ready to do a 2.2.0 G/A (General Availability) in the > next couple of weeks. Questions: > > 1) Do the XSLTC folks have any problem with this? > > 2) Does anyone need to apply for any priority-one bugs b

RE: Transparent caching with JAXP/TrAX

yeah I suppose.. I was looking at it from a Production/Test environment point of view... re your other post, I think that XSL stylesheets should be treated like JSP's, if the source changes on the "application server" then they should be recompiled -Original Message- >Shouldnt the appli

RE: RelationalExpr doing alpha comparisons?

Hi Everett, I feel I lucked into a great reference with Michael Kay's XSLT Programmer's Reference. He explains there that when one of the entities being compared is a node it takes the type of the other, so making one node a number was sufficient. Cute huh? According to him, and as Gary verifi

Re: -PARAM command line option

It changed because so many people complained about the XalanJ 1.x behavior. The question is whether you want -PARAM to get an expression or a literal value. Too many people did -PARAM someValueWithoutQuotes and were surprised when they didn't get anything in their parameter. I don't think I wan

Re: Transparent caching with JAXP/TrAX

Morten Jorgensen <[EMAIL PROTECTED]> wrote: > Why does TransformerFactory.newTemplates() have to compile the input > stylesheet if there is already a stored class definition for the translet? As the main designer of TrAX, I can testify that TransformerFactory#newTemplates() was always meant as a

cvs commit: xml-xalan/test/java/src/org/apache/qetest/xsl TraxDatalet.java

curcuru 01/07/10 08:08:41 Added: test/java/src/org/apache/qetest/xsl TraxDatalet.java Log: Simplified datalet works better with existing tests; User sets Name or URL or Stringdata, gets back Sources, etc. Revision ChangesPath 1.1 xml-xalan/test/java/

[Bug 2538] - xsltc does not merge attrib sets with same name

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2538 *** shadow/2538 Tue Jul 10 07:47:14 2001 --- shadow/2538.tmp.24987 Tue Jul 10 07:50:47 2001 *** *** 59,62 text-decoration="none" because the value directly defined in the copy element should override any definition

[Bug 2538] New: - xsltc does not merge attrib sets with same name

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2538 *** shadow/2538 Tue Jul 10 07:47:14 2001 --- shadow/2538.tmp.24973 Tue Jul 10 07:47:14 2001 *** *** 0 --- 1,62 + ++ + | xsltc does not mer

Re: Transparent caching with JAXP/TrAX

Hi Scott, [EMAIL PROTECTED] wrote: > > But, this means that the stylesheet > > is compiled every time the user wants to instanciate a translet _object_. > > No. A stylesheet is compiled everytime a user wants to instanciate a > Templates object. When they use a Transformer object, it simply cr

Re: Transparent caching with JAXP/TrAX

> Jeff Winter wrote: > > > Why does TransformerFactory.newTemplates() have to compile the input > > stylesheet if there is already a stored class definition for the translet? > > Here's my two cents: I'm not sure why it would necessarily "have" to compile > the input each time, but the benefit i

Re: Transparent caching with JAXP/TrAX

Morten Jorgensen <[EMAIL PROTECTED]> wrote: > Why would anyone bother to use compiled stylesheets if they have to > be compiled for every transformation (or sequence of transformations)? I didn't say that they should be recompiled for every transformation. A Templates object should be created o

Re: XSLTC Source Diff

Erwin, Thanks a million for all your effort! You are the first 'external' contributor to the XSLTC code, so congratualtions. I'll buy you a pint if you come over to Dublin for the Apache conference later this year... I could not apply the diffs directly as some of the source code has changed dra

[Bug 2537] New: - the first attribute is ignored by the XSL parser

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2537 *** shadow/2537 Tue Jul 10 06:57:28 2001 --- shadow/2537.tmp.24263 Tue Jul 10 06:57:28 2001 *** *** 0 --- 1,18 + ++ + | the first attribut

RE: Transparent caching with JAXP/TrAX

>Shouldnt the application look after whether or not the stylesheet has >changed or not. i.e. is the cache up to date? Not all saved changes are ready to be tested. Yes, one can maintan separate editing and testing directories, but it's also convenient to just be able to say "refresh when I tell

Re: Transparent caching with JAXP/TrAX

>But I still don't think that every call to newTemplates() should >necessarily require re-compilation - we should at least offer the option >of caching between sessions. I suspect what you're trying to emulate is the Java compiler, which is generally smart enough to load an existing classfile if

[Bug 2536] New: - imerged attrib sets with redundant attribs last one applies

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2536 *** shadow/2536 Tue Jul 10 06:40:30 2001 --- shadow/2536.tmp.24038 Tue Jul 10 06:40:30 2001 *** *** 0 --- 1,43 + ++ + | imerged attrib set

-PARAM command line option

In xalan 1.x, I used to have to wrap the values in single quotes (ie -PARAM variable-name "'variable-value'"). I think the old way was more consistent (eg the parameter gets replaced with exactly what you set it to). Why has this changed in xalan 2.x? How are number values to be passed in? Can

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

curcuru 01/07/10 06:25:47 Added: test/java/src/org/apache/qetest/xalanj2 FactoryFeatureTest.java Log: Basic functionality of transforms with Xalan-J 2.x setAttributes Revision ChangesPath 1.1 xml-xalan/test/java/src/org/apache/

Re: Antwort: RE: Xalan 2.2.0D6 has great performance gain!

>I have a question to the maximum number of nodes. Is there a way to process >more nodes or is this planned. The problem is that DTM is using an int as its internal reference to a node, and some of those bits are reserved to select between DTM instances. We can certainly trade off more nodes aga

[Bug 2535] New: - xsltc fails attribset24, outputting a double ns prefix

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2535 *** shadow/2535 Tue Jul 10 06:15:20 2001 --- shadow/2535.tmp.23980 Tue Jul 10 06:15:21 2001 *** *** 0 --- 1,94 + ++ + | xsltc fails attrib

Re: more on this ....Re: stylesheet requires attribute: version

>Forgive me for my ignorance, but, syntactically, what is the : >namespaceURI >qualifiedName >value Qualified Name and Namespace URI are terms defined by the XML Namespaces spec. In brief, the Qualified Name is the nodename including namespace prefix if any, the namespace URI is the namespace wh

Re: more on this ....Re: stylesheet requires attribute: version

If you're using XSLT, you really want to use the Level 2 DOM, and specifically the namespace-aware factory methods createElementNS() and createAttributeNS()/setAttributeNS rather than the old createElement and createAttribute/setAttributes calls. Failing to do so will yield a DOM that does not su

RE: Transparent caching with JAXP/TrAX

>> Why does TransformerFactory.newTemplates() have to compile the input >> stylesheet if there is already a stored class definition for the translet? >Here's my two cents: I'm not sure why it would necessarily "have" to compile the input each time, but the benefit >is that you can change the st

RE: Transparent caching with JAXP/TrAX

Title: RE: Transparent caching with JAXP/TrAX > Why does TransformerFactory.newTemplates() have to compile the input > stylesheet if there is already a stored class definition for the translet? Here's my two cents: I'm not sure why it would necessarily "have" to compile the input each time,

Re: Transparent caching with JAXP/TrAX

Gary L Peskin wrote: > I may be missing something here and I'm sure Scott will jump in but here > is my understanding of things. I don't really think that TRaX has "... > loads of crap ... that most users will never bother even looking at" but > I could be wrong there too. "Crap" is a badly chos

  1   2   >