[EMAIL PROTECTED] wrote:
Well,
In the current c14n implementation changing the behaviour is only a how
the symb table is create(i.e. When I create the symbol table the
xmlns="" binding is marked as rendered, so it is not emitted), I can
parametrized this behaviour.
But what happend in the excl c1
Dittmann Werner wrote:
This behaviour is absolutely necessary in order that exclusive
canonicalization can function correctly in the case of
changes to apex definitions of the default namespace. The
canonicalization specifications should both have been
defined to always emit apex xmlns=""; this la
> Berin,
>
> well I don't know if it is the same reason as for
> encryption. During the discussion I also asked
> one of the WSS gurus about the topic. Here is his
> answer to my question:
>
>
> This behaviour is absolutely necessary in order that exclusive
> canonicalization can function correctl
:14
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: Question on c14n exclusive
>
>
> Dittmann Werner wrote:
>
> >
> > * Finally, employ the canonicalization method specified as
> a parameter to the transform to
> > serialize N to produce the octet stream output
Dittmann Werner wrote:
* Finally, employ the canonicalization method specified as a parameter to the transform to
serialize N to produce the octet stream output of this transform; but, in place of any
dereferenced element Ri and its descendants,
process the dereferenced node set Ri' instead. Dur
m can be sloved.
Regards,
Werner
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 27. Mai 2004 17:22
An: [EMAIL PROTECTED]
Betreff: Re: AW: Question on c14n exclusive
Raul,
thanks.
However, the element that I
On 27/05/2004, at 17:34, Dittmann Werner wrote:
Raul,
already tried that hack, the problem with that is that
c14n outputs either a byte buffer that is the XML
docu as String or as a node set - this has to be
serialized then deadlock.
Well, I try to ask the WSS guys how they think this
problem c
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 27. Mai 2004 17:22
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: Question on c14n exclusive
>
>
> > Raul,
> > thanks.
> >
> > However, the element that I c
> Raul,
> thanks.
>
> However, the element that I create is a top level
> elemen, i.e. an apex node (as far as I understand the
> c14n specs). According to the WSS specs
>
>
> * Finally, employ the canonicalization method specified as a parameter to
> the transform to
> serialize N to produce the
nicalizeXPathNodeSet(nodeset, incNamespace) would this
work? A very confusing topic :-) (And hard to read specs too).
Regards,
Werner
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 27. Mai 2004 15:29
> An: [EMAIL PROTE
> All,
>
> a question to the c14 gurus on the list.
>
> I set up an Element node and set the default namespace
> to "" using the following code:
>
>elem.setAttributeNS(WSConstants.XMLNS_NS, "xmlns", "");
>
> This seems to work.
>
> The element is c14n'ed using the following code:
>
>XMLUtil
All,
a question to the c14 gurus on the list.
I set up an Element node and set the default namespace
to "" using the following code:
elem.setAttributeNS(WSConstants.XMLNS_NS, "xmlns", "");
This seems to work.
The element is c14n'ed using the following code:
XMLUtils.circumventBug2650(e
12 matches
Mail list logo
