Quick follow up on that one: (1) I did the revert, i.e. the example should work now.
(2) The next version of wss4j (3.0.x) seems to support the method signature changes of xmlsec/santuario as they internally upgraded. Their release is under vote [1] and needs to get picked up by cxf in the chain. Gruß Richard [1] https://lists.apache.org/thread/rzww6qqt06wmvcf9hv607o63ddm8mzzt Am Samstag, dem 08.10.2022 um 11:33 +0000 schrieb Zowalla, Richard: > Hi David, > > good catch! Looks like we didn't were that far with the build in > July, > so didn't notice that one :) > > It looks like CXF 3.5.x depends on xmslec 2.3.0 - I tested it with > 2.3.0, but no luck either. Needs some digging, upgrade / patching. > > For now, I will revert the upgrade commit to the previous version > (2.2.3) on main and cleanup jira accordingly + leave some information > in the related tickets, so I can do some digging in cxf, wss4j, etc. > later. That thing shouldn't block our efforts in stabilizing the > build. > > > Gruß > Richard > > > > Am Samstag, dem 08.10.2022 um 02:23 -0500 schrieb David Blevins: > > FYI this upgrade is what is breaking `examples/webservice-ws- > > security` > > > > The version 2.2.3 or 2.2.4 will cause the example's test to > > pass. The version 3.0.0 causes the failure due to missing method > > signature. I also tried 2.3.2, but no luck. > > > > I didn't revert as I figured Richard might have some preferences on > > how to proceed. Looks like either a CXF patch or a downgrade and > > jira cleanup would work. > > > > > > -David > >
smime.p7s
Description: S/MIME cryptographic signature
