June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12239) Wildfly 13 to wildfly 17 json serialization

by Alfredo Marchini (Jira)

[ https://issues.jboss.org/browse/WFLY-12239?page=com.atlassian.jira.plugin... ] Alfredo Marchini closed WFLY-12239. ----------------------------------- Resolution: Rejected Is not a bug. Java EE 8 uses json-b not Jackson > Wildfly 13 to wildfly 17 json serialization > ------------------------------------------- > > Key: WFLY-12239 > URL: https://issues.jboss.org/browse/WFLY-12239 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 17.0.0.Final > Environment: I developear an EAR, with an EJB module and a Web module, that works perfectly on wildfly 13. > I am trying to migrate to version 17.0.0.Final > Reporter: Alfredo Marchini > Assignee: Jim Ma > Priority: Major > Labels: jackson, json, serialization, yasson > Fix For: 13.0.0.Final > > > I have problem in serialization of Pojo to JSON. > I have a Provider that impelments ContextResolver<ObjectMapper>. > That constructor is called regulary on deploy, but the method getContext is never called, so my custom serialization registration is never called. > What's changed at json serialization level between 13 and 17? > If I copy yasson-1.0.1 from wildfly 13 and swap it with yasson-1.0.3 (wildfly 17) everything works fine. > Thank you very much > Regards -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12239) Wildfly 13 to wildfly 17 json serialization

by Alfredo Marchini (Jira)

[ https://issues.jboss.org/browse/WFLY-12239?page=com.atlassian.jira.plugin... ] Alfredo Marchini commented on WFLY-12239: ----------------------------------------- It's not a bug, it's mine problem. Sorry > Wildfly 13 to wildfly 17 json serialization > ------------------------------------------- > > Key: WFLY-12239 > URL: https://issues.jboss.org/browse/WFLY-12239 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 17.0.0.Final > Environment: I developear an EAR, with an EJB module and a Web module, that works perfectly on wildfly 13. > I am trying to migrate to version 17.0.0.Final > Reporter: Alfredo Marchini > Assignee: Jim Ma > Priority: Major > Labels: jackson, json, serialization, yasson > Fix For: 13.0.0.Final > > > I have problem in serialization of Pojo to JSON. > I have a Provider that impelments ContextResolver<ObjectMapper>. > That constructor is called regulary on deploy, but the method getContext is never called, so my custom serialization registration is never called. > What's changed at json serialization level between 13 and 17? > If I copy yasson-1.0.1 from wildfly 13 and swap it with yasson-1.0.3 (wildfly 17) everything works fine. > Thank you very much > Regards -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2726) Drools core doesn't run on AWS lambda

by Sebastian Duque (Jira)

[ https://issues.jboss.org/browse/DROOLS-2726?page=com.atlassian.jira.plugi... ] Sebastian Duque commented on DROOLS-2726: ----------------------------------------- Any news about this? > Drools core doesn't run on AWS lambda > ------------------------------------- > > Key: DROOLS-2726 > URL: https://issues.jboss.org/browse/DROOLS-2726 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Adeela Huma > Assignee: Mario Fusco > Priority: Major > > When running drools on AWS lambda they get this exception apparently: > {code} > java.lang.ExceptionInInitializerError: > java.lang.ExceptionInInitializerError > java.lang.ExceptionInInitializerError > at org.kie.api.internal.utils.ServiceRegistry.getInstance(ServiceRegistry.java:27) > ... > Caused by: java.lang.RuntimeException: Child services [org.kie.api.internal.assembler.KieAssemblers] have no parent > at org.kie.api.internal.utils.ServiceDiscoveryImpl.buildMap(ServiceDiscoveryImpl.java:191) > at org.kie.api.internal.utils.ServiceDiscoveryImpl.getServices(ServiceDiscoveryImpl.java:97) > ... > {code} > Reporting the bug from stack overflow discussion: > https://stackoverflow.com/questions/51273121/optaplanner-with-aws-lambda -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3967) All Maven modules in all Kogito-related Maven repos need to be converted to JUnit 5

by Lukáš Petrovický (Jira)

[ https://issues.jboss.org/browse/DROOLS-3967?page=com.atlassian.jira.plugi... ] Lukáš Petrovický updated DROOLS-3967: ------------------------------------- Summary: All Maven modules in all Kogito-related Maven repos need to be converted to JUnit 5 (was: All Maven modules in all Submarine-related Maven repos need to be converted to JUnit 5) > All Maven modules in all Kogito-related Maven repos need to be converted to JUnit 5 > ----------------------------------------------------------------------------------- > > Key: DROOLS-3967 > URL: https://issues.jboss.org/browse/DROOLS-3967 > Project: Drools > Issue Type: Epic > Reporter: Lukáš Petrovický > Assignee: Lukáš Petrovický > Priority: Major > Labels: kogito > Fix For: 8.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3967) All Maven modules in all Kogito-related Maven repos need to be converted to JUnit 5

by Lukáš Petrovický (Jira)

[ https://issues.jboss.org/browse/DROOLS-3967?page=com.atlassian.jira.plugi... ] Lukáš Petrovický updated DROOLS-3967: ------------------------------------- Labels: kogito (was: submarine) > All Maven modules in all Kogito-related Maven repos need to be converted to JUnit 5 > ----------------------------------------------------------------------------------- > > Key: DROOLS-3967 > URL: https://issues.jboss.org/browse/DROOLS-3967 > Project: Drools > Issue Type: Epic > Reporter: Lukáš Petrovický > Assignee: Lukáš Petrovický > Priority: Major > Labels: kogito > Fix For: 8.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4271) JUnit 5: Migrate Runtimes > Codegen to JUnit 5

by Lukáš Petrovický (Jira)

Lukáš Petrovický created DROOLS-4271: ---------------------------------------- Summary: JUnit 5: Migrate Runtimes > Codegen to JUnit 5 Key: DROOLS-4271 URL: https://issues.jboss.org/browse/DROOLS-4271 Project: Drools Issue Type: Task Reporter: Lukáš Petrovický Assignee: Mario Fusco Fix For: 8.0.0.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4554) Enabled the embedded JBoss Log Manager tests for the IBM JVM

by James Perkins (Jira)

James Perkins created WFCORE-4554: ------------------------------------- Summary: Enabled the embedded JBoss Log Manager tests for the IBM JVM Key: WFCORE-4554 URL: https://issues.jboss.org/browse/WFCORE-4554 Project: WildFly Core Issue Type: Task Components: Embedded, Logging, Test Suite Reporter: James Perkins Assignee: James Perkins The JBoss Log Manager embedded tests were disabled for the IBM JVM. This was due to the IBM JDK initializing the log manager too early. However with the fix for WFCORE-4553 with a small workaround we can now enabled these tests for the IBM JVM. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12205) Update jboss-ejb-client to 4.0.19

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12205?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-12205. ------------------------------------- Resolution: Out of Date WFLY-12200 moved to 4.0.20. > Update jboss-ejb-client to 4.0.19 > --------------------------------- > > Key: WFLY-12205 > URL: https://issues.jboss.org/browse/WFLY-12205 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Affects Versions: 17.0.0.Final > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > Fix For: 18.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12248) Align jgroups stacks in example configurations with default ha configuration

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12248?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12248: ------------------------------------ Fix Version/s: 17.0.1.Final > Align jgroups stacks in example configurations with default ha configuration > ---------------------------------------------------------------------------- > > Key: WFLY-12248 > URL: https://issues.jboss.org/browse/WFLY-12248 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 17.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-804) Kiali Release Notifier Jenkins Job Is Broken

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-804: ------------------------------------- Summary: Kiali Release Notifier Jenkins Job Is Broken Key: SWSQE-804 URL: https://issues.jboss.org/browse/SWSQE-804 Project: Kiali QE Issue Type: QE Task Reporter: Matthew Mahoney Assignee: Matthew Mahoney kiali-release-notifier is using the incorrect container repo (should be using quay.io. and not docker.io). Also, the Kiali version / tag is in correct. Reference job: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/kiali-workflow/j... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2019