Yup.

I've also worked out the problem, but I need some advice from everyone as to the "right" fix.

The samples create a manifest object that refers to a URI in the rest of the signature. At the time the manifest is created, the element that will hold the relevant Id has not yet been added to the document. So when the sample calls "generateDigestValues" for the manifest, one of the references cannot be resolved.

In the "pre-Raul" (:>) code, that quietly continued. In the post-raul code, a run-time exception (indicating an empty input to a transform) is thrown.

My personal opinion is that the latter is the correct behaviour. If you have a reference in your document, and the Id cannot be resolved, then the library should throw an exception.

What do others think?

Cheers,
        Berin


Davanum Srinivas wrote:


np. we should add "mega-sample" target to the "test" itself.

-- dims

On Wed, 12 May 2004 22:34:29 +1000, Berin Lautenbach
<[EMAIL PROTECTED]> wrote:

Dims,

I just tried to apply your new code for Merlin-23 and it's flushed out
that the mega-sample target is now throwing an exception when it creates
a non XSLT target (and so is the new 23).

I think this is something to do with the new optimisations, but I'll try
and track it down later this week.

So it's going to take me a little while longer to get the 23 code into
CVS :<.

Cheers,
       Berin





Reply via email to