Re: [messaging-dev] Jakarta Messaging Update

[Enrico Olivelli <eolivelli@xxxxxxxxx>]

I am also a maintainer of another library that implements the JMS
specs and passes the current TCK.
I will be happy to the new TCK when you have a draft ready

Enrico

Il giorno mer 12 lug 2023 alle ore 12:57 Arjan Tijms via messaging-dev
<messaging-dev@xxxxxxxxxxx> ha scritto:
>
> Hi,
>
> Eclipse OpenMQ is also active, and could perhaps be used as well. See https://github.com/eclipse-ee4j/openmq/graphs/contributors
>
> It's already converted to the jakarta namespace, and already runs the TCK.
>
> Kind regards,
> Arjan Tijms
>
>
>
> On Wed, 12 Jul 2023 at 00:22, Matt Pavlovich via messaging-dev <messaging-dev@xxxxxxxxxxx> wrote:
>>
>> Hi Scott-
>>
>> Thanks, I’ll look into that.
>>
>> Matt Pavlovich
>>
>> On Jul 11, 2023, at 3:48 PM, Scott Marlow <smarlow@xxxxxxxxxx> wrote:
>>
>> On the list for EE 11 is to refactor the Standalone Messaging TCK into a separate Maven Module that uses JUnit.  Volunteers to help with the TCK refactoring is very much appreciated if anyone is interested in jumping in on the https://github.com/jakartaee/platform-tck/tree/tckrefactor branch.
>>
>> For running the existing Messaging 3.1 TCK, you might look at the https://github.com/jakartaee/platform-tck/blob/master/docker/jmstck.sh script (nothing to do with Docker by the way) that is used for validating that GlassFish can pass the Messaging TCK.  Perhaps that will help you get started with running the current TCK with Apache Ant.
>>
>> Scott
>>
>>
>>
>> On Tue, Jul 11, 2023 at 2:12 PM Matt Pavlovich via messaging-dev <messaging-dev@xxxxxxxxxxx> wrote:
>>>
>>> @Ivar, @David — good info, thanks.
>>>
>>> I think making a separate maven module that does the download + run is a good approach. For now, we can make it run only via manual CI invocation and then perhaps we run it on a schedule down the road.
>>>
>>> @David-
>>>
>>> Do you have any cycles to dig into adding a Maven module that downloads and starts running it? It looks like there is a jndi component, so we probably need a small wrapper to initialize an in-memory JNDI context.  I can point you to the ActiveMQ xml used previously for JMS spec validation runs.
>>>
>>> Thanks,
>>> Matt Pavlovich
>>>
>>> On Jul 11, 2023, at 1:03 PM, David Blevins <david.blevins@xxxxxxxxx> wrote:
>>>
>>> We (Apache) wouldn’t be able to ship the licensed TCK that Ivar mentions, but running on Apache hardware it is not a legal issue.
>>>
>>> I.e. we can have a Jenkins job on the Apache side that downloads the TCK via curl, sets it up and runs it.
>>>
>>> Warning that there are a few thousand tests and takes a few hours to run.
>>>
>>> -David
>>>
>>>
>>> On Jul 11, 2023, at 10:53 AM, Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>>>
>>> Well, that's complicated :)
>>> I don't know about the Apache rules around this, but this is how it is:
>>>
>>> If you download the TCK bundle from the link I gave you, it is licensed under the Eclipse Foundation TCK Licence (https://www.eclipse.org/legal/tck.php)
>>> This is the bundle you must use if you claim compatibility.
>>>
>>> If you're only going to run it in your CI and not use it for compatibility claims, you can always build it from source, it is then under "Eclipse Public License 2.0 一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception". The complicating factor is that the source for the messaging TCK is still in the Platform TCK source, so I assume extracting it and building it yourself is not trivial. There is an ongoing refactoring effort to extract all TCKs to their own repositories, but this is still ongoing.
>>>
>>> Hope this helps, and didn't confuse you more :)
>>>
>>> Ivar
>>>
>>>
>>>
>>> On Tue, Jul 11, 2023 at 7:35 PM Matt Pavlovich <mattrpav@xxxxxxxxx> wrote:
>>>>
>>>> Hi Ivar-
>>>>
>>>> Thanks! I’ll check it out.
>>>>
>>>> Do you know off hand what is the licensing situation? For example, are we able to include it in the Apache ActiveMQ source tree as a unit test to run in CI?
>>>>
>>>> Thanks,
>>>> Matt Pavlovich
>>>>
>>>> On Jul 11, 2023, at 12:33 PM, Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>>>>
>>>> Hi Matt,
>>>>
>>>> You can download the TCK for Jakarta Messaging 3.1 from this page: https://jakarta.ee/specifications/messaging/3.1/
>>>>
>>>> If you're looking for other versions, they're all listed here: https://jakarta.ee/specifications/messaging/
>>>>
>>>> Ivar
>>>>
>>>> Ivar
>>>>
>>>> On Tue, Jul 11, 2023 at 7:29 PM Matt Pavlovich via messaging-dev <messaging-dev@xxxxxxxxxxx> wrote:
>>>>>
>>>>> David-
>>>>>
>>>>> What is the current situation in terms of getting access to the Jakarta Messaging TCK?
>>>>>
>>>>> That’d be a good next step to get it running against ActiveMQ.
>>>>>
>>>>> Thanks,
>>>>> Matt Pavlovich
>>>>>
>>>>> > On Jul 11, 2023, at 12:07 PM, Matt Pavlovich <mattrpav@xxxxxxxxx> wrote:
>>>>> >
>>>>> > Hi David-
>>>>> >
>>>>> > Sounds good, I agree ActiveMQ is the best place to start =). I am a committer on ActiveMQ and I personally completed most of the JMS 2.0 work and have started the Jakarta conversion =)
>>>>> >
>>>>> > To get you current--
>>>>> >
>>>>> > 1. ActiveMQ 5.18.x ships w/ JMS 2.0 API and most features completed
>>>>> >
>>>>> > 2. ActiveMQ jakarta conversion is about 80% done. We are targeting the fall for a release
>>>>> >
>>>>> > Thanks,
>>>>> > Matt Pavlovich
>>>>> >
>>>>> >
>>>>> >> On Jul 11, 2023, at 11:28 AM, David Blevins <david.blevins@xxxxxxxxx> wrote:
>>>>> >>
>>>>> >> There are definitely no shortage of ideas we could implement.  Both JAXB and JSONB are outlined here:
>>>>> >>
>>>>> >> - https://github.com/jakartaee/messaging-proposals
>>>>> >>
>>>>> >> The real trick is the work on the implementation; the spec can’t go final unless there is an implementation that can pass all the exist and new tck tests.
>>>>> >>
>>>>> >> The implementation I’d want to use for anything I’d work on would be ActiveMQ Classic.  It would likely take a year to get it converted from javax to jakarta, implement all of JMS2.0, and get it passing the existing TCK before we could begin work on new spec features.
>>>>> >>
>>>>> >> I suspect we’re in the same boat on that one, so maybe next steps would be to kick off a thread or two in ActiveMQ.
>>>>> >>
>>>>> >>
>>>>> >> -David
>>>>> >>
>>>>> >>> On Jul 11, 2023, at 9:01 AM, Matt Pavlovich via messaging-dev <messaging-dev@xxxxxxxxxxx> wrote:
>>>>> >>>
>>>>> >>> Hello-
>>>>> >>>
>>>>> >>> There is interest in kicking off discussions for including an update to Jakarta Messaging.
>>>>> >>>
>>>>> >>> Key features to consider:
>>>>> >>>
>>>>> >>> 1. INDIVIUAL ACK mode
>>>>> >>> 2. NO ACK mode
>>>>> >>> 3. Message Conversion API - Ability to convert directly to objects from JSON, JAXB, etc
>>>>> >>>
>>>>> >>> Thanks!
>>>>> >>> Matt Pavlovich
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> _______________________________________________
>>>>> >>> messaging-dev mailing list
>>>>> >>> messaging-dev@xxxxxxxxxxx
>>>>> >>> To unsubscribe from this list, visit https://accounts.eclipse.org
>>>>> >>
>>>>> >
>>>>>
>>>>> _______________________________________________
>>>>> messaging-dev mailing list
>>>>> messaging-dev@xxxxxxxxxxx
>>>>> To unsubscribe from this list, visit https://accounts.eclipse.org
>>>>
>>>>
>>>>
>>>> --
>>>> Ivar Grimstad
>>>> Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration.
>>>>
>>>>
>>>
>>>
>>> --
>>> Ivar Grimstad
>>> Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration.
>>>
>>>
>>>
>>> _______________________________________________
>>> messaging-dev mailing list
>>> messaging-dev@xxxxxxxxxxx
>>> To unsubscribe from this list, visit https://accounts.eclipse.org
>>
>>
>> _______________________________________________
>> messaging-dev mailing list
>> messaging-dev@xxxxxxxxxxx
>> To unsubscribe from this list, visit https://accounts.eclipse.org
>
> _______________________________________________
> messaging-dev mailing list
> messaging-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://accounts.eclipse.org