> Am I missing something or is there no jakarta alternative for
artemis-cdi-client yet?

You're not missing anything. There is currently no Jakarta alternative for
the artemis-cdi-client module.

> If so, is there something planned in this regard...

There is nothing currently planned as far as I'm aware. I wasn't even aware
that it used javax classes and therefore needed a Jakarta alternative. That
said, it would be relatively simple to create a Jakarta alternative as has
been done for other modules.

That said, I was thinking of deprecating this module and removing it in the
impending 3.0 release because there's never been any indication that folks
are actually using it. I think you're the first person to ever ask a
question about it. Can you elaborate on your use-case and if there would be
any alternatives if this module was removed in the future? I certainly
don't mind keeping it around if folks are using it and there are no
compelling alternatives.


Justin

On Thu, Jan 2, 2025 at 5:21 AM Christian Ortlepp <
christian.ortl...@hypergene.com> wrote:

> Hi,
>
> I am currently trying to migrate a project which uses
> artemis-jms-client, artemis-jms-server, artemis-jdbc-store and
> artemis-cdi-client from javax to jakarta. While there are jakarta
> replacements for the client and server and the jdbc-store dependency
> doesn't seem to use javax/jakarta, artemis-cdi-client does depend on
> some javax libraries (inject and annotations) and I could not find any
> replacement for it.
>
>
> Am I missing something or is there no jakarta alternative for
> artemis-cdi-client yet? If so, is there something planned in this
> regard, do you want to do the upgrade in-place or create a new artifact
> similarly to artemis client/server?
>
>
> Best Regards,
>
> Christian Ortlepp
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
> For additional commands, e-mail: users-h...@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
>
>

Reply via email to