Raul Benito wrote:
I have something implemented for SAX as you can see bugzilla entry
http://issues.eu.apache.org/bugzilla/show_bug.cgi?id=32657 .
And I have take a look for JSR105, but i think the tree API is not
100% applicable to
for example one pass implementations.
In this cases, there should be a way in the verification API, to tell
when the element to digest begins and what transforms apply.
In case enveloping signatures this information can be stored from there.
But in case of enveloped signatures, this information should be passed
by the caller, if he/she wants a one pass verification (i.e. no
backstore/replay mechanism; store every event/node to replay it latter
when all information has been gotten).
I don't know how to handle this case in JSR105, perhaps it is a way or
perhaps it should extended to this cases.
What do you think?
Right, it will probably need to be extended in a future revision to add
support for one-pass implementations. But that's ok we can add
non-standard APIs for now and work it thru the JCP later. I think what
is more important is seeing if the 105 API is flexible enough to be
extended to handle your implementation.
Thanks,
Sean
