You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2018/02/22 16:02:00 UTC

[jira] [Comment Edited] (KARAF-5627) Upgrade to PAX-JMS 0.2.0

    [ https://issues.apache.org/jira/browse/KARAF-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372980#comment-16372980 ] 

Guillaume Nodet edited comment on KARAF-5627 at 2/22/18 4:01 PM:
-----------------------------------------------------------------

The Pax-JMS 0.2.0 features actually have some problems because a library required at runtime is not installed.  That's because a package is flagged optional (and should be) but the code has mandatory requirements on it right now (easy to break).  For those reasons, we should defer the upgrade until a new release comes up with a fix.

In addition, the pooling stuff that has been added with https://github.com/ops4j/org.ops4j.pax.jms/pull/3 is not at the correct level, as the pooling should be done when exposing the {{ConnectionFactory}} built using the {{ConnectionFactoryFactory}}, not in the {{ConnectionFactoryFactory}} itself.


was (Author: gnt):
The Pax-JMS 0.2.0 features actually have some problems because a library required at runtime is not installed.  That's because a package is flagged optional (and should be) but the code has mandatory requirements on it right now (easy to break).  For those reasons, we should defer the upgrade until a new release comes up with a fix.

> Upgrade to PAX-JMS 0.2.0
> ------------------------
>
>                 Key: KARAF-5627
>                 URL: https://issues.apache.org/jira/browse/KARAF-5627
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-jms
>            Reporter: John Poth
>            Priority: Major
>
> Upgrade PAX-JMS to [0.2.0|https://github.com/ops4j/org.ops4j.pax.jms/releases/tag/jms-0.2.0]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)