[
http://issues.apache.org/jira/browse/XALANJ-1978?page=comments#action_12319325
]
Thomas Mathis commented on XALANJ-1978:
---
Thank you, I confirm that the issue is fiexed and my programs now run correctly
(without workarounds).
> Using StreamResult w
[
http://issues.apache.org/jira/browse/XALANJ-936?page=comments#action_12319300 ]
Brian Minchau commented on XALANJ-936:
--
Shane, as the issue reporter please confirm that this is fixed to your
satisfaction in the Xalan-J 2.7 release, that was released
[
http://issues.apache.org/jira/browse/XALANJ-1368?page=comments#action_12319299
]
Brian Minchau commented on XALANJ-1368:
---
Joerg, as the issue reporter please confirm that this is fixed to your
satisfaction in the Xalan-J 2.7 release, that was relea
[
http://issues.apache.org/jira/browse/XALANJ-1431?page=comments#action_12319298
]
Brian Minchau commented on XALANJ-1431:
---
ds, as the issue reporter please confirm that this is fixed to your
satisfaction in the Xalan-J 2.7 release, that was released
[
http://issues.apache.org/jira/browse/XALANJ-1478?page=comments#action_12319297
]
Brian Minchau commented on XALANJ-1478:
---
Rich, as the issue reporter please confirm that this is fixed to your
satisfaction in the 2.7 release, then we can close this
[
http://issues.apache.org/jira/browse/XALANJ-1640?page=comments#action_12319294
]
Brian Minchau commented on XALANJ-1640:
---
Corey, as the issue reporter please confirm that this is fixed to your
satisfaction in the 2.7 release, then we can close this
[
http://issues.apache.org/jira/browse/XALANJ-1852?page=comments#action_12319293
]
Brian Minchau commented on XALANJ-1852:
---
Sergei, as the issue reporter please confirm that this is fixed to your
satisfaction in the 2.7 release, then we can close thi
[
http://issues.apache.org/jira/browse/XALANJ-1853?page=comments#action_12319291
]
Brian Minchau commented on XALANJ-1853:
---
Sergei, as the issue reporter please confirm that this is fixed to your
satisfaction in the 2.7 release, then we can close thi
[ http://issues.apache.org/jira/browse/XALANJ-1886?page=all ]
Brian Minchau closed XALANJ-1886:
-
> Multiple problems with collecting xsl:attributes with over-ridden values and
> prefix/URI maps
>
[
http://issues.apache.org/jira/browse/XALANJ-1912?page=comments#action_12319290
]
Brian Minchau commented on XALANJ-1912:
---
Micha, this fix made it into the Xalan-J 2.7 release. Please confirm that it is
fixed, then we can close this issue.
> match=
[
http://issues.apache.org/jira/browse/XALANJ-1955?page=comments#action_12319289
]
Brian Minchau commented on XALANJ-1955:
---
Elliotte,
this should be fixed in 2.7. Please confirm this so we can close the issue.
> Fail Oasis test case Keys_PerfRepro3
>
[
http://issues.apache.org/jira/browse/XALANJ-1978?page=comments#action_12319288
]
Brian Minchau commented on XALANJ-1978:
---
Thomas, this bug should be fixed in Xalan-J 2.7, that was released Aug 8, 2005.
As the issue reporter, please confirm that thi
[
http://issues.apache.org/jira/browse/XALANJ-2147?page=comments#action_12319287
]
Scott Lamb commented on XALANJ-2147:
It's definitely fixed. Thanks!
(Are you asking me to change the status to verified? Either I don't have
permissions to do that or I
[
http://issues.apache.org/jira/browse/XALANJ-1985?page=comments#action_12319286
]
Brian Minchau commented on XALANJ-1985:
---
Nick this issue is now fixed in the Xalan-J 2.7 release. As the issue reporter,
please confirm so that we can close this issue
[
http://issues.apache.org/jira/browse/XALANJ-2023?page=comments#action_12319283
]
Brian Minchau commented on XALANJ-2023:
---
Ken, as the issue reporter please confirm that this issue is fixed in the
Xalan-J 2.7 release, then we can close this issue.
[ http://issues.apache.org/jira/browse/XALANJ-2051?page=all ]
Brian Minchau closed XALANJ-2051:
-
Closing this issue.
> XML Serializer serializes some DTD information, but not all
> ---
>
>
[
http://issues.apache.org/jira/browse/XALANJ-2054?page=comments#action_12319280
]
Brian Minchau commented on XALANJ-2054:
---
Daniel, as the reporter of this issue please confirm that it is fixed to your
satisfaction in the Xalan-J 2.7 release, then we
[
http://issues.apache.org/jira/browse/XALANJ-2059?page=comments#action_12319279
]
Brian Minchau commented on XALANJ-2059:
---
Yash please confirm that this is fixed in 2.7 and close this issue.
> Transformation fails when an href attribute of xsl:inclu
[ http://issues.apache.org/jira/browse/XALANJ-2079?page=all ]
Brian Minchau closed XALANJ-2079:
-
I've verified that the current 2.7 website has the links fixed.
I'm taking the liberty of closing this issue on Henry's behalf.
> Links to GUMP build are o
[
http://issues.apache.org/jira/browse/XALANJ-2081?page=comments#action_12319277
]
Brian Minchau commented on XALANJ-2081:
---
Yash, please confirm that this is fixed in 2.7 and close this issue.
> XSLTC does ignores non-whitespaces as if they were whit
[
http://issues.apache.org/jira/browse/XALANJ-2085?page=comments#action_12319276
]
Brian Minchau commented on XALANJ-2085:
---
Yash this patch should be in 2.7, please confirm and close the issue.
> Need to update Javadoc for org.apache.xpath.domapi pac
[
http://issues.apache.org/jira/browse/XALANJ-2086?page=comments#action_12319275
]
Brian Minchau commented on XALANJ-2086:
---
Jack,
this issue is now resolved as being fixed in the Xalan-J 2.7 release. As the
issue reporter please confirm the code no l
[ http://issues.apache.org/jira/browse/XALANJ-2089?page=all ]
Brian Minchau closed XALANJ-2089:
-
Yash, I've taken the liberty of closing this issue for you. Re-open if you need
to, but I sure hope you don't do that.
> Performance degradation in ElemNu
[
http://issues.apache.org/jira/browse/XALANJ-2090?page=comments#action_12319271
]
Brian Minchau commented on XALANJ-2090:
---
Yash, as the issue reporter, please confirm that this is fixed to your
satisfaction in the 2.7 release, then we can close this
[ http://issues.apache.org/jira/browse/XALANJ-2096?page=all ]
Brian Minchau closed XALANJ-2096:
-
Closing this issue. The smoketest is not currently failing.
> Smoketest fails with xml-xalan extract from CVS.
> --
[
http://issues.apache.org/jira/browse/XALANJ-2097?page=comments#action_12319268
]
Brian Minchau commented on XALANJ-2097:
---
Nick, please confirm that this issue is resolved to your satisfaction in the
Xalan-J 2.7 release, then we can close this issue
[
http://issues.apache.org/jira/browse/XALANJ-2140?page=comments#action_12319266
]
Brian Minchau commented on XALANJ-2140:
---
arn44,
this bug is fixed and is now in the 2.7 release. You are the reporter, so
please confirm that the issue is fixed so tha
[
http://issues.apache.org/jira/browse/XALANJ-2099?page=comments#action_12319267
]
Brian Minchau commented on XALANJ-2099:
---
Morris, as the issue reporter, please confirm that this is fixed in 2.7 so we
can close this issue.
> EXSLT date:day-abbrevia
[
http://issues.apache.org/jira/browse/XALANJ-2146?page=comments#action_12319265
]
Brian Minchau commented on XALANJ-2146:
---
Henry, as the reporter of this issue, would you please close it, it is in the
2.7 release.
> Byte code generated by XSLTC con
[
http://issues.apache.org/jira/browse/XALANJ-2147?page=comments#action_12319264
]
Brian Minchau commented on XALANJ-2147:
---
Scott,
as the reporter of the issue, and since the fix is in the Xalan-J 2.7 release,
please confirm the fix so that we can cl
[
http://issues.apache.org/jira/browse/XALANJ-2154?page=comments#action_12319263
]
Brian Minchau commented on XALANJ-2154:
---
Andreas,
this fix made it into the 2.7 release of Xalan-J. Please confirm that this
problem is fixed to your satisfaction so t
[ http://issues.apache.org/jira/browse/XALANJ-2159?page=all ]
Brian Minchau closed XALANJ-2159:
-
GUMP is no longer broken because of this. Closing this issue.
> Class path and bootstrap class path are not set correctly for test harness in
> Gump build
[
http://issues.apache.org/jira/browse/XALANJ-2163?page=comments#action_12319261
]
Brian Minchau commented on XALANJ-2163:
---
Brian Vargas,
the trivial change was made and is now in the 2.7 release. Would you confirm
that the problem is fixed, then we
[
http://issues.apache.org/jira/browse/XALANJ-2175?page=comments#action_12319260
]
Brian Minchau commented on XALANJ-2175:
---
Henry, as the reporter of this issue, and since the patch is now in the 2.7
release, please close this issue.
> Support testi
[
http://issues.apache.org/jira/browse/XALANJ-2176?page=comments#action_12319259
]
Brian Minchau commented on XALANJ-2176:
---
Henry, as the reporter of this issue, and since the patch should be in the 2.7
release, please close this issue.
> Java sourc
[
http://issues.apache.org/jira/browse/XALANJ-2103?page=comments#action_12319258
]
Brian Minchau commented on XALANJ-2103:
---
Fraser,
the fix is now in the official Xalan-J 2.7 release. Please confirm that this is
fixed for you so that we can close thi
[ http://issues.apache.org/jira/browse/XALANJ-2105?page=all ]
Brian Minchau closed XALANJ-2105:
-
Closing this issue.
> XMLReaderManager.releaseXMLReader(reader) - null pointer exception
>
[
http://issues.apache.org/jira/browse/XALANJ-2110?page=comments#action_12319256
]
Brian Minchau commented on XALANJ-2110:
---
arn44, since you reported this issue Xalan-J 2.7 was released. Please verify
that your problem is fixed in that release so we
[
http://issues.apache.org/jira/browse/XALANJ-2114?page=comments#action_12319255
]
Brian Minchau commented on XALANJ-2114:
---
Dave,
not only has John Gentilin's patch for this isse been reviewed by Henry, it was
also applied (I just had a look at thos
[
http://issues.apache.org/jira/browse/XALANJ-2121?page=comments#action_12319254
]
Brian Minchau commented on XALANJ-2121:
---
Dave,
Xalan-J 2.7 was released Aug 8, 2005 and should have the fix. Please verify so
we can close this issue.
> Need correct
[
http://issues.apache.org/jira/browse/XALANJ-2128?page=comments#action_12319253
]
Brian Minchau commented on XALANJ-2128:
---
Faizan,
Xalan-J 2.7 was released on Aug 8, 2005. Please confirm that the memory leak is
fixed in the 2.7 release, and we can t
[
http://issues.apache.org/jira/browse/XALANJ-1216?page=comments#action_12319252
]
Brian Minchau commented on XALANJ-1216:
---
XALANJ-1833 was marked as a duplicate of this issue. Elliotte has indicated
that that issue is now fixed to his satisfaction,
[ http://issues.apache.org/jira/browse/XALANJ-1837?page=all ]
Brian Minchau closed XALANJ-1837:
-
Assign To: (was: Xalan Developers Mailing List)
Closing this issue.
> Fails OASIS test case select85 involving current() function
> ---
[ http://issues.apache.org/jira/browse/XALANJ-1833?page=all ]
Brian Minchau closed XALANJ-1833:
-
Assign To: (was: Xalan Developers Mailing List)
Closing this issue.
> Xalan fails axes62 test from Oasis test suite
> -
[ http://issues.apache.org/jira/browse/XALANJ-1835?page=all ]
Brian Minchau closed XALANJ-1835:
-
Assign To: (was: Xalan Developers Mailing List)
Closing this issue.
> Fails OASIS namespace test 141/ Puts an element in
> http://www.w3.org/XML/1
Here is the stack trace. It appears that Xalan is trying to load a
template from the Web Start cache, and being denied read permission.
ERROR: 'java.security.AccessControlException: access denied
(java.io.FilePermission C:\Documents and Settings\guym\Application
Data\Sun\Java\Deployment\cache
Greetings, I've having trouble debugging a peculiar issue.
I'm developing a Java Web Start application that makes extensive use of
XSLT. My XSL templates are packaged in a Jar file with the application.
I'm testing with Java 1.5.0_04, though the app should work in Java 1.4
and higher. All the
[
http://issues.apache.org/jira/browse/XALANJ-1576?page=comments#action_12319233
]
Peter Kharchenko commented on XALANJ-1576:
--
seems like a very old issue, with a patch available. any reason it's not making
the releases?
> xsl:attribute and eleme
> Thanks, I tried that (output below) but there appears to be a source
file
> missing "LocalMsgIndex.hpp"
> Is this a script generated header that somehow is not getting created
> because i'm pretending the platform is linux but it's detecting interix
> somewhwere?
First of all, please try to ref
Hi,
I'm using a DOM adapter which aims at mapping graps of java beans to XML
document. I see DTM implementations are parsing XML trees fully before
applying a stylesheet.
Problem is my objects are lazily loaded using the hibernate persistance
framework.
I've seen something talking about it in th
Thanks, I tried that (output below) but there appears to be a source file
missing "LocalMsgIndex.hpp"
Is this a script generated header that somehow is not getting created
because i'm pretending the platform is linux but it's detecting interix
somewhwere?
%gunzip Xalan-C_1_9_0-src.tar.gz
%tar xf X
Improper assert statement in FormatterToXML::accumCharUTF
-
Key: XALANC-545
URL: http://issues.apache.org/jira/browse/XALANC-545
Project: XalanC
Type: Bug
Components: XalanC
Versions: 1.7
Environmen
> Are there any instructions for building xalan-c 1.9 on interix?
> I ask because "runConfigure -h" does not list interix as a valid
platform
> value
>
> "runConfigure -h" for the pre-req i.e. xerces-c 2.6 DOES list interix as
a
> valid platform so I was wondering if xalan-c will include a way
Hi,Are
there any instructions for building xalan-c 1.9 on interix?I ask because
"runConfigure -h" does not list interix as a valid
platformvalue"runConfigure -h" for the pre-req i.e. xerces-c 2.6
DOES list interix as avalid platform so I was wondering if xalan-c
will include a way to build
Yash Talwar wrote:
Hi Elliotte,
Prior to release 2.7, xalan.jar file included the code for serializer. In
release 2.7, the serializer code is bundled in serializer.jar file. So,
when you used older versions, you included xalan.jar file in the classpath.
Xalan code make use of serializer code to
[
http://issues.apache.org/jira/browse/XALANJ-1835?page=comments#action_12319190
]
elharo commented on XALANJ-1835:
I can confirm that this issue is fixed in 2.7.
> Fails OASIS namespace test 141/ Puts an element in
> http://www.w3.org/XML/1998/namespace
[
http://issues.apache.org/jira/browse/XALANJ-1837?page=comments#action_12319189
]
elharo commented on XALANJ-1837:
I don't think I have permissions to close issues myself, but this has been
fixed for a while. Feel free to close it down.
> Fails OASIS te
[
http://issues.apache.org/jira/browse/XALANJ-1833?page=comments#action_12319188
]
elharo commented on XALANJ-1833:
It seems fixed to me. Thanks.
> Xalan fails axes62 test from Oasis test suite
> -
>
> K
Elliottee,
SERIALIZER DOES NOT DEPEND ON XALAN
===
In previous releases the code to do the serialization of the output
result tree was in the same jar as the code to do the XSL transformation,
in xalan.jar. That code was pulled out of xalan.jar and put into
serializ
Hi Elliotte,
Prior to release 2.7, xalan.jar file included the code for serializer. In
release 2.7, the serializer code is bundled in serializer.jar file. So,
when you used older versions, you included xalan.jar file in the classpath.
Xalan code make use of serializer code to output the result tr
Failure to throw exception when encountering stylesheet with unmapped extension
function
Key: XALANJ-2190
URL: http://issues.apache.org/jira/browse/XALANJ-2190
Project: XalanJ2
For what it's worth here's the relevant part of the stack trace:
java.lang.NoClassDefFoundError: org/apache/xml/serializer/SerializerTrace
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
java.security.Secu
I replaced my old 2.6.2 xalan.jar with the new 2.7.0 xalan.jar and
everything promptly broke. The reason is that I didn't have
serializer.jar in my classpath. Easy enough to fix, but the next
question is why I need this? i.e. what depends on serializer.jar, and
why should anything so depend? I
I noticed that Xalan 2.7 is now advertised as requiring Java 1.3 or
later. I'm not sure when this changed. What prevents Xalan from running
with 1.2, or is it just that it has not been tested with 1.2?
--
Elliotte Rusty Harold [EMAIL PROTECTED]
XML in a Nutshell 3rd Edition Just Published!
ht
64 matches
Mail list logo
