Re: [VOTE] - Release Apache Santuario - XML Security for Java 2.0.9

+1 (non-binding) Cheers, Hugo > On 14 Aug 2017, at 13:10, Colm O hEigeartaigh wrote: > > This is a vote to release Apache Santuario - XML Security for Java 2.0.9. > This is a minor bug fix release - perhaps the most significant fix is to > allow setting default

SANTUARIO-458

Hey Colm, Whats the next step in discussing the patch for SANTUARIO-458? Does my solution make sense given the requirements of the interface i’m trying to talk to or should i try for an alternative approach? Cheers, Hugo

Re: [VOTE] - Release Apache Santuario - XML Security for Java 2.0.8

gt; > > Colm. > > On Fri, Dec 2, 2016 at 1:37 PM, Hugo Trippaers <trip...@gmail.com > <mailto:trip...@gmail.com>> wrote: > Hey Colm, > > Was there something still wrong with the patch for SANTUARIO-458 so it > couldn’t be included on 2.0.8? > >

Re: [VOTE] - Release Apache Santuario - XML Security for Java 2.0.8

Hey Colm, Was there something still wrong with the patch for SANTUARIO-458 so it couldn’t be included on 2.0.8? Cheers, Hugo > On 1 Dec 2016, at 14:39, Colm O hEigeartaigh wrote: > > This is a vote to release Apache Santuario - XML Security for Java 2.0.8. > > Issues

Question on specific document requirements

Hey folks, Hope this is the right place to ask this, but i’m working on an interface to a system with some specific requirements i haven’t figured out yet. I’ve got some of them covered so far (they use KeyName as key identifier for example), but i have a few remaining things i need to solve

Re: KeyName support in santuario

t; Colm. > > On Mon, Oct 10, 2016 at 3:24 PM, Hugo Trippaers <trip...@gmail.com> wrote: > Hello, > > I’m working on a project that uses KeyName to identify the key used to verify > or sign the signature. I’m using the santuario library through the > XmlSecIn/Ou