Hi Scott,
First, sorry for the lame bug report. I understand that i'm putting a mess
on the process by doing this. Did simply lost my brain on this one. You have
the right to kill me next time.
Apart from that, your fix works like a charm.
I'm also (and I'm sure you will) be very pleased to see
Hi,
I have a question to the maximum number of nodes. Is there a way to process
more nodes or is this planned.
The number of 1048575 nodes may be reached by data exchanging
applications.
Regards
Thomas
dbertoni01/07/09 22:15:53
Modified:c/src/XPath XPathEvaluator.hpp
Log:
Updated comments.
Revision ChangesPath
1.2 +3 -3 xml-xalan/c/src/XPath/XPathEvaluator.hpp
Index: XPathEvaluator.hpp
==
ok, I've sussed this out.
I'm posting this here so that the next person who has the problem can find something.
(sorry to those who have already got their head around namesapce nodes)
How to generate an XSL file on the fly as a DOM document using JAXP.
warning: If prior attempts do not work,
Etienne --
The DOM is explained in the W3C DOM Recommendation. Xerces, used by
Xalan, implements most or all of Level 2, the Core of which you can find
here: http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html
Your attributes don't need to be in a namespace, just the element. Th
There is absolutely no way we can help you unless you can supply more
information to help diagnose the problem.
"The problem may be at libstdc++" is not very helpful. Please provide
exact error messages and file names for the messages.
Dave
We have no plans at present for a FreeBSD port, although contributions for
ports are always welcome.
Dave
jimmy
For the description of what XPath considers a number, see the
recommendation:
http://www.w3.org/TR/xpath#numbers
An explicit call to number() has the same semantics as an implicit
conversion to number. Locale-specific information is _not_ taken into
account, so if your processor is converti
I can not compile Xalan (event samples) with gcc
2.96 of RedHat 7.1. The problem may be at libstdc++.
Please help me,
thanks.
What is the exact format of the "numeric" data as text?
I've found that "1000.00" will be treated as a number,
but "1,000.00" will not. However, number() always seems
to work, though I've not experimented with the effects of
mixing formats. (Say, "1.000,00" in the XML, but "1,000.00"
in the J
Gary,
There is something about namespaces I have missunderstood, and the documentation
for doing this stuff (in java) is practically non-existent (or very well hidden).
Forgive me for my ignorance, but, syntactically, what is the :
namespaceURI
qualifiedName
value
required for setAttributeNS ?
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1334
*** shadow/1334 Sun May 20 17:25:12 2001
--- shadow/1334.tmp.18360 Mon Jul 9 19:42:16 2001
***
*** 1,19
! Bug#: 1334
! Product: XalanJ2
! Version: 2.0.1
! Platform: All
! OS/Version: Windows NT/2K
! Status: NEW
! Re
Etienne --
This is not correct because you are not putting these elements into a
namespace. You need to use createElementNS to create an element in the
namespace.
Gary
Etienne Deleflie wrote:
>
> Hi,
>
> more on this dynamic XSL DOM document creation. Perhaps I am not creating the
> DOM docu
Hi,
more on this dynamic XSL DOM document creation. Perhaps I am not creating the
DOM document correctly (even though it prints out correctly)
... I am setting both the attributes of the root node (version and
xmlns:xsl)
http://www.w3.org/1999/XSL/Transform";>
by doing the following
Hi,
I was wondering if you have any plans of adding freeBSD as
a supported platform and if yes, in what time frame.
Thanks!
Jim
Hello,
thanks for your reply.
I just tried setting name space awareness on the DocumentFactoryBuilder (i'm
using JAXP)
so now,
myBuilder.isNamespaceAware() returns true.
... but I am still getting the same error !
etienne
Gary L Peskin wrote:
> I'm not sure how you're building myDomD
Thanks. Got it. I should be able to look into this later today.
Gary
Dave wrote:
>
> A couple little corrections: The example makes more sense if you reverse
> the numeric values in the HighestNumber and Number nodes in the XML. This
> way, the relevant xsl:when test doesn't get triggered w
A couple little corrections: The example makes more sense if you reverse
the numeric values in the HighestNumber and Number nodes in the XML. This
way, the relevant xsl:when test doesn't get triggered when it should. The
other thing is that in my final example, I should have said rather than .
I've committed this change as well as the "challanges" misspelling.
Thanks for reporting these problems.
Gary
Alexey Mahotkin wrote:
>
> --- faq.xml Tue Jul 3 19:30:13 2001
> +++ faq.xml-new Sun Jul 8 02:08:55 2001
> @@ -151,7 +151,7 @@
>
>
>
> - How does I use the "sig
garyp 01/07/09 17:06:44
Modified:java/xdocs/sources/design design2_0_0.xml
java/xdocs/sources/xalan faq.xml
Log:
Correct typos reported by Alexey Mahotkin <[EMAIL PROTECTED]>
Revision ChangesPath
1.5 +1 -1 xml-xalan/java/xdocs/sources/design/d
I'm not sure how you're building myDomDocument but it sounds like you
may not have namespace support turned on in your DOM builder. If that
is the case, please let me know so that I can include this as a FAQ
since it does come up from time to time.
Gary
Etienne Deleflie wrote:
>
> Hello,
>
>
Hello,
I am writing an XSL stylesheet on the fly, as a DOM document.
Printed out, it looks like this ...
http://www.w3.org/1999/XSL/Transform";>
Strange thing is, when I use Xalan thus .
transformer = factory.newTransformer( new DOMSource( myDomDoc
Gary,
Thanks for your response. I'm using Xalan 2.1.0. I'm invoking xalan
through the JAXP interface in my Java code. Here's the XML and XSLT I'm
working with. The XSLT is in the simplified stylesheet format:
XML:
100
5
XSLT:
http://www.w3.org/1999/XSL/Transform"; xsl:version="1.0">
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2523
*** shadow/2523 Mon Jul 9 16:06:09 2001
--- shadow/2523.tmp.16558 Mon Jul 9 16:07:55 2001
***
*** 38,41
--- Additional Comments From [EMAIL PROTECTED] 2001-07-09 16:06 ---
Thank you for pointing this out.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2524
*** shadow/2524 Mon Jul 9 16:04:14 2001
--- shadow/2524.tmp.16550 Mon Jul 9 16:07:54 2001
***
*** 2,9
| org.apache.xalan.lib.Extension.evaluate() throws exception all the time|
+---
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2523
*** shadow/2523 Mon Jul 9 16:02:26 2001
--- shadow/2523.tmp.16536 Mon Jul 9 16:06:09 2001
***
*** 33,36
XPathContext xctxt = (XPathContext) myContext;
will also fail. myContext should be cast to the 'this' p
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2524
*** shadow/2524 Mon Jul 9 16:04:14 2001
--- shadow/2524.tmp.16505 Mon Jul 9 16:04:14 2001
***
*** 0
--- 1,36
+ ++
+ | org.apache.xalan.l
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2523
*** shadow/2523 Mon Jul 9 16:02:26 2001
--- shadow/2523.tmp.16491 Mon Jul 9 16:02:26 2001
***
*** 0
--- 1,36
+ ++
+ | org.apache.xalan.l
Dave --
I think that Michael Kay is correct on this. It may be a bug in Xalan.
What version of Xalan are you using and can you supply working XML and
XSLT examples that will allow us to reproduce the problem?
Gary
Dave wrote:
>
> According to Michael Kay, a relational comparison doesn't comp
According to Michael Kay, a relational comparison doesn't compare strings,
but converts strings to numbers if possible and compares numeric values.
When for example this element is evaluated by Xalan in my stylesheet:
where number and highest number contain numbers.
It seems to compare the tw
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2520
*** shadow/2520 Mon Jul 9 13:18:32 2001
--- shadow/2520.tmp.14922 Mon Jul 9 13:18:32 2001
***
*** 0
--- 1,34
+ ++
+ | keyword only attri
--- faq.xml Tue Jul 3 19:30:13 2001
+++ faq.xml-new Sun Jul 8 02:08:55 2001
@@ -151,7 +151,7 @@
- How does I use the "signature" file to verify my download?
+ How do I use the "signature" file to verify my download?
For each Xalan download fil
"Matthew L. Avizinis" <[EMAIL PROTECTED]> wrote:
> In my testing,
> the output element with the method attribute set to text but without the
> encoding attribute emits the two character output you describe in para 2
> below.
On mine too. I must have misphrased that.
BTW, the XSLT spec states t
Sorry, not at this time. What would be cool is if you could just serialize
the stylesheet into a character stream, and get a clean XSLT stylesheet.
I've long wanted to do this, but it has never risen high enough on the
priority list.
Since the StylesheetRoot/Templates object implements a minima
Hi,
I need to write some code to create a "merged" stylesheet resulting from
composing a source stylesheet and all of its imports and includes. I thought
that I might be able to use Xalan's templates package to do this, but I
can't figure out how.
Is it possible to get a String repesentation of
You are correct on all counts, with possibly one exception. In my testing,
the output element with the method attribute set to text but without the
encoding attribute emits the two character output you describe in para 2
below.
I have seen the Lite. It's ice cold too. :-)
thanks much,
Matthew L
> This is documented here :
> http://xml.apache.org/xalan-j/xsltc/xsltc_trax.html#templatescreation as
> sems to fit your model.
Sorry, I'm a confused guy. I see the docs, and seem to remember from
previous conversations with Todd that he was going to do this, but I don't
see the code anywh
Dave,
What was happening was that I was sending an ASCII extended character to
the template and it was spitting out two characters, just as you suggest in
#2 below. Using both #1 and #2 has removed the problem. I, as a human, was
assuming text output so it didn't occur to me that I had to spec
curcuru 01/07/09 11:36:30
Modified:test/java/src/org/apache/qetest/trax
TransformerFactoryAPITest.java
Log:
Added testCase7 with getFeature, set/getAttribute tests;
Note assumption that any factory we test must support Streams
(would be pretty silly if so
Call to extension function failed: method call/new failed:
java.lang.reflect.Inv
ocationTargetException target exception: java.lang.OutOfMemoryError
Does anyone know how to resolve this? Thanks.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2517
*** shadow/2517 Mon Jul 9 11:24:06 2001
--- shadow/2517.tmp.13676 Mon Jul 9 11:24:07 2001
***
*** 0
--- 1,86
+ ++
+ |
Hi Scott,
[EMAIL PROTECTED] wrote:
>Morten Jorgensen <[EMAIL PROTECTED]> wrote:
>
>>and
>>we don't want to compile such classes more often than we have
>>to, and this is the reason why we want cache translets.
>>
>
>My position is that the XSLT processor should not be doing caching. I have
>sai
XalanJ2 uses reflection for processing of the stylesheet, which turns out
to be really slow on some environments -- much slower than I had realized.
This is something I'm going to have to do some work on real soon.
-scott
> Would it not make more sense to focus on
> deallocation first instead of trying to make the implementation more
> compact?
Well, deallocation can only occur in some cases. But I agree that
deallocation is probably more important.
> FWIW, I had hoped to be able to devote some time to the deal
Hi,
Before using Xalan-j2.2, I was using Xalan version 1. Please refer to the
lines below.
XSLTProcessor processor = XSLTProcessorFactory.getProcessor();
XSLTInputSource xslinput = new XSLTInputSource(new
FileInputStream(new File(styleSheetPath, sheetLocation)));
Styleshe
curcuru 01/07/09 10:04:44
Added: test/tests/api/xalanj2 TransformState99a.xml
TransformState99a.xsl TransformState99b.xml
TransformState99b.xsl TransformState99binc.xsl
TransformState99c.xml TransformState99c.xsl
curcuru 01/07/09 10:03:25
Added: test/java/src/org/apache/qetest/xalanj2
TransformStateDatalet.java TransformStateTest.java
TransformStateTestlet.java
Log:
New tests for TransformState; only partly validated so far
Revision Cha
Morten Jorgensen <[EMAIL PROTECTED]> wrote:
> and
> we don't want to compile such classes more often than we have
> to, and this is the reason why we want cache translets.
My position is that the XSLT processor should not be doing caching. I have
said this many times and I will continue to say
My two cents (maybe a bit less). Would it not make more sense to focus on
deallocation first instead of trying to make the implementation more
compact? Especially since you had mentioned that there may be an expense in
execution speed for a more compact implementation, there is a known
limitation
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2445
*** shadow/2445 Fri Jul 6 09:37:22 2001
--- shadow/2445.tmp.12501 Mon Jul 9 08:57:15 2001
***
*** 243,245
--- 243,268
on. I did a search for SAXParserFactory, and found it in JaxpParser, and do
see setNames
Tom/Dick/Harry/anybody,
We are trying to come up with a decent design for transparent
translet caching with JAXP/TrAX. Please let me first make a
distinction between caching javax.xml.transform.Transformer
objects and caching Translet classes. A Transformer object can
be instanciated (using a fac
Stephane, thank you for the bug report. I replicated the bug, and just
checked in a fix. I sent you a jar offline to try.
It is better for us if you can post bug reports to
http://nagoya.apache.org/bugzilla/. It helps us track them, do triage on
them, and create regression tests.
-scott
sboag 01/07/09 08:17:18
Modified:java/src/org/apache/xalan/transformer TransformerImpl.java
Log:
In executeChildTemplates, somehow there was a popMode without
a corresponding pushMode. The pushMode was added.
Addresses bug posted by Stephane Bailliez <[EMAIL PROTECTED]>
on
Hello,
Does anyone out there have a copy of xalan built using the above C++
compiler. The xalan 1 1 we have here does not compile !
Martin
Actually, the appropriate place to ask this kind of
question is over on [EMAIL PROTECTED] The
[EMAIL PROTECTED] list is for cross-project and
administrative issues. (I'm also cc:ing xalan-dev for
the time being, since it's more active until we get
people to move to xalan-j-users)
Have you tried
I just gave a try to Xalan 2.2D6.
Besides the fact that I have apparently some EOL spitted out to the console
(that do not show up in Xalan 2.0), it crashes after some successful output.
Ths stylesheet makes heavy use of the redirect extension to generate some
javadoc-like report.
If you have any
Indeed, this is probably because it needs a GNU compatible version of tar.
See http://jakarta.apache.org/ant/manual/CoreTasks/tar.html for details.
As a matter of fact, it won't work with default Solaris tar command.
So Shane recommandation is valid:
You can either upgrade your tar command or d
57 matches
Mail list logo
