Hi Daniel,
I tried your xsl, but I got the same result using either JDK 8 or a
recent JDK 9 (jdk9dev) build:
xmlns="ns2">xmlns="ns2">
For the issue with regard to empty namespace, please open a bug and
let's fix it.
Thanks,
Joe
On 7/26/16, 10:32 AM, Daniel Fuchs wrote:
Hi Christoph,
I
Hi Christoph,
I was at first a bit suspicious of your proposed patch, but
I applied it and played with it and could not fault it.
Now I tend to believe this is the correct thing to do (though
that's not my area of expertise).
I tried it with a bit more elaborate content in the "transform"
templa
On 26/07/16 14:53, Langer, Christoph wrote:
you mean with my webrev built in or with the current jdk9 dev?
... and with your patch applied I see this:
xmlns="ns1">
cheers,
-- daniel
Hi Christoph,
On 26/07/16 14:53, Langer, Christoph wrote:
Hi Daniel,
you mean with my webrev built in or with the current jdk9 dev?
With the current jdk9 dev - sorry if that was unclear.
cheers,
-- daniel
public static void main(String[] args) throws XMLStreamException,
Tra
Hi Christoph, Joe,
Actually what I see with the latest dev version of
JDK 9 (eng. build built a few minutes ago) is this:
xmlns="ns1">
Notice that xmlns="ns1" appears twice in the root element.
So maybe there's more than one bug here :-(
cheers,
-- daniel
On 26/07/16 12:56, Langer, Christo
v@openjdk.java.net
> Subject: Re: JAXP: XSLTC transformer swallows empty namespace declaration
> which is necessary to undeclare default namespace
>
> Hi Christoph, Joe,
>
> Actually what I see with the latest dev version of
> JDK 9 (eng. build built a few minutes ago) is this:
&g
Hi Joe,
thanks for looking at this.
Here is my comments:
> I'm not sure why empty namespace was explicitly excluded. But for the
> 2nd part, the developer was clear with a note on the intention. You may
> want to try removing the condition statement that excluded the empty
> namespace, but keep t
On 7/22/2016 3:38 AM, Langer, Christoph wrote:
Hi,
I have a customer reporting the following phenomena which I believe is an issue.
Consider the following xsl:
-XSL-
http://www.w3.org/1999/XSL/Transform"; version="1.0">
Hi,
I have a customer reporting the following phenomena which I believe is an issue.
Consider the following xsl:
-XSL-
http://www.w3.org/1999/XSL/Transform"; version="1.0">
