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=2961
Hi,
i am getting a Null Pointer Exception in the importNode function while
importing a node to a new document .
importNode does not support some node types. Which are those node types? How
to handle such node types then ?...
public Document domResult (XObject objXObject)
{
DocumentBuilderFacto
Xalan-Dev,
I apologize for sending to this list, but I could not find a user
list at http://xml.apache.org/mail.html
Upon trying to build Xalan on Red Hat Linux 7.1,
the build stopped at the file XMLSupport/FormatterToHTML.cpp.
The compiler basically went into a hot loop, and sucked up
99% of th
sboag 01/08/01 19:12:42
Added: test/tests/bugzilla Bugzilla2945.out Bugzilla2945.xml
Bugzilla2945.xsl
Log:
Test for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2945
I guess I have to create a Testlet for these?
Revision ChangesPath
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=2945
sboag 01/08/01 19:04:17
Modified:java/src/org/apache/xml/dtm DTMAxisIterator.java
java/src/org/apache/xml/dtm/ref DTMAxisIteratorBase.java
DTMDefaultBaseIterators.java
java/src/org/apache/xpath/axes OneStepIterator.java
Log:
Ad
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=2945
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=2559
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=1561
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=1426
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=1378
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=1270
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=1209
Scott is going to be working tomorrow on a real fix so that you should
be able to revert back to your original code when he's done.
Gary
John Gentilin wrote:
>
> I just wanted to know if your workaround was going to
> be the fix or if there was a more "correct" fix. I don't
> mind changing the
I just wanted to know if your workaround was going to
be the fix or if there was a more "correct" fix. I don't
mind changing the code, just wanted to know if there
was more to test. The workaround works as it did before,
just with the workaround.
Gary L Peskin wrote:
> Scott --
>
> I'm a littl
I'll give it a try tonight or tomorrow, while it is still fresh in my mind.
-scott
Gary L Peskin
Scott --
I'm a little backed up on an important project for work at the moment.
If you have time, that would be great. Otherwise I should be freed up
late Friday/early Monday.
John --
Use the workaround for now. In what way does this not work as it did
before?
Gary
[EMAIL PROTECTED] wrote
Yes. This was a problem, which you were not having, that caused
incorrect results when a parameter was -not- passed in at all and the
default value was being used.
Gary
John Gentilin wrote:
>
> Scott,
>
> There was actually a second thread on the same subject
> yesterday, "XSL Parameters and
"Swanson, Brion" wrote:
> The part that is most intriguing to me is that the JAXP stuff would 'sniff'
> a directory in the CLASSPATH and grab JAR files that aren't EXPLICITY listed
> in the CLASSPATH.
This doesn't happen. How are you invoking XalanJ? Does it do this from
the command line? If s
Brion --
You must be looking at some old code because I couldn't find that line.
All I can find is a reference to the now static method createDocument()
in the DOMHelper class. I believe that this is here only temporarily as
we transition away from some of the old interfaces. In any event, it
Scott,
There was actually a second thread on the same subject
yesterday, "XSL Parameters and DOM Nodes". A response
from you stated that you had checked in some code to fix the
problem. Different problem ??
JG
[EMAIL PROTECTED] wrote:
> Dunno. Gary, what's your summary at this point? Do you
My coworker has tried Xalan 2.2.x with our system, and unfortunately,
there's still a few too many bugs to be able to use it for our production
system.
It was just an interesting/annoying little quirk that I discovered and
thought you guys should know about just in case someone else ran into the
Dunno. Gary, what's your summary at this point? Do you want to try
something or should I?
> but it still
> does not work as it did before.
I would like it to work as before. To date, I don't think any work has
been done to make it so.
-scott
Hey - that wasn't that long. Pretty good description too - thanks!
(Although as you noted true bugfix help comes more quickly to those who
include the calling code and especially the printStackTrace() output...
;-)
Yes, JAXP has a 'magic' lookup system; yes, in previous Xalan builds
the last-dit
Sun claims that 1.4 has much better performance with regards to
reflection
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 4:50 AM
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'; 'Stephane Bailliez'
Subject: RE: xalan-j 2.2-D6
XalanJ
I found the following snippet of code in
org.apache.xalan.transformer.TransformerImpl.java:
public ContentHandler createResultContentHandler(
Result outputTarget, OutputProperties format) {
// ...code skipped...
if (null != outputNode)
{
// ...more code i
dleslie 01/08/01 13:14:37
Modified:java/xdocs/sources/xalan samples.xml
Added: java/xdocs/sources/xalan xmlfilters.gif
Log:
Added Todd Miller diagram for UseXMLFilters.
Revision ChangesPath
1.36 +3 -2 xml-xalan/java/xdocs/sources/xalan/samples.xml
I may have found a minor bug in the interaction between Xalan and JAXP
regarding the DocumentBuilder(Factory) class(es).
Simply put, when I upgraded Xalan1 to Xalan 2.1.0 and placed the jar file in
the same directory as a pre-existing crimson.jar file, my application
started spewing exceptions ab
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=2954
Wow, I got my moneys worth on that one. I sort of had my head
in the sand cranking out the unit test code for the SQL Extensions
and I am a little confused with the outcome.
Do I need the code Gary outlined in bugzilla or should it work as
before after Scott's check in ??
I just tested it, and w
tmiller 01/08/01 12:24:04
Added: java/src/org/apache/xalan/xsltc/trax SAX2DOM.java
Log:
work in progress, converted needed for DOMResult
Revision ChangesPath
1.1 xml-xalan/java/src/org/apache/xalan/xsltc/trax/SAX2DOM.java
Index: SAX2DOM.java
===
tmiller 01/08/01 12:23:22
Modified:java/src/org/apache/xalan/xsltc/trax TransformerImpl.java
DOM2SAX.java
Log:
add support for DOMResult handling
Revision ChangesPath
1.10 +26 -7
xml-xalan/java/src/org/apache/xalan/xsltc/trax/Transformer
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=2952
dmarston01/08/01 12:07:38
Added: test/tests/conf-gold/idkey idkey49.out
Log:
New test of generate-id() and document() nodes.
Revision ChangesPath
1.3 +2 -16 xml-xalan/test/tests/conf-gold/idkey/idkey49.out
dmarston01/08/01 12:05:49
Added: test/tests/conf/idkey idkey49d.xml idkey49.xsl idkey49a.xml
idkey49b.xml idkey49c.xml idkey49.xml
Log:
New test of generate-id() and document() nodes.
Revision ChangesPath
1.1 xml-xalan/test/test
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
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
dmarston01/08/01 11:47:46
Modified:test/tests/conf-gold/match match08.out
Added: test/tests/conf-gold/match match17.out match18.out
match19.out match20.out match21.out match22.out
match23.out match24.out match25.out match26.out
L
dmarston01/08/01 11:46:20
Modified:test/tests/conf/match match08.xsl match08.xml
Added: test/tests/conf/match match17.xml match17.xsl match18.xml
match18.xsl match19.xml match19.xsl match20.xml
match20.xsl match21.xml match21.xsl m
johng 01/08/01 11:37:27
Modified:java/src/org/apache/xalan/lib/sql XConnection.java
Log:
Update after building Unit Test's
Submitted by: John Gentilin
Revision ChangesPath
1.19 +78 -47xml-xalan/java/src/org/apache/xalan/lib/sql/XConnection.java
Index: X
johng 01/08/01 11:36:09
Added: java/samples/extensions/sql/streamable dbinfo.xml
Log:
Added dbinfo.xml, needed by Process for -IN parameter
Submitted by: John Gentilin
Revision ChangesPath
1.3 +0 -0 xml-xalan/java/samples/extensions/sql/streamable/dbinfo
johng 01/08/01 11:34:57
Added: java/samples/extensions/sql/show-error dbinfo.xml
Log:
Added dbinfo, needed by -IN parameter for Process
Submitted by: John Gentilin
Revision ChangesPath
1.3 +0 -0 xml-xalan/java/samples/extensions/sql/show-error/dbinfo.xml
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=2951
johng 01/08/01 11:32:34
Modified:java/samples/extensions/sql/streamable pivot.xsl
Log:
dded new connect method and error checking
Submitted by: John Gentilin
Revision ChangesPath
1.2 +24 -13xml-xalan/java/samples/extensions/sql/streamable/pivot.xsl
Ind
johng 01/08/01 11:30:32
Added: java/samples/extensions/sql/show-error invalidConn.xsl
invalidPQuery.xsl invalidQuery.xsl
Removed: java/samples/extensions/sql/show-error dbtest.xsl
Log:
dded new error test cases
Submitted by: John Gentilin
Rev
johng 01/08/01 11:29:16
Modified:java/samples/extensions/sql/pquery dbtest.xsl
Log:
dded new connect method and error checking
Submitted by: John Gentilin
Revision ChangesPath
1.3 +22 -2 xml-xalan/java/samples/extensions/sql/pquery/dbtest.xsl
Index: db
johng 01/08/01 11:28:37
Modified:java/samples/extensions/sql/ext-connection dbtest.xsl
Log:
Added new connect method and error checking
Submitted by: John Gentilin
Revision ChangesPath
1.3 +19 -1 xml-xalan/java/samples/extensions/sql/ext-connection/dbtest.x
johng 01/08/01 11:27:43
Modified:java/samples/extensions/sql/basic-connection
dbtest-cinfo.xsl dbtest.xsl
Log:
Added the new connect mechinism and error checking
Submitted by: John Gentilin
Revision ChangesPath
1.2 +20 -1
xml-xalan/
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=2930
mmidy 01/08/01 09:50:33
Modified:java/src/org/apache/xalan/processor XSLTAttributeDef.java
Log:
Fix for Bugzilla 2930. Fix from Alexander Rudnev. Handle namespaced elements.
Revision ChangesPath
1.20 +2 -1
xml-xalan/java/src/org/apache/xalan/processor/XSLTAt
At 01/08/2001 16:58:08, [EMAIL PROTECTED] wrote:
# The release should happen within the next two weeks.
#
# If you're going to modify the build system, then I think it's going to be
# more difficult for you to do the integration. I strongly suggest you
# reconsider that decision.
I shall ta
The release should happen within the next two weeks.
If you're going to modify the build system, then I think it's going to be
more difficult for you to do the integration. I strongly suggest you
reconsider that decision.
Dave
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=2948
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=2517
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=2931
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=2313
At 01/08/2001 14:50:47, [EMAIL PROTECTED] wrote:
# It should be quite soon. Someone has generously contributed the necessary
# changes, although I haven't had time to get them in yet.
#
# They will be integrated before we do the next release.
#
# Dave
Excellent, thankyou. When will the next
It should be quite soon. Someone has generously contributed the necessary
changes, although I haven't had time to get them in yet.
They will be integrated before we do the next release.
Dave
You could use expat, but since we require Xerces to be there, I doubt
there's any benefit to it. You'll end up writing and testing a bunch of
integration code and that seem to me a waste of time.
I'm curious as to why you think the Xalan-C++ sources are "split across
several platforms". There
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=2859
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=2832
Just wanted to let you know I haven't forgotten about this. I'm still
trying to decide what to do.
(The problem is that the variable could be a node list returned from an
extension that is out of document order, or with nodes on different levels
which would also require a sorted iterator. I ca
Hello,
I read an XML document which contains an internal DTD and with DOM I change
some nodes in this document.
Then I try to serialize the new document to a file, but it doesn't serialize
my previous DOCTYPE
Can you tell me what's wrong in this serializing Java code :
SerializerTo
morten 01/08/01 04:52:59
Modified:java/src/org/apache/xalan/xsltc/compiler Constants.java
If.java Key.java Predicate.java Step.java When.java
java/src/org/apache/xalan/xsltc/compiler/util
CompareGenerator.java
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=2945
Hi all,
How can I transform an org.w3c.dom.NodeList into an XPath node set on which
I can use XPath expressions to select nodes?
Example: I use XPathAPI.selectNodeList to get a NodeList; anter that, I
want to apply another XPath selection to it...
Christian
Make that Macs (possibly Macos 9) as well. Has Xalan-c been compiled and run on
Macos 9 and X?
At 01/08/01 08:45:41, Roger Day wrote:
# Actually, I was looking for more in-depth details than just the
usage-patterns.
# Maybe I should have added more detail. We're using xalan-c. The product will
Hi
I'm trying to rebuild the Xalan-C++ 1.1 on Solaris 2.6, bat there are
some problems. When CC includes the STLport header "stl/_deque.h",
encouters some errors like this:
--
CC -O -KPIC -mt -xs -ptr//xml-xalan/c/obj -featu
Actually, I was looking for more in-depth details than just the usage-patterns.
Maybe I should have added more detail. We're using xalan-c. The product will be
compiled across the usual suspects as well as SGI. For example, I notice that
the Xalan-c source is split across across several platforms;
69 matches
Mail list logo
