RE: Undeclared namespace prefix

Scott Cantor wrote: > >> Aside from the embarrassment though, it remains the case that the >> serializer does not need the assistance of setAttributeNS; it does this >> job itself. > > There's no such thing as "the serializer". There are hundreds of things > called "serializers". DOM3 includes

Re: Undeclared namespace prefix

Werner Dittmann wrote: > Peter B. West schrieb: > >>> you're using namespaces. >>> >> >> setAttributeNS doesn't work for me following createElementNS. I get >> org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or >> c

Re: Undeclared namespace prefix

something wrong. >> > > I'm pretty sure that's because of your bug, using a DOM1 call to create that > initial attribute. > >> I'm not sure when this arrangement of the namespace and attribute occurs, >> but the ordering may be affected by the

RE: Undeclared namespace prefix

Scott Cantor wrote: > >> Because we use it in WSS4J we always rely on the backward compatibility. >> Changing the WSS4J code just to circumvent a problem would cause a major >> effort to many applications that actually use WSS4J. Before changing >> WSS4J we shall check if a fix in xmlsec is more

Re: Can't trace org.jcp.xml.dsig.internal.dom.DOMXMLSignature in NetBeans

Thanks Sean. Yes, I tried that. I was interested to see if any problems that would surface for a user of the JDK, that were fixed in 1.4.2. Peter sean.mullan wrote: > > Peter B. West wrote: >> That was quick. The source for org.jcp is not part of src.zip in the JDK >> dist

Re: Questions about xml-security-1.4.2 and Java 1.6

Sean, you mention that JDK6 include 1.3.1 + bug fixes. Where can I get hold of the source as included in 1.6? Peter sean.mullan wrote: > > dan costelloe wrote: >> Greetings, >> >> I've recently been tinkering with xml-security-1.4.2 and the experience >> so far >> has left me with some quest

Re: Can't trace org.jcp.xml.dsig.internal.dom.DOMXMLSignature in NetBeans

That was quick. The source for org.jcp is not part of src.zip in the JDK distribution. If I try to use the xmlsec-1.4.2.jar sources, things go wrong, naturally. Where can I get the sources that were included in the JDK? I'm used 1.6.0_07 and 1.6.0_10RC. Peter B. West wrote: > >

Can't trace org.jcp.xml.dsig.internal.dom.DOMXMLSignature in NetBeans

I've been trying to track down problems by tracing in NetBeans. I am using the JSR-105 API for the signature components, so I assume that I am getting these classes from rt.jar, as there is no services SPI in the xmlsec-1.4.2.jar. When I try to trace the calls using NetBeans, the trace skips stra

Re: Undeclared namespace prefix

se a major >> effort to many applications that actually use WSS4J. Before changing >> WSS4J we shall check if a fix in xmlsec is more appropriate. >> >> Regards, >> Werner >> >> Arnaud schrieb: >>> Peter B. West pbw.id.au> writes: >

Re: Undeclared namespace prefix "ds" error

ase let me know because I don't know what to do > about > it and I've alread spend many hours on this... > > Thanks in advance for any help. > > Arnaud. -- Peter B. West <http://cv.pbw.id.au/> Folio <http://defoe.sourceforge.net/folio/>

Re: Unbound prefix after decryption

ng players, I suppose. Is this the way things ought to be, or should the canonicalization be checking the namespace and prefix components on each element, and including an xmlns attribute when any change occurs between an element and its parent? Peter B. West wrote: > > I've encounte

Unbound prefix after decryption

I've encountered a strange problem in the process of decrypting a message which had been signed using xml:dsig before being encrypted with xml-security. The elements wrapping both the signed message and the encrypted message were defined in the same namespace, and given the same prefix: "sp" in t