We can probably include this upgrade in the CXF 4.1 or later version after it's released and get into WSS4j. AFAIK, there is no CXF or WSS4j issue blocked by the OpenSAML 5.0.0 upgrade. @Colm O hEigeartaigh <[email protected]> @Andriy Redko <[email protected]> WDYT ?
On Mon, Nov 7, 2022 at 9:25 PM Misagh <[email protected]> wrote: > Hello all, > > If possible, I'd like to ask that you allow v4 to ship with a new > release of wss4j that would contain this change: > https://github.com/apache/ws-wss4j/pull/62 > > At the moment, OpenSAML v5 is not released yet, but it is anticipated > to be GA before end of this year, hopefully. > > On Mon, Nov 7, 2022 at 12:19 PM Jim Ma <[email protected]> wrote: > > > > Hi all, > > After 9 months of work, we finally fixed/worked around all issues for > > Jakarta support. Now all the cxf tests are passed: > > https://ci-builds.apache.org/job/CXF/job/CXF-JDK17/848/ and we can say > that > > CXF successfully migrated to Jakarta namespace(and support Jakarta > EE9.1). > > To get cxf jakarta artifacts/binary available for the CXF community > > especially the user who asked for this jakarta artifacts like [1] and > get > > more feedback from our community, do you think it's time to release the > CXF > > 4.0.0 and what else do you think we should have in this new jakarta > release > > ? > > > > [1]https://lists.apache.org/thread/kwfg2s5gj72tkgn5c5vdcsvtgdkdm6dl > > > > Thanks, > > Jim >
