[JBoss JIRA] (WFLY-10320) Upgrade artemis from 1.5.x to 2.x.x
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-10320?page=com.atlassian.jira.plugin... ]
Jeff Mesnil commented on WFLY-10320:
------------------------------------
Artemis 2.5.0 will not be integrated as it had regression compared to Artemis 1.5.5
The current plan is to integrate Artemis 2.6.0 after WildFly 13.0.0.Final
> Upgrade artemis from 1.5.x to 2.x.x
> -----------------------------------
>
> Key: WFLY-10320
> URL: https://issues.jboss.org/browse/WFLY-10320
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JMS
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: feature-branch-blocker
> Fix For: 14.0.0.CR1
>
>
> As the summary of this Jira hints, this is an umbrella Jira for tracking all issues related to the upgrade of Artemis component from version 1.x to 2.x.
> The issues were identified after running tests against following pull request - https://github.com/wildfly/wildfly/pull/10641
> This PR integrates Artemis 2.4.0 in WildFly master branch
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10048) Deploying of malformed MDB should be allowed, but infractions should be reported as warnings
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFLY-10048?page=com.atlassian.jira.plugin... ]
Romain Pelisse updated WFLY-10048:
----------------------------------
Summary: Deploying of malformed MDB should be allowed, but infractions should be reported as warnings (was: Deploying of malformed MDB should be reported as warnings)
> Deploying of malformed MDB should be allowed, but infractions should be reported as warnings
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-10048
> URL: https://issues.jboss.org/browse/WFLY-10048
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 12.0.0.Final
> Reporter: Romain Pelisse
> Assignee: Romain Pelisse
> Fix For: 13.0.0.Beta1
>
>
> When a deployment containing malformed MDB is deployed to EAP server, the deploy operation passes. There should be a check at deploy time that MDBs meet all requirements and if there are some issues, the deploy operation should fail.
> Examples of malformed MDBs:
> class is marked as final
> onMessage method is marked as final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10048) Deploying of malformed MDB should be reported as warnings
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFLY-10048?page=com.atlassian.jira.plugin... ]
Romain Pelisse updated WFLY-10048:
----------------------------------
Summary: Deploying of malformed MDB should be reported as warnings (was: Deploying of malformed MDB should fail)
> Deploying of malformed MDB should be reported as warnings
> ---------------------------------------------------------
>
> Key: WFLY-10048
> URL: https://issues.jboss.org/browse/WFLY-10048
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 12.0.0.Final
> Reporter: Romain Pelisse
> Assignee: Romain Pelisse
> Fix For: 13.0.0.Beta1
>
>
> When a deployment containing malformed MDB is deployed to EAP server, the deploy operation passes. There should be a check at deploy time that MDBs meet all requirements and if there are some issues, the deploy operation should fail.
> Examples of malformed MDBs:
> class is marked as final
> onMessage method is marked as final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3816) ExtensionIndexService throws NPE while reading extensions on the IBM jdk
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3816?page=com.atlassian.jira.plugi... ]
Petr Kremensky commented on WFCORE-3816:
----------------------------------------
Hi [~swd847]
{noformat}
$ for JAR in `find /usr/lib/java/ibm-java-8.0-5.11/jre/lib/ext/ -name "*.jar" ` ; do unzip -l $JAR | grep MANIFEST &> /dev/null || echo $JAR ; done
/usr/lib/java/ibm-java-8.0-5.11/jre/lib/ext/traceformat.jar
/usr/lib/java/ibm-java-8.0-5.11/jre/lib/ext/dtfj.jar
/usr/lib/java/ibm-java-8.0-5.11/jre/lib/ext/dtfjview.jar
{noformat}
I've updated the MR to check for null instead, thanks.
> ExtensionIndexService throws NPE while reading extensions on the IBM jdk
> ------------------------------------------------------------------------
>
> Key: WFCORE-3816
> URL: https://issues.jboss.org/browse/WFCORE-3816
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 5.0.0.Alpha7
> Environment: {noformat}
> java version "1.8.0_161"
> Java(TM) SE Runtime Environment (build 8.0.5.11 - pxa6480sr5fp11-20180326_01(SR5 FP11))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180309_380776 (JIT enabled, AOT enabled)
> OpenJ9 - 49fcaf39
> OMR - 5cbbadf
> IBM - 4453dac)
> JCL - 20180319_01 based on Oracle jdk8u161-b12
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Petr Kremensky
>
> https://github.com/wildfly/wildfly-core/blob/5.0.0.Alpha7/server/src/main... reads extensions from jars manifest like:
> {code:java}
> File jar = new File(<jar>)
> final JarFile jarFile = new JarFile(jar);
> final Manifest manifest = jarFile.getManifest();
> final Attributes mainAttributes = manifest.getMainAttributes();
> ...
> {code}
> The latest [IBM jdk 8.0-5.11|https://developer.ibm.com/javasdk/downloads/sdk8/] (and possible some of previous releases) contains some jars \[1\] where {{manifest.getMainAttributes();}} throws NPE, causing deploy operation of archive with Extension-List to fail, see WFLY-10349.
> \[1\]
> ibm-java-8.0-5.11/jre/lib/ext/traceformat.jar: java.lang.NullPointerException
> ibm-java-8.0-5.11/jre/lib/ext/dtfj.jar: java.lang.NullPointerException
> ibm-java-8.0-5.11/jre/lib/ext/dtfjview.jar: java.lang.NullPointerException
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2543) "?" doesn't work with multi-conditions in decision table
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2543?page=com.atlassian.jira.plugi... ]
Tibor Zimányi updated DROOLS-2543:
----------------------------------
Description:
When having multivalue cell in DMN decision table with this values: "? > 10, 90", FEEL compilation fails with the following output [1]. This multivalue works when it is closed in brackets like this: "(? > 10), 90" or when the condition order is switched like this: "90, ? > 10". I will provide a PR with a reproducer.
[1] https://gist.github.com/baldimir/d6f51198696e4f2b84d3eb0aaf2a9815
was:
When having multivalue cell in DMN decision table with this values: "? > 10, 90", FEEL compilation fails with the following output [1]. This multivalue works when it is closed in brackets like this: "(? > 10), 90". I will provide a PR with a reproducer.
[1] https://gist.github.com/baldimir/d6f51198696e4f2b84d3eb0aaf2a9815
Summary: "?" doesn't work with multi-conditions in decision table (was: "?" doesn't work with multi-conditions in decision table without brackets)
> "?" doesn't work with multi-conditions in decision table
> --------------------------------------------------------
>
> Key: DROOLS-2543
> URL: https://issues.jboss.org/browse/DROOLS-2543
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.7.0.Final
> Reporter: Tibor Zimányi
> Assignee: Edson Tirelli
>
> When having multivalue cell in DMN decision table with this values: "? > 10, 90", FEEL compilation fails with the following output [1]. This multivalue works when it is closed in brackets like this: "(? > 10), 90" or when the condition order is switched like this: "90, ? > 10". I will provide a PR with a reproducer.
> [1] https://gist.github.com/baldimir/d6f51198696e4f2b84d3eb0aaf2a9815
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months