You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@santuario.apache.org by Rebecca Searls <rs...@redhat.com> on 2021/11/23 13:25:17 UTC
A jakarta namespace version
Wildfly components requires a jakarta namesapce version of
org.apache.santuario:xmlsec.
I have created such a version. I would like to submit a PR for it.
Re: A jakarta namespace version
Posted by Colm O hEigeartaigh <co...@apache.org>.
Yes, good point.
Colm.
On Thu, Dec 2, 2021 at 10:26 AM Matti Aarnio <ma...@methics.fi> wrote:
>
> Given that the Jakarta-namespace change is major incompatibility with previous versions,
> perhaps you should call it 3.0.0 ?
>
> Best Regards,
> Matti
>
> On 02/12/2021 12.16, Colm O hEigeartaigh wrote:
>
> The main reason is that we have just released a new major version of
> Santuario (2.3.0). However, I think we could get 2.4.0 out in
> January/Feb next year with the changes and drop 2.1.x, does it work
> for you?
>
> Colm.
>
>
Re: A jakarta namespace version
Posted by Matti Aarnio <ma...@methics.fi>.
Given that the Jakarta-namespace change is major incompatibility with
previous versions,
perhaps you should call it 3.0.0 ?
Best Regards,
Matti
On 02/12/2021 12.16, Colm O hEigeartaigh wrote:
> The main reason is that we have just released a new major version of
> Santuario (2.3.0). However, I think we could get 2.4.0 out in
> January/Feb next year with the changes and drop 2.1.x, does it work
> for you?
>
> Colm.
Re: A jakarta namespace version
Posted by Rebecca Searls <rs...@redhat.com>.
Let me know if I can help with any of this.
On Thu, Dec 2, 2021 at 9:20 AM Rebecca Searls <rs...@redhat.com> wrote:
> Yes, Colm. A Santuario 3.0.0 in January/Feb 2022 works for us. We at
> RedHat would be happy to help.
>
> On Thu, Dec 2, 2021 at 8:41 AM Cantor, Scott <ca...@osu.edu> wrote:
>
>> On 12/2/21, 8:14 AM, "Colm O hEigeartaigh" <co...@apache.org> wrote:
>>
>> > If there is demand then I don't mind keeping 2.1.x for a while
>> longer.
>>
>> I doubt there's demand from anyone but me, but we don't generally break
>> API compatibility outside of a major version, which isn't imminent for us
>> until Spring 6 is out (which is also when we're expecting to move to
>> Jakarta.
>>
>> We would prefer at least 6 months notice to get something done but as
>> long as we have a date that's the main thing.
>>
>> -- Scott
>>
>>
>>
Re: A jakarta namespace version
Posted by Rebecca Searls <rs...@redhat.com>.
Yes, Colm. A Santuario 3.0.0 in January/Feb 2022 works for us. We at
RedHat would be happy to help.
On Thu, Dec 2, 2021 at 8:41 AM Cantor, Scott <ca...@osu.edu> wrote:
> On 12/2/21, 8:14 AM, "Colm O hEigeartaigh" <co...@apache.org> wrote:
>
> > If there is demand then I don't mind keeping 2.1.x for a while longer.
>
> I doubt there's demand from anyone but me, but we don't generally break
> API compatibility outside of a major version, which isn't imminent for us
> until Spring 6 is out (which is also when we're expecting to move to
> Jakarta.
>
> We would prefer at least 6 months notice to get something done but as long
> as we have a date that's the main thing.
>
> -- Scott
>
>
>
Re: A jakarta namespace version
Posted by "Cantor, Scott" <ca...@osu.edu>.
On 12/2/21, 8:14 AM, "Colm O hEigeartaigh" <co...@apache.org> wrote:
> If there is demand then I don't mind keeping 2.1.x for a while longer.
I doubt there's demand from anyone but me, but we don't generally break API compatibility outside of a major version, which isn't imminent for us until Spring 6 is out (which is also when we're expecting to move to Jakarta.
We would prefer at least 6 months notice to get something done but as long as we have a date that's the main thing.
-- Scott
Re: A jakarta namespace version
Posted by Colm O hEigeartaigh <co...@apache.org>.
If there is demand then I don't mind keeping 2.1.x for a while longer.
It only gets security fixes anyway at this stage.
Colm.
On Thu, Dec 2, 2021 at 1:02 PM Cantor, Scott <ca...@osu.edu> wrote:
>
> On 12/2/21, 5:16 AM, "Colm O hEigeartaigh" <co...@apache.org> wrote:
>
> > The main reason is that we have just released a new major version of
> > Santuario (2.3.0). However, I think we could get 2.4.0 out in
> > January/Feb next year with the changes and drop 2.1.x, does it work
> > for you?
>
> Dropping 2.1 with that little notice is a little inconvenient, but I guess if that's the notice my project will have to make do.
>
> -- Scott
>
>
Re: A jakarta namespace version
Posted by "Cantor, Scott" <ca...@osu.edu>.
On 12/2/21, 5:16 AM, "Colm O hEigeartaigh" <co...@apache.org> wrote:
> The main reason is that we have just released a new major version of
> Santuario (2.3.0). However, I think we could get 2.4.0 out in
> January/Feb next year with the changes and drop 2.1.x, does it work
> for you?
Dropping 2.1 with that little notice is a little inconvenient, but I guess if that's the notice my project will have to make do.
-- Scott
Re: A jakarta namespace version
Posted by Colm O hEigeartaigh <co...@apache.org>.
The main reason is that we have just released a new major version of
Santuario (2.3.0). However, I think we could get 2.4.0 out in
January/Feb next year with the changes and drop 2.1.x, does it work
for you?
Colm.
On Mon, Nov 29, 2021 at 3:59 PM Rebecca Searls <rs...@redhat.com> wrote:
>
> > WSS4J only uses the javax.xml.bind dependencies for the streaming implementation,
> > which is currently only consumed by CXF. CXF won't switch to using Jakarta for a
> > while, so until then I think there's not much point in updating WSS4J.
>
> CXF is NOT the only consumer of WSS4J and its streaming code. Wildfly and thus
> EAP use it as do some of its (our) customers. And I would expect there are
> other products outside the CXF and Wildfly realm that use it as well.
>
> In the hierarchy of this ecosystem Santuario is a foundational component. Waiting
> for higher level components to move before moving this foundational component
> impedes the progress of all. Why must all be tied to CXF's schedule? Why can't the
> jakarta native version (e.g. https://github.com/apache/santuario-xml-security-java/pull/63)
> be provided for those who want to move now?
>
> On Mon, Nov 29, 2021 at 6:19 AM Colm O hEigeartaigh <co...@apache.org> wrote:
>>
>> We don't have an imminent release date yet, because the Santuario StAX
>> implementation is really only used by Apache CXF, and CXF confirmed to
>> me that it would be a while before they switch to using Jakarta.
>>
>> Colm.
>>
>> On Tue, Nov 23, 2021 at 8:14 PM Rebecca Searls <rs...@redhat.com> wrote:
>> >
>> > Yes, When will this be available and in a public repository?
>> >
>> > On Tue, Nov 23, 2021 at 12:22 PM Colm O hEigeartaigh <co...@apache.org> wrote:
>> >>
>> >> Hi Rebecca,
>> >>
>> >> I believe we have an existing PR -
>> >> https://github.com/apache/santuario-xml-security-java/pull/63
>> >> Or are you referring to something else?
>> >>
>> >> Colm.
>> >>
>> >> On Tue, Nov 23, 2021 at 1:25 PM Rebecca Searls <rs...@redhat.com> wrote:
>> >> >
>> >> > Wildfly components requires a jakarta namesapce version of org.apache.santuario:xmlsec.
>> >> > I have created such a version. I would like to submit a PR for it.
>> >>
>>
Re: A jakarta namespace version
Posted by Rebecca Searls <rs...@redhat.com>.
> WSS4J only uses the javax.xml.bind dependencies for the streaming
implementation,
> which is currently only consumed by CXF. CXF won't switch to using
Jakarta for a
> while, so until then I think there's not much point in updating WSS4J.
CXF is NOT the only consumer of WSS4J and its streaming code. Wildfly and
thus
EAP use it as do some of its (our) customers. And I would expect there are
other products outside the CXF and Wildfly realm that use it as well.
In the hierarchy of this ecosystem Santuario is a foundational component.
Waiting
for higher level components to move before moving this foundational
component
impedes the progress of all. Why must all be tied to CXF's schedule? Why
can't the
jakarta native version (e.g.
https://github.com/apache/santuario-xml-security-java/pull/63)
be provided for those who want to move now?
On Mon, Nov 29, 2021 at 6:19 AM Colm O hEigeartaigh <co...@apache.org>
wrote:
> We don't have an imminent release date yet, because the Santuario StAX
> implementation is really only used by Apache CXF, and CXF confirmed to
> me that it would be a while before they switch to using Jakarta.
>
> Colm.
>
> On Tue, Nov 23, 2021 at 8:14 PM Rebecca Searls <rs...@redhat.com> wrote:
> >
> > Yes, When will this be available and in a public repository?
> >
> > On Tue, Nov 23, 2021 at 12:22 PM Colm O hEigeartaigh <
> coheigea@apache.org> wrote:
> >>
> >> Hi Rebecca,
> >>
> >> I believe we have an existing PR -
> >> https://github.com/apache/santuario-xml-security-java/pull/63
> >> Or are you referring to something else?
> >>
> >> Colm.
> >>
> >> On Tue, Nov 23, 2021 at 1:25 PM Rebecca Searls <rs...@redhat.com>
> wrote:
> >> >
> >> > Wildfly components requires a jakarta namesapce version of
> org.apache.santuario:xmlsec.
> >> > I have created such a version. I would like to submit a PR for it.
> >>
>
>
Re: A jakarta namespace version
Posted by Colm O hEigeartaigh <co...@apache.org>.
We don't have an imminent release date yet, because the Santuario StAX
implementation is really only used by Apache CXF, and CXF confirmed to
me that it would be a while before they switch to using Jakarta.
Colm.
On Tue, Nov 23, 2021 at 8:14 PM Rebecca Searls <rs...@redhat.com> wrote:
>
> Yes, When will this be available and in a public repository?
>
> On Tue, Nov 23, 2021 at 12:22 PM Colm O hEigeartaigh <co...@apache.org> wrote:
>>
>> Hi Rebecca,
>>
>> I believe we have an existing PR -
>> https://github.com/apache/santuario-xml-security-java/pull/63
>> Or are you referring to something else?
>>
>> Colm.
>>
>> On Tue, Nov 23, 2021 at 1:25 PM Rebecca Searls <rs...@redhat.com> wrote:
>> >
>> > Wildfly components requires a jakarta namesapce version of org.apache.santuario:xmlsec.
>> > I have created such a version. I would like to submit a PR for it.
>>
Re: A jakarta namespace version
Posted by Rebecca Searls <rs...@redhat.com>.
Yes, When will this be available and in a public repository?
On Tue, Nov 23, 2021 at 12:22 PM Colm O hEigeartaigh <co...@apache.org>
wrote:
> Hi Rebecca,
>
> I believe we have an existing PR -
> https://github.com/apache/santuario-xml-security-java/pull/63
> Or are you referring to something else?
>
> Colm.
>
> On Tue, Nov 23, 2021 at 1:25 PM Rebecca Searls <rs...@redhat.com> wrote:
> >
> > Wildfly components requires a jakarta namesapce version of
> org.apache.santuario:xmlsec.
> > I have created such a version. I would like to submit a PR for it.
>
>
Re: A jakarta namespace version
Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi Rebecca,
I believe we have an existing PR -
https://github.com/apache/santuario-xml-security-java/pull/63
Or are you referring to something else?
Colm.
On Tue, Nov 23, 2021 at 1:25 PM Rebecca Searls <rs...@redhat.com> wrote:
>
> Wildfly components requires a jakarta namesapce version of org.apache.santuario:xmlsec.
> I have created such a version. I would like to submit a PR for it.