You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@santuario.apache.org by Xiaopong Tran <xp...@idsignet.com> on 2003/06/17 08:42:19 UTC

question on XMLSignature constructor

I remember someone has asked the question on this forum before, but couldn't
find it. 

What was the reason that all the constructors of XMLSignature must have
a base URI? Say, if app1 receives a DOM object from somewhere that it
needs to sign, and after signing, passes the DOM object to the next
application app2 (and all without writing to a file), and app2 has to 
verify the signature, ... some system flow like this, you see what
I mean. 

How do you handle things like that?

thanks

x


Re: question on XMLSignature constructor

Posted by Xiaopong Tran <xp...@idsignet.com>.
On Tuesday 17 June 2003 15:06, Christian Geuer-Pollmann wrote:
> If the signed contents are *RELATIVE* to a signed document, e.g. a file in
> the file system, the XMLSignature must know what it's own location is.
>
> When the signed contents are in the same document as the signature, you can
> set BaseURI to "" or null or "memory://" or whatever...
>

Thanks, that was fast, I haven't even finished reading in the code where
that BaseURI ends up with yet :)

rgds

x

Re: question on XMLSignature constructor

Posted by Christian Geuer-Pollmann <ge...@nue.et-inf.uni-siegen.de>.
If the signed contents are *RELATIVE* to a signed document, e.g. a file in 
the file system, the XMLSignature must know what it's own location is.

When the signed contents are in the same document as the signature, you can 
set BaseURI to "" or null or "memory://" or whatever...

--On Dienstag, 17. Juni 2003 14:42 +0800 Xiaopong Tran <xp...@idsignet.com> 
wrote:

> I remember someone has asked the question on this forum before, but
> couldn't find it.
>
> What was the reason that all the constructors of XMLSignature must have
> a base URI? Say, if app1 receives a DOM object from somewhere that it
> needs to sign, and after signing, passes the DOM object to the next
> application app2 (and all without writing to a file), and app2 has to
> verify the signature, ... some system flow like this, you see what
> I mean.
>
> How do you handle things like that?
>
> thanks
>
> x
>