[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
[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
[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
[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