To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project xsltc has an issue affecting its community integration.
This issue
mrgla...@apache.org
Sam Ruby wrote on 08/20/2011 03:18:51 AM:
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.org/nagged.html,
> and/or contact the folk at gene...@gump.apache.org.
>
>
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project xsltc has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project xsltc has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project xsltc has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project xsltc has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project xsltc has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project xsltc has an issue affecting its community integration.
This issue
xsl:key does not work with XSLTC when a global variable is defined with
document()
--
Key: XALANJ-2534
URL: https://issues.apache.org/jira/browse/XALANJ-2534
Project
Wrong transformation results using XSLTC
Key: XALANJ-2531
URL: https://issues.apache.org/jira/browse/XALANJ-2531
Project: XalanJ2
Issue Type: Bug
Security Level: No security risk; visible to
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
be going through none of the classes
modified by the patch.
> [PATCH] XSLTC resource leak causes 'No more DTM IDs are available' error
>
>
> Key: XALANJ-2439
> URL:
lts on current stylesheet and the improved ones (Xalan-J 2.7.1, JDK
1.6.0_17_x64, Win7_x64):
--
Checking with initial stylesheet.
[XSLT] Average time (per transformation) for 20 transformations: 21.9 ms.
[XSLTC] Average time (per transformation) for 20 transformations: 10222.85 ms.
Checking
Checking with initial stylesheet.
[XSLT] Average time (per transformation) for 20 transformations: 21.9 ms.
[XSLTC] Average time (per transformation) for 20 transformations: 10222.85 ms.
Checking with improved stylesheet.
[XSLT] Average time (per transformation) for 20 transformations: 9.2 ms.
[
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
>
to resolve all doubts.
Regards, Helge
--
Helge Schulz - http://OpenSHORE.org
> [PATCH] XSLTC resource leak causes 'No more DTM IDs are available' error
>
>
> Key: XALANJ-2439
>
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
> [
or Oracle who
has signed an Apache CLA can contribute such code.
Thanks for your understanding,
Henry
> [PATCH] XSLTC resource leak causes 'No more DTM IDs are available' error
>
>
>
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
h to the JAXP/JDK version of Xalan-J
and verified that the new patch passed
all JAXP regression tests. See:
<http://jaxp-sources.dev.java.net/source/browse/jaxp-sources/xml-xalan/java/src/com/sun/org/apache/xalan/internal/xsltc/compiler/FilterExpr.java?view=markup>
<http://jaxp-sources
--
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
>
rees.
Helge Schulz - http://OpenSHORE.org
> [PATCH] XSLTC resource leak causes 'No more DTM IDs are available' error
>
>
> Key: XALANJ-2439
> URL: https://issues.apa
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
>>
sting file 'accept/collation/collation02.xsl'
...
[echo] Testing file 'contrib/xsltc/schemasoft/selectHREF.xsl'
[echo] Testing file 'contrib/xsltc/schemasoft/suppressEmptyElements.xsl'
[echo] Compare output files of latest and fixed Xalan version
[concat]
ho] Testing file 'accept/collation/collation02.xsl'
...
[echo] Testing file 'contrib/xsltc/schemasoft/selectHREF.xsl'
[echo] Testing file 'contrib/xsltc/schemasoft/suppressEmptyElements.xsl'
[echo] Compare output files of latest and fixed Xalan version
[co
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
s/asf/xalan/test/trunk/tests/) and
compare the output files against them of a run of an unpatched version:
run-conformance-test:
test-xslt-all:
[echo] Testing file 'accept/collation/collation01.xsl'
[echo] Testing file 'accept/collation/collation02.xsl'
...
[echo]
.
--
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
>
-2493.
> set:distinct() over attribute list breaks XSLTC throwing HIERARCHY_REQUEST_ERR
> --
>
> Key: XALANJ-2424
> URL: https://issues.apache.org/jira/bro
I'm a bit surprised that it
should be possible to deal with this issue in the kind of patch you wrote,
though, as opposed to a complete redesign. Haven't had a deeper look yet, and
I'm not an official developer in any case, only collecting patches for my own
uses, but it sounds too
e :
java -cp xsltc.jar org.apache.xalan.xsltc.cmdline.Compile xsltcbug.xsl
java -cp xsltc.jar:. org.apache.xalan.xsltc.cmdline.Transform xsltcbug.xml
xsltcbug
If I try with current svn version, I got this :
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/xalan/xslt
simple stylesheet runs fine with Xalan but gives runtime error with XSLTC:
Incompatible type for getting or setting field
-
Key: XALANJ-2478
LT's document method
<http://www.exslt.org/exsl/elements/document/index.html>. This allows all
output parameters to be explicitly set for the secondary files.
> Wrong encoding with redirect:write in xsltc
> ---
>
>
LT's document method
<http://www.exslt.org/exsl/elements/document/index.html>. This allows all
output parameters to be explicitly set for the secondary files.
> Wrong encoding with redirect:write in xsltc
> ---
>
>
Xsltc compiler has dubious looking stuttering code
--
Key: XALANJ-2472
URL: https://issues.apache.org/jira/browse/XALANJ-2472
Project: XalanJ2
Issue Type: Task
Security Level: No
function-available in XSLTC says that Xalan extensions are available when they
aren't
-
Key: XALANJ-2465
URL: https://issues.apache.org/jira/browse/XALANJ
XSLTC rejects stylesheet that uses unavailable extension function even if
extension function is never called
Key: XALANJ-2464
URL: https
XSLTC transformation 200 times slower than pure Xalan
-
Key: XALANJ-2459
URL: https://issues.apache.org/jira/browse/XALANJ-2459
Project: XalanJ2
Issue Type: Bug
Security Level: No
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xsltc has an issue affecting its community integration.
This issue affects 1
repository.
> Missing prefix for literal result element with XSLTC if namespace was
> associated with a different prefix in another part of the styl
xes is cumulative across stylesheet modules
> with XSLTC
>
>
> Key: XALANJ-2447
> URL: https://issues.apache.org/jira/browse/XALANJ-2447
> Project: Xal
rote:
>
> Hi Helge.
>
> I'm afraid you can't assign someone to review. However I will have a look
> at your patch.
Any progress in reviewing my patch?
--
Helge Schulz - http://OpenSHORE.org
> [PATCH] XSLTC ignores XPat
04/08/2008 02:09
AMSubject
[jira] Commented: (XALANJ-2438)
[PATCH] XSLTC ignores XPath
and apply this patch?
How can I assign this issue to a reviewer or committer?
Brian Minchau and other PMC members did not respond to mail requests for help.
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
>
alan 2.7.1.
Why don't you fix such grave bugs?
> XSLTC Causes NoSuchFieldError if global variable is unused
> --
>
> Key: XALANJ-2325
> URL: https://issues.apache.org/jira/browse/XALANJ-23
alan/xsltc/dom/SAXImpl.java
===
--- org/apache/xalan/xsltc/dom/SAXImpl.java (revision 640381)
+++ org/apache/xalan/xsltc/dom/SAXImpl.java (working copy)
@@ -1836,6 +1836,11 @@
init
[PATCH] XSLTC resource leak causes 'No more DTM IDs are available' error
Key: XALANJ-2439
URL: https://issues.apache.org/jira/browse/XALANJ-2439
Project: XalanJ2
ifies what I'm advocating. I expect that the code will pass
some of those cases, but apparently not all.
> [PATCH] XSLTC ignores XPath predicates in xsl:key elements
> --
>
> Key: XALANJ-2438
>
iles, input files and expected output
files for every keying situation?
All: Is the splitting of my test case a precondition for the evaluation or
acceptance of my patch?
> [PATCH] XSLTC ignores XPath predicates in xsl:key e
ding isolation of any dependency on generate-id()
taking the first member if its argument is a multi-node set. Nested predicates
should be tested separately, after testing simple predicates.
I'm not saying Helge has to do this, but someone should split the test case.
> [PATCH] XSLTC i
[PATCH] XSLTC ignores XPath predicates in xsl:key elements
--
Key: XALANJ-2438
URL: https://issues.apache.org/jira/browse/XALANJ-2438
Project: XalanJ2
Issue Type: Bug
al poster but can confirm that this is really fixed.
Sorry for missing the deadline by 2 days :)
> XSLTC compiltation error : Branch target offset too large for short
> ---
>
> Key: XALANJ-1324
>
Hope, it helps.
>
> Christine Li
> XML Transformation
> IBM Toronto Lab
> Tel: (905)413-2601
> Email: [EMAIL PROTECTED]
>
>
> *"Stefan Keller" <[EMAIL PROTECTED]>*
>
> 10/02/2008 03:52 PM Please respond to
> xalan-dev@xml.apache.org
>
>
tefan Keller" <[EMAIL PROTECTED]>
10/02/2008 03:52 PM
Please respond to
xalan-dev@xml.apache.org
To
xalan-dev@xml.apache.org
cc
Subject
XSLTC with TransformerFactoryConfigurationError
Hi, just another boring classpath error... I just like to speed up my XSLT
and followed clos
osm_example.gml
-xsltc -xt -xj osm2gml.jar -n
javax.xml.transform.TransformerFactoryConfigurationError:
Provider org.apache.xalan.xsltc.trax.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(
TransformerFactory.java:108)
at
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xsltc has an issue affecting its community integration.
This issue affects 1
istinct() over attribute list breaks XSLTC throwing HIERARCHY_REQUEST_ERR
> --
>
> Key: XALANJ-2424
> URL: https://issues.apache.org/jira/browse/XALANJ-2424
>
for ELEMENT_NODE, thus, no cigar.
I'm still contemplating that fact, to be fair.
> set:distinct() over attribute list breaks XSLTC throwing HIERARCHY_REQUEST_ERR
> --
>
> Key: XALANJ-2424
>
t:distinct() over attribute list breaks XSLTC throwing HIERARCHY_REQUEST_ERR
> --
>
> Key: XALANJ-2424
> URL: https://issues.apache.org/jira/browse/XALANJ-2424
>
set:distinct() over attribute list breaks XSLTC throwing HIERARCHY_REQUEST_ERR
--
Key: XALANJ-2424
URL: https://issues.apache.org/jira/browse/XALANJ-2424
Project: XalanJ2
nder Bugzilla bug 38787.[1] Xalan-J
needs to refresh the version of BCEL it includes.
[1] http://issues.apache.org/bugzilla/show_bug.cgi?id=38787
> "Instruction unknown" Exception thrown using XSLTC
"Instruction unknown" Exception thrown using XSLTC in Turkish locale
Key: XALANJ-2420
URL: https://issues.apache.org/jira/browse/XALANJ-2420
Project: XalanJ2
[
https://issues.apache.org/jira/browse/XALANJ-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alfred Nathaniel closed XALANJ-2317.
Yes, thanks, problem is fixed in 2.7.1.
> Command line XSLTC 2.7.0 swallows er
and xsl:preserve-space do not match elements in
> a namespace with XSLTC
> ---
>
> Key: XALANJ-2230
> URL: https://issues.apache.org/jira/browse/XALANJ-2230
>
[
https://issues.apache.org/jira/browse/XALANJ-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Zongaro closed XALANJ-2377.
-
Verified this is fixed in Xalan-J 2.7.1.
> VerifyError loading translet compiled with XSLTC f
key function in a top-level variable
> with XSLTC
> -
>
> Key: XALANJ-2384
> URL: https://issues.apache.org/jira/browse/XALANJ-2384
> Project: XalanJ2
[
https://issues.apache.org/jira/browse/XALANJ-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Zongaro closed XALANJ-2339.
-
Closing issue now that Daniel has verified that it's fixed.
> XSLTC: name()-function doe
t, I'll do that on
your behalf.
> XSLTC: name()-function doesnt work properly with test-statement before
> --
>
> Key: XALANJ-2339
> URL: https://issues.apache.org/jira/browse/XAL
this bugtracking system. Can i set a state like "verified" or
is this comment enough?
> XSLTC: name()-function doesnt work properly with test-statement before
> --
>
> Key: XALANJ-2339
&
JRE you are
using) so getting it used may require work with your classpath or endorsed
directory, of course this may be true of Xalan-J in general).
2) All transformations will use your handler, not just the particular
stylesheet of interest.
I think the above should work, even for XSLTC. A
. Could
you include that too? I can't use XSLTC because it doesn't support that
extension.
> XSLTC does not support all extension xsl:output attributes
> --
>
> Key: XALANJ-2137
>
[
https://issues.apache.org/jira/browse/XALANJ-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Minchau closed XALANJ-1761.
-
closing this issue.
> XSLTC does not merge xsl:output attributes prope
relevant for 2.7.1, it is fixed in 2.7.1.
Changing the affected version to 2.7.
> XSLTC uses DocumentBuilderFactory bootstrap too often
> -
>
> Key: XALANJ-1878
> URL: https://issues.apache.org/jira/bro
[
https://issues.apache.org/jira/browse/XALANJ-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538121
]
Christine Li commented on XALANJ-2411:
--
The patch looks good to me.
> XSLTC creates namespace nodes when
d,
but rather that the default namespace is changed on this element.
Template 'makeElement3' makes sure that a new prefix is not generated,
and that the default namespace is changed. There is no possible re-use
of an existing prefix, so this differs from makeElement2.
> XSLTC c
XSLTC creates namespace nodes when it could re-use existing ones in scope.
--
Key: XALANJ-2411
URL: https://issues.apache.org/jira/browse/XALANJ-2411
Project: XalanJ2
ectly resolves the
problem.
> XSLTC doesn't correctly set the parent of some nodes ... compile time
> failures result
> -
>
> Key: XALANJ-2389
> URL: https://i
[
https://issues.apache.org/jira/browse/XALANJ-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Minchau reassigned XALANJ-2389:
-
Assignee: Brian Minchau
> XSLTC doesn't correctly set the parent of so
same testcase:
http://www.w3.org/1999/XSL/Transform";>
,,,
The correct output is:
352,352,352,352
Note that this is an XSLTC problem, it works fine for the interpreter.
> XSLTC doesn't correctly set the parent of some nodes
set a non-default value.
That's not quite true. There is a Stylesheet.setTemplateInlining(boolean)
method, which the ApplyImports, Import, Include, and most importantly, the
XSLTC class all reference. The XSLTC class in particular uses the value
of its own _templateInlining field, which h
I agree that the default for a new switch should probably be "the way it
used to work before the switch was added" unless the new mode will be an
improvement for most users. Defaulting to performance mode rather than
debugging (I assume) mode makes sense to me. Second the motion to make this
one d
There are three pending issues before Apache Xalan-J 2.7.1 goes into
test/build/distribute mode:
XALANJ-2206
XALANJ-2395
XALANJ-1243
The PMC has voted for the release 2.7.1, allowing for a few last moment
fixes to get in, and those 3 are the fixes.
I'm fine with 2395 and 1243 and am personally r
OK. I have opened a bug in Jira and attached a simple test case. The
transformation runs as expected when simply run.
The bug occurs when you try to pre-compile the XSL. When you do this,
the xsl:import cannot be found. It does not enter the custom URIResolver
(TemplatesResolver)
best,
-Rob
On
On Sep 18, 2007, at 10:27 AM, Robert Koberg wrote:
But it is pretty simple to reproduce:
- create an XSL file the either imports or includes another XSL, and
uses the document function to bring in an XML. The files should not be
relative to the XSL
- create two URIResolvers that can resolve (p
how the problem.
This has been a bug for as long as XSLTC has existed. I have reported it
several times.
But it is pretty simple to reproduce:
- create an XSL file the either imports or includes another XSL, and
uses the document function to bring in an XML. The files should not be
relative
On Sep 17, 2007, at 6:37 PM, Robert Koberg wrote:
On Mon, 2007-09-17 at 18:02 -0400, Santiago Pericas-Geertsen wrote:
On Sep 15, 2007, at 8:49 PM, Robert Koberg wrote:
Hi,
Has anything or will anything be done for XSLTC to use a resolver
for
xsl:import/xsl:include for the Templates
On Mon, 2007-09-17 at 18:02 -0400, Santiago Pericas-Geertsen wrote:
> On Sep 15, 2007, at 8:49 PM, Robert Koberg wrote:
>
> > Hi,
> >
> > Has anything or will anything be done for XSLTC to use a resolver for
> > xsl:import/xsl:include for the Templates object.
On Sep 15, 2007, at 8:49 PM, Robert Koberg wrote:
Hi,
Has anything or will anything be done for XSLTC to use a resolver for
xsl:import/xsl:include for the Templates object.
You mean other than the URIResolver that you can set on the
TransformerFactory?
-- Santiago
Xalan interpretive
Hi,
Has anything or will anything be done for XSLTC to use a resolver for
xsl:import/xsl:include for the Templates object.
Xalan interpretive does do this and allows you to set a different
resolver for the Transformer. (So does Saxon 6x).
Thanks,
-Rob
Invalid AccessControlException for XSLTC with SecurityManager
-
Key: XALANJ-2397
URL: https://issues.apache.org/jira/browse/XALANJ-2397
Project: XalanJ2
Issue Type: Bug
tParent() issue.
> XSLTC doesn't correctly set the parent of some nodes ... comile time failures
> result
>
>
> Key: XALANJ-2389
> URL: https://iss
XSLTC doesn't correctly set the parent of some nodes ... comile time failures
result
Key: XALANJ-2389
URL: https://issues.apache.org/jira/browse/XALANJ-2389
Pr
repository.
> NullPointerException for reference to key function in a top-level variable
> with XSLTC
> -
>
> Key: XALANJ-2384
> URL: https://issues.apache.org/jira/
1 - 100 of 3289 matches
Mail list logo
