VinyJones created XALANJ-2559:
-
Summary: XLST XPath condition on preceding-sibling returns more
results that if there is any condition
Key: XALANJ-2559
URL: https://issues.apache.org/jira/browse/XALANJ-2559
shath...@e-z.net wrote:
> Gareth,
>
> Thanks for the link. Our first priority is to get additional functionality
> with XPath 1.0 and EXSLT functions.
>
> I am interested in pursuing the XPath2 integration after our XalanC 1.11
> product is released at the end of summer. I s
Gareth,
Thanks for the link. Our first priority is to get additional functionality
with XPath 1.0 and EXSLT functions.
I am interested in pursuing the XPath2 integration after our XalanC 1.11
product is released at the end of summer. I see this XPath2 integration
to become XalanC 2.0
6, Steve Hathaway wrote:
>
> Samuel - GSOC 2012
>
> You're doing good.
>
> It looks like you understand the basics of the XPath function class that
> needs to be extended
> and customizing the appropriate execute() methods.
>
> Here are some comments:: Ref: fi
which could still
be there / be of use.
Cheers,
G
On 30 Jul 2012, at 03:06, Steve Hathaway wrote:
> Samuel - GSOC 2012
>
> You're doing good.
>
> It looks like you understand the basics of the XPath function class that
> needs to be extended
> and customizing the app
Samuel - GSOC 2012
You're doing good.
It looks like you understand the basics of the XPath function class that
needs to be extended
and customizing the appropriate execute() methods.
Here are some comments:: Ref: file OspXpathConvertDate.cpp from zip example.
YourXPathFunction::ex
Error Handling in XPath Functions - brief architecture description
The Xalan/XPath standard library error messages for "en_US" are
found in file:
(src)/xalanc/NLS/en_US/XalanMsg_en_US.xlf
The messages in xliff format use 0-3 parameter substitutions.
The xlif file is proces
I think we've all learned some valuable lessons from that
experience.
Thanks.
Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrgla...@ca.ibm.com
E-mail: mrgla...@apache.org
Steve Hathaway wrote on 03/25/2012 04:33:12 PM:
> FYI: Java XPath-2
>
> I
FYI: Java XPath-2
I just did a brief difference analysis of last year's GSoC 2011
code for xalan2 and the current Apache Xalan Java trunk.
Here are the significant changes found in the Google GSoC repository:
1. A refactoring of security, almost identical to what we have.
2. Adding
[
https://issues.apache.org/jira/browse/XALANJ-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gareth reakes closed XALANJ-2549.
-
Resolution: Not A Problem
Query rather than bug
> XPath with default namesp
an-j/xpath_apis.html#namespacecontext
For more information. If its still not clear then ask the list.
Gareth
> XPath with default namespace - No result
>
>
> Key: XALANJ-2549
> URL: https://issues.apa
ort']/account_number");
Removing the *xmlns attribute* from the report tag allows me to find the
correct result but is not my use case.
Adding a prefix to the namespace and using it also allows me to find the
correct result but is not my use case either.
XPath with default namespace - No result
Key: XALANJ-2549
URL: https://issues.apache.org/jira/browse/XALANJ-2549
Project: XalanJ2
Issue Type: Bug
Security Level: No security risk; visible to
ution.
> Wrong XPath evaluation with queries starting with ".//" when wrapping a
> Xerces Document
> ---
>
> Key: XALANC-596
> URL: https://issues.
Bertrand Delacretaz wrote on 07/06/2011 05:17:52
AM:
> Hi,
>
> 2011/6/29 Xun Long Gui :
> > ...I talked with Victor about how to merge his job with Xalan's
> code base, it
> > seems that Vict's project add XSLT 2.0 support for Xalan by merging
> > PsychoPath, not build a brand new version of Xal
Hi,
2011/6/29 Xun Long Gui :
> ...I talked with Victor about how to merge his job with Xalan's code base, it
> seems that Vict's project add XSLT 2.0 support for Xalan by merging
> PsychoPath, not build a brand new version of Xalan base on its code base. So
> i think it is a little strange to rele
If you want to collaborate on the PsychoPath/XSLT 2.0 project, I'm
willing to host the code on the Bilrost github site. This would at least
give it a place to reside publicly until it can be determined where it
will eventually reside.
https://github.com/organizations/bilrost
Please let me know if
Hi there,
I talked with Victor about how to merge his job with Xalan's code base, it
seems that Vict's project add XSLT 2.0 support for Xalan by merging
PsychoPath, not build a brand new version of Xalan base on its code base. So
i think it is a little strange to release his project as a new Xalan
Hi Victor,
On Fri, Jun 24, 2011 at 5:56 AM, Victor Wang
wrote:
>... Yeah, I am working for merging PsychoPath with Xalan to get XSLT 2.0
> features, but I have just started this job for more than one month and have
> not finished a steady version yet, so i do not think it is a good idea to
> merg
Hi Bert,
Yeah, I am working for merging PsychoPath with Xalan to get XSLT 2.0
features, but I have just started this job for more than one month and have
not finished a steady version yet, so i do not think it is a good idea to
merge my *experiment* code with Xalan code base currently. In GSoC sch
>From the desk of Steven J. Hathaway: (some markup removed for posting...)
I hope these notes provide useful insight into the XPath extended function
programming in the Apache Xalan-C/C++ version 1.11.
This document provides some of my working notes when building libraries of
XPath exten
Should we consider releasing a 2.7.2 or 2.8 just to warm up the development
and release process again?
Are there some simple changes we could put in (for example
https://issues.apache.org/jira/browse/XALANJ-2423) for a new release?
Gary
On Wed, Jun 22, 2011 at 12:14 PM, Bertrand Delacretaz <
bde
Hi Victor,
On Wed, Jun 15, 2011 at 6:15 AM, Victor Wang
wrote:
> ...Yeah, we are working for implement some XSLT 2.0 features for Xalan, as
> this
> project is really a huge project, i need help from Xalan community, i am
> looking forward to do something for Xalan community. thank you
Do you h
I will try to review this project and find to solution to work together to
get a new Xalan release version ASAP
在 2011年6月16日 上午6:19，David Carver 写道：
> I'd be interested in helping you guys out. I already have a future fork
> of Xalan code in GitHub.
>
> https://github.com/kingargyle/bilrost
>
>
Thanks Dave!
I remember seeing your postings some time back.
I'd like to review what you have done.
Some of my recent postings on Apache JIRA for the XML XALANC
project still need to be committed.
I'll be glad to get you the Doxygen configuration for the current
versions of Doxygen and GraphViz p
I'd be interested in helping you guys out. I already have a future fork
of Xalan code in GitHub.
https://github.com/kingargyle/bilrost
I've got a branch where I've mavenized the build, which makes it a bit
simplier to get started. Not much work has happened. I'm also one of the
committers for the
Dear Bertrand,
Yeah, we are working for implement some XSLT 2.0 features for Xalan, as this
project is really a huge project, i need help from Xalan community, i am
looking forward to do something for Xalan community. thank you
2011/6/14 Bertrand Delacretaz
> Hi Xun Long Gui ,
>
> It seems lik
Hi Bert,
Due to low activity in Xalan community (In fact, we discussed the project in
Xalan-dev mail list before, but it seems that not much developers are
interested in it ), i discuss this project with the student directly, and
plan to host this project in Google Code web site ( As I can not acc
Hi Xun Long Gui ,
It seems like you are the mentor for this GSoC project about Xalan:
http://www.google-melange.com/gsoc/project/google/gsoc2011/aguai/9003
I haven't seen this discussed on the Xalan dev list, are your
discussions about this happening on another Apache list?
The Xalan project is
his topic was discussed in mail list for
>> many many times in recent years, so many guys are expecting it come true.
>> But due to low activity in Apache Xalan community, no committer to push this
>> thing, it is really very regretful.
>>
>> These days, i submited "
topic was discussed in mail list for
> many many times in recent years, so many guys are expecting it come true.
> But due to low activity in Apache Xalan community, no committer to push this
> thing, it is really very regretful.
>
> These days, i submited "Implement XSLT 2.0
mmitter to push this
> thing, it is really very regretful.
>
> These days, i submited "Implement XSLT 2.0 and XPath 2.0 for Xalan" project
> proposal as an GSoC[1] project. Now, i need your feedbacks to improve the
> proposal, all the advises, suggestions are welcom
push this
thing, it is really very regretful.
These days, i submited "Implement XSLT 2.0 and XPath 2.0 for Xalan" project
proposal as an GSoC[1] project. Now, i need your feedbacks to improve the
proposal, all the advises, suggestions are welcome :-)
I am not a Xalan committer(alrough i d
eems fine. I will send an email to the PMC
members to see if there are any objections to accepting it.
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
> Key: XALANJ-2438
>
bug, and that a similar fix would be in
order. In fact, the indication from the original reporter that a similar bug
exists in the Oracle implementation makes it rather unlikely that Helge --
intentionally or inadvertently -- copied GPL licensed code into this patch.
> [PATCH] XSLTC ignores
You may be interested in the Test Suite for XSLT 1.0 and XPath 1.0
provided by OASIS.
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xslt
I know for XPath 2.x, XSLT 2.x, and XQuery 1.x the W3C has created a
very large test suite for use by implementers.
Dave
On 06/24/2010 03
On 6/22/2010 6:49 AM, kesh...@us.ibm.com wrote:
It's been too many years since I've looked at this code... I found the
XSLT tests, but haven't found XPath API tests yet, outside of the most
basic sorts of formulas. Do they exist, and if so how does one launch them?
Hi Joe,
It's been too many years since I've looked at this code... I found the
XSLT tests, but haven't found XPath API tests yet, outside of the most
basic sorts of formulas. Do they exist, and if so how does one launch
them?
__
"... Three thing
might
> implement the ItemPSVI interface of the Xerces XML Schema API?
and you reponded:
David Carver wrote on 04/11/2010 09:48:22 AM:
> For XML Schema Awarness which PsychoPath supports, it requires
> Xerces-J. For all other DOM's that are given to it, it defaults to
&
ce of the Xerces XML Schema API?
and you reponded:
David Carver wrote on 04/11/2010 09:48:22 AM:
> For XML Schema Awarness which PsychoPath supports, it requires
> Xerces-J. For all other DOM's that are given to it, it defaults to
> just the XPath core functionality. It currently re
plementing XSLT 2.0 for Xalan, then, i
> discovered that merge with Xalan with PsychoPath will speed up this project.
> You said "The Xerces-J 2.10 upcoming release using PsychoPath as one of it's
> XPath 2.0 engines" , it seems that implement XSLT 2.0 for Xalan is in plan
&
e Xerces-J 2.10 upcoming release using PsychoPath
as one of it's XPath 2.0 engines" , it seems that implement XSLT 2.0
for Xalan is in plan now, good to hear that, so many guys are eager to
see that come true,I am eager to do something for this huge
project. In fact, i hold "imp
might
implement the ItemPSVI interface of the Xerces XML Schema API?
For XML Schema Awarness which PsychoPath supports, it requires
Xerces-J. For all other DOM's that are given to it, it defaults to just
the XPath core functionality. It currently requires a DOM Level 3
implementation,
If there is not functionality you need, then I would HIGHLY recommend
contributing patches back to the psychopath project. The Xerces-J 2.10
upcoming release using PsychoPath as one of it's XPath 2.0 engines, so
it can be intergrated with out having to fork the code necessarily.
If you
Hi Henry,
These days, i was looking at PsychoPath document and source code and studing
it, apparently, PsychoPath does not support enough user interface for Xalan to
get all the necessary things such as get XPath syntax tree. But merging Xalan
and PsychoPath and use PsychoPath as our
Hi, Jesper.
Jesper Møller wrote on 04/01/2010 06:24:49 PM:
> I'm one of the committers on PsychoPath XPath 2 engine and would
> like to offer my input where I can help if this is a viable way.
>
> First off, I must confess that while I know XSLT pretty well, I've
&g
Hi Jesper,
Welcome here first!
As you said, one day if PsychoPath supplies a decent API which can satisfy
the requirement of both Xalan and Xerces, it will be very easy for Xalan to
consume PsychoPath.
But as you know, Xalan is known as a XSLT engine, support XSLT 2.0 is very
important,necessary
erator and Schema interfaces aren't rich enough
> for the type information we need in XPath 2 (and thus XSLT 2).
Xalan currently runs on the DTM interfaces and data model. Those could
certainly be extended to carry schema information. Work would also have to
be done to replace the nodeset r
Hi Xalan-dev list
I'm one of the committers on PsychoPath XPath 2 engine and would like to offer
my input where I can help if this is a viable way.
First off, I must confess that while I know XSLT pretty well, I've not studied
Xalan-J in depth. However, from looking over the desig
Hi
Yeah, i have checked out PsychoPath source code,i think it is a good idea to
merge PsychoPath with Xalan, it will support nearly all the XPath 2.0
implemention for Xalan. After that, my task is to implement the other XSLT 2.0
specification for Xalan,this solution really speed this project
You guys may be able to speed some of this up by leveraging the
PsychoPath XPath 2.0 processor that is at Eclipse.
It is already being used by Xerces-J for XSD 1.1 Assertion support. Why
re-invent the wheel if you can leverage something that already exists.
http://wiki.eclipse.org
Hi Michael,
Starting with utility parts is regular way to implement a new recommendation
specification. But i think, functions is a very practical part. If i finish it
first,may be some guys can go it into service. Months ago,i was working with a
XSLT project based on Xalan, i need some XPath
rsion 1.0. I will
implement the ones XSLT 2.0 defined but Xalan not support yet.
2.change Xalan-J data structrue to track XSLT 2.0 Schema types
So far, I know it clear about how to add a new XPath function for Xalan, and
have finished some functions, so this part may be i can handler it well.But
was coding with Xalan, i want
> to finish some XPath 2.0 functions which do not use sequences and
> schema-type first,because these functions are very practical and
> compatible with XPath 1.0. In fact, i have finish some functions and
> test them to confirm them works well (for examp
n understand why Henry feels this would need to be assessed /
committed by a Sun or Oracle employee since they own the copyright on any
modifications / additions that have been made since forking from the ASF
codebase.
Thanks.
[1] http://www.apache.org/legal/3party.html
[2] http://mail-archive
e.
Thanks.
[1] http://www.apache.org/legal/3party.html
[2] http://mail-archives.apache.org/mod_mbox/www-legal-discuss/
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
> Key: XALANJ-2438
>
have
then been the correct way to contribute a patch to Xalan-J and JDK (over JAXP,
which is the only source for XML updates) simultaneously?
Did you or any Apache member receive a request from Oracle/Sun to remove the
discussed files?
Regards, Helge
--
Helge Schulz - http://OpenSHORE.org
> [
I
believe you also have test case code in those jar files, and I can't make the
judgment myself about what should remain and what should be removed.
Thanks again for you understanding,
Henry
> [PATCH] XSLTC ignores XPat
code.
Thanks for your understanding,
Henry
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
> Key: XALANJ-2438
> URL: https://issues.apache.org/jira/browse/XALANJ-243
tate 'RESOLVED' with resolution
'FIXED':
<http://jaxp.dev.java.net/issues/show_bug.cgi?id=60>
I hope my patch will go sometime also in the Apache Xalan-J version.
--
Helge Schulz - http://OpenSHORE.org
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
--
Helge Schulz - http://OpenSHORE.org
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
> Key: XALANJ-2438
> URL: https://issues.apache.org/jira/browse/XALANJ-2438
>
RE.org
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
> Key: XALANJ-2438
> URL: https://issues.apache.org/jira/browse/XALANJ-2438
> Project: XalanJ2
>
.do?bug_id=6689809>
>
> or submit this bug as an official support request to Sun, if your
> organization has a support contract with Sun. Thank you!
>
> --
> Helge Schulz - http://OpenSHORE.org
>
>> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
>>
9 PM:
Hello Xalan committer,
I have uploaded a new version of my patch, which avoids the infinite recursion
in certain XPath expressions discovered by Henry Zongaro. I tested this new
version with all XSL files from the sections 'accept', 'conf' and 'contrib'
8 PM:
Hello Xalan committer,
I have uploaded a new version of my patch, which avoids the infinite recursion
in certain XPath expressions discovered by Henry Zongaro. I tested this new
version with all XSL files from the sections 'accept', 'conf' and 'contrib'
lge Schulz - http://OpenSHORE.org
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
> Key: XALANJ-2438
> URL: https://issues.apache.org/jira/browse/XALANJ-2438
> Proje
ed a new version of my patch, which avoids the infinite recursion
in certain XPath expressions discovered by . I tested this new version with all
XSL files from the sections 'accept', 'conf' and 'contrib' from the Xalan test
archive (see http://svn.apache.org/repo
.
--
Helge Schulz - http://OpenSHORE.org
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
> Key: XALANJ-2438
> URL: https://issues.apache.org/jira/browse/XALANJ-2
g at your patch. I didn't see an obvious
problem, but when I tried applying it and running the conformance tests, I got
a StackOverflowError while processing test case axes13. So it looks like
you've introduced an infinite recursion with the patch.
> [PATCH] XSLTC ignores XPath pred
n-J.
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
> Key: XALANJ-2438
> URL: https://issues.apache.org/jira/browse/XALANJ-2438
> Project: XalanJ2
> Is
and commit my patch?
Is there still an active commiter in this project?
--
Helge Schulz - http://OpenSHORE.org
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
> Key: XALANJ-2438
>
Hi,
I've created a few classes using and mainly inspired by Xalan's XPath
implementation, adding a new functionality to the low-level XPath API,
which I think might be of some interest for the community. Thus I would
be happy to share the code if
- Given the description belo
case that demonstrates what you described?
Thanks,
Henry
> Xpath support in Xalan does not work if default namespace is used
> -
>
> Key: XALANJ-2469
> URL: https://issues.apache.org/jira
used xpath expression as "/abc:Invoice" and defined the prefix abc as
abc="http://edi.carquest.com/2007/types/transnet";. The xml is same with default
namespace as xmlns="http://edi.carquest.com/2007/types/transnet"; in the
root-tag. But this also did not help.
We
d to include a crucial reference to section
5.1 of XPath.[4] That section states, "An element node has an expanded-name
computed by expanding the QName of the element specified in the tag in
accordance with the XML Namespaces Recommendation [XML Names]." It's the XML
Namespaces
2.3 of the XPath recommendation[2] says, "A node test that is a QName
is true if and only if the type of the node (see "5 Data Model") is the
principal node type and has an expanded-name equal to the expanded-name
specified by the QName." Just above that appears the text you&
[
https://issues.apache.org/jira/browse/XALANJ-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652455#action_12652455
]
rohit singh commented on XALANJ-2469:
-
sorry for typo. I meant "This xpath e
as that a typo? Did you mean to say that it "does not
return the specified element," or did you really mean that it "does return the
specified elements," but you expected it to return an empty node set?
An empty node set should be the result in this case, as a NameTest in an X
s is XSLT4J Java 2.7.4
> Xpath support in Xalan does not work if default namespace is used
> -
>
> Key: XALANJ-2469
> URL: https://issues.apache.org/jira/browse/XALANJ-2469
>
Xpath support in Xalan does not work if default namespace is used
-
Key: XALANJ-2469
URL: https://issues.apache.org/jira/browse/XALANJ-2469
Project: XalanJ2
Issue Type: Bug
[
https://issues.apache.org/jira/browse/XALANC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bertoni closed XALANC-684.
Fix confirmed.
> XPath single quote-comma bug
>
>
>
[
https://issues.apache.org/jira/browse/XALANC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bertoni resolved XALANC-684.
--
Resolution: Fixed
Fix Version/s: CurrentCVS
Patch applied.
> XPath single quote-co
27;Project
Only->Build only AllInOne''
If no errors occurred you will now have the following files:
* Xalan-C_1.lib
* Xalan-C_1_11.dll
* XalanMessages_1_11.dll
* XalanMessages_1_11.lib
== Applying a patch using TortoiseSVN ==
# Download the patch from [https://issues.apache.org/jira/
as a command to apply the patch
automatically. You can get it from here:
http://tortoisesvn.tigris.org/
Tortoise SVN integrates into Windows Explorer, so it should be very easy for
you to get up to speed.
> XPath single quote-comma bug
>
>
>
[
https://issues.apache.org/jira/browse/XALANC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bertoni reassigned XALANC-684:
Assignee: David Bertoni
> XPath single quote-comma
XPath single quote-comma bug
Key: XALANC-684
URL: https://issues.apache.org/jira/browse/XALANC-684
Project: XalanC
Issue Type: Bug
Components: XalanC
Affects Versions: 1.10
Environment
XPath ignores namespace declarations except on root element
---
Key: XALANJ-2456
URL: https://issues.apache.org/jira/browse/XALANJ-2456
Project: XalanJ2
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/XALANJ-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romeu Flores closed XALANJ-2455.
Resolution: Invalid
sorry. I misused jira
> CLONE -XPath ignores namespace declarations exc
[
https://issues.apache.org/jira/browse/XALANJ-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romeu Flores closed XALANJ-2455.
Resolution: Invalid
sorry. I misused jira
> CLONE -XPath ignores namespace declarations exc
CLONE -XPath ignores namespace declarations except on root element
--
Key: XALANJ-2455
URL: https://issues.apache.org/jira/browse/XALANJ-2455
Project: XalanJ2
Issue Type: Bug
CLONE -XPath ignores namespace declarations except on root element
--
Key: XALANJ-2455
URL: https://issues.apache.org/jira/browse/XALANJ-2455
Project: XalanJ2
Issue Type: Bug
ong evaluation of abbreviated XPath in template match
>
>
> Key: XALANC-679
> URL: https://issues.apache.org/jira/browse/XALANC-679
> Project: XalanC
> Issue Type: Bug
[
https://issues.apache.org/jira/browse/XALANC-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bertoni reassigned XALANC-679:
Assignee: David Bertoni
> Possible wrong evaluation of abbreviated XPath in template ma
Possible wrong evaluation of abbreviated XPath in template match
Key: XALANC-679
URL: https://issues.apache.org/jira/browse/XALANC-679
Project: XalanC
Issue Type: Bug
ision 337966 needed in XalanJ 2.4.1
> (http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_0/src/org/apache/xpath/objects/XRTreeFra
could try applying the patch and rebuilding it yourself.
I hope that helps.
[1] http://xml.apache.org/xalan-j/downloads.html#previous-releases
> Revision 337966 needed in XalanJ 2.4.1
> (http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_0/src/org/apache/xpath/objects/XRTreeFra
code for Xalan-J 2.4.1.
Kristof
> Revision 337966 needed in XalanJ 2.4.1
> (http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_0/src/org/apache/xpath/objects/XRTreeFra
The patch on Xalan 2.7 is not compatible with
2.4.1." Can you elaborate on what problem you encounter in trying to apply the
patch to the source code for Xalan-J 2.4.1?
> Revision 337966 needed in XalanJ 2.4.1
> (http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_0/src/org/
lease 2.4.1 of Xalan ?
below the bug reference that have been fixed in release 2.7
http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_0/src/org/apache/xpath/objects/XRTreeFrag.java?view=log
http://svn.apache.org/viewvc?view=rev&revision=337966
Cheers,
Anis
> Revision 337966 n
Revision 337966 needed in XalanJ 2.4.1
(http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_0/src/org/apache/xpath/objects/XRTreeFrag.java?view=log
1 - 100 of 1504 matches
Mail list logo
