> AttributeImpl is a helper class in SAX. Its addAttribute() method is
namespace-aware.
Sorry; missed that. Good.
(I've spent too much time educating people about this since DOM2 came out;
it's an automatic playback trigger. Sigh.)
__
"You build world of s
> This issue can happen in JDK 6 if an Attribute is created with SAX
> AttributeImpl addAttribute() method and a "type" string argument of
Quick reminder: NOBODY should still be using the addAttribute() method
unless you are explicitly writing DOM 1.0 code. It is not interoperable
with DOM 2.
Whose JDK?
IBM's JDK 6 (ships with some of IBM's products, though I believe it's not
available separately) uses an interpreter derived from Xalan-J, and a
compiler which is new code.
Sun's JDK 6, as far as I know, still uses a very outdated and relatively
buggy copy of Xalan-J for both interpr
The compiler is telling you that you're passing in the wrong kind of
string. The function expects XMLCh chararacters, not XalanDOMChar
characters.
__
"You build world of steel and stone
I build worlds of words alone
Skilled tradespeople, long years taught:
Yo
First step: Can you build and run without your change?
If so: The code thinks your change is incorrect, since it is having
unintended effects. Ask whether you really need this change at all, and/or
whether there's another way to accomplish what you need. You SHOULDN'T
have to patch code to hand
Sanity check: I presume you're asking about Xalan for C++, since the Java
code would not require cross-compilation.
Theoretically, it should be just like cross-compiling to any other
platform: Get the cross-compiler. Figure out what options to set in the
code in order to match that machine's a
Michael Glavassevich wrote on 06/27/2011 12:44:36
AM:
> If the intention is to contribute the code to Xalan, in my opinion
> it would be better for the effort to be here. Folks interested in
> contributing can become committers.
+1000. It isn't hard to work with the Apache development environm
> I would not use XML and XSLT for PDF document pagination.
> I instead use XSLT to convert XML into a LaTex markup language and then
> let the underlying troff/groff processors generate the actual content
for
> printing and publishing.
For what it's worth, something very similar to that was the
Unfortunately this is actually an issue in a back-level version of our
internal branch of Xalan-C, which limits what I can tell/show you.
(Actually, given the symptoms we're seeing, I wouldn't bet against a wild
pointer in the customer's code -- they're seeing SIGILL one one platform
and SIGSEG
Just trying this on the chance that someone might recognize it...
Does anyone happen to remember a Xalan-C bug which caused the creation of
temporary trees which had no DocumentFragment root node, and if so do you
happen to remember what caused it?
(Can't switch the customer to current Xalan-C.
By turning the pretty-printing flag on, you gave the system permission to
inject whitespace to indent the elements nicely. If that isn't what you
wanted, don't request it
__
"... Three things see no end: A loop with exit code done wrong,
A semaphore untes
Usually what this error means is that you have a single xsl:template
which is excessively complex. There's a Java limitation on how large a
single method may be, and a template starts out as a single method.
Xalan's code generation attempts to modularize excessively large
functions, but it loo
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 things see no end: A loop
If you're outputting in UTF-8, it can express all of Unicode directly (as
two- or three-byte sequences if necessary), so Numeric Character
References generally won't be needed and won't be produced.
If you set the output encoding to ASCII rather than UTF-8, any characters
over 127 will be escap
> 1) PsychoPath is not "streamy" yet
Nor is Xalan, really. We have some ability to do deferred loading of the
document, but real streaming is one of those "always wanted, never got
around to" projects. It's a _big_ challenge.
> 2) Type informations is not part of current interfaces.
True. One
> Is it that big an ask to be able to set a variable from an extension
element?
Specifically, to set a variable to something other than XPath-compatable
data, since of course the syntax you show already works for result tree
fragments...
... I'm really not sure. Probably worth drafting a prot
I'm still not sure I understand why you feel you have to express this as
extension elements, when extension functions can already do what you
(appear to) need?
__
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the ch
> Can anyone tell me if there's any way to add an object (not node or
> tree fragment) variable to the variable stack from an extension element?
>From an extension _element_... I don't think so.
>From an extension _function_, yes. If the returned value is not an
instanceof one of the types cal
> > If I were to write an xslt processor from scratch, I'd either drop DTM
> > altogether, or have the transformation work on some interface which
can
> > be provided from both DOM and DTM. I'd also try to get some closer
> > integration between the xslt interpreter and the xsltc compiler, i.e.
>
Better link to the IBM beta:
http://webspherecommunity.blogspot.com/2009/07/xml-feature-pack-xpath-20xslt-20xquery.html
Unfortunately, some of the folks who have been working on that are the
same people who had previously been providing most of the active support
for Xalan
Of course Xa
I believe David is referring to
http://webspherecommunity.blogspot.com/2009/04/was-open-xml-feature-pack-beta.html
__
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
-- "Threes" Rev 1
Search for "keshlam". That's Joe Kesselman. (IE, me.)
I've become less active in part because I've been fully overcommitted
(grin) to other projects. In general I've been waiting to let the
community answer questions, and only throwing my two cents in if I can do
What you're looking for is the xsl:number directive. Standard XSLT, not an
EXSLT library function.
__
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
-- "Threes" Rev 1.1 - Duane Elms
Second the nomination of the estimable Mr. Bertoni, if he's willing to
take the job. Dave's been involved in Xalan more or less since it started,
and has been the prime mover behind keeping Xalan-C alive. "The reward for
doing a job well is that people want you to do even more of it..."
___
In Xalan-J, the solution would be to output to a SAX stream as UTF-8 or
UTF-16, and then route that stream through a separate serializer which
converts it to the appropriate encoding. It's been too long since I've
looked at Xalan-C, but I presume something similar is possible there.
___
I'm not sure if it's still there, but at one point we did experiment with
an extension function which could be used to flush document()s out of the
cache, specifically for those applications where a stylesheet is scanning
through a document which itself is a long list of documents.
If anyone kn
The main trick to building Xalan in Eclipse is making sure that Eclipse
finds the copy you're trying to build rather than the outdated one
provided by the JVM. This can most easily be done by opening the
Preferences, going down to Installed JREs, duplicating the entry for your
preferred JRE, an
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
I'm not a PMC member, but given that Dave basically *is* the Xylem-C team
I'd certainly consider this appropriate.
__
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
-- "Threes" Rev 1
We've known for a while that some part of Xalan are oversynchronized, due
to their use of the original Java heap and vector classes -- but we
couldn't move to the unsynchronized 1.2 Collection classes because we were
still committed to running on Java 1.1.8.
Now that Xerces has given up compatabi
Just making sure I understand the question: Is the user looking for arbitrary XPath interpretation, similar to
http://www.exslt.org/dyn/
or are they specifically looking for the equivalent of select?
We do have an implementation of exslt:dyn, though of course it works only in interpretive mode a
31 matches
Mail list logo
