Re: [xmlsec] Re: Problems signing...
Looks like the root element in xmlDocPtr (could be obtained using xmlDocGetRootElement()) is NULL. This can be if you have mailformed XML document in the input. I think that the simplest way to check this is to save XML template just before signing. Aleksey Robert Wittams wrote: >Sorry to bother you (again ... ), but is there a similarly obvious >explanation for the error: > >xmlSecGetChildNodeSet: the node is null >xmlSecTransformStateParseUri: failed to create node set >xmlSecTransformStateCreate: uri parsing failed >xmlSecReferenceRead: failed to create transforms state > >in the reference node. This is using an empty URI. >The xml does have a xmlDocPtr ( is this necessary? ) > >Sorry to be a pain, >Rob > > >On Tuesday 18 Jun 2002 9:11 pm, you wrote: > > >>As you've said it was "something obvious" :) >> >>Aleksey. >> >>Robert Wittams wrote: >> >> >>>Doh, >>> >>>forgot to init library, so transform array was empty. >>> >>>Robert Wittams >>> >>>On Tuesday 18 Jun 2002 7:24 pm, Robert Wittams wrote: >>> >>> Hi, I am getting the error: xmlSecTransformNodeRead: id "http://www.w3.org/TR/2001/REC-xml-c14n-20010315"; is unknown when trying to sign messages. I'm using the included constants, generating the signature node, it is not a template. The URI is the same as in the sources of xmlsec. This happens with all C14N method constants. Could it be a lbxml2 / xmlsec mismatch? I'm using 0.0.6, and the debian unstable libxml2. (2.4.22) I tried to use the CVS snapshot, but it seems to require CVS libxml2 which is a bit of a hassle. Or is this something obvious? Robert Wittams >>>___ >>>xmlsec mailing list >>>[EMAIL PROTECTED] >>>http://www.aleksey.com/mailman/listinfo/xmlsec >>> >>>
Re: [xmlsec] Re: Problems signing...
As you've said it was "something obvious" :) Aleksey. Robert Wittams wrote: Doh, forgot to init library, so transform array was empty. Robert Wittams On Tuesday 18 Jun 2002 7:24 pm, Robert Wittams wrote: Hi, I am getting the error: xmlSecTransformNodeRead: id "http://www.w3.org/TR/2001/REC-xml-c14n-20010315" is unknown when trying to sign messages. I'm using the included constants, generating the signature node, it is not a template. The URI is the same as in the sources of xmlsec. This happens with all C14N method constants. Could it be a lbxml2 / xmlsec mismatch? I'm using 0.0.6, and the debian unstable libxml2. (2.4.22) I tried to use the CVS snapshot, but it seems to require CVS libxml2 which is a bit of a hassle. Or is this something obvious? Robert Wittams ___ xmlsec mailing list [EMAIL PROTECTED] http://www.aleksey.com/mailman/listinfo/xmlsec
[xmlsec] Re: Problems signing...
Doh, forgot to init library, so transform array was empty. Robert Wittams On Tuesday 18 Jun 2002 7:24 pm, Robert Wittams wrote: > Hi, > > I am getting the error: > > xmlSecTransformNodeRead: id > "http://www.w3.org/TR/2001/REC-xml-c14n-20010315"; is unknown > > when trying to sign messages. I'm using the included constants, generating > the signature node, it is not a template. The URI is the same as in the > sources of xmlsec. This happens with all C14N method constants. > > Could it be a lbxml2 / xmlsec mismatch? > I'm using 0.0.6, and the debian unstable libxml2. (2.4.22) > > I tried to use the CVS snapshot, but it seems to require CVS libxml2 which > is a bit of a hassle. > > Or is this something obvious? > > Robert Wittams