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 updated WFLY-12239: ------------------------------------ Issue Type: Bug (was: Feature Request) > 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 updated WFLY-12239: ------------------------------------ Fix Version/s: 13.0.0.Final > 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)

Alfredo Marchini created WFLY-12239: --------------------------------------- Summary: Wildfly 13 to wildfly 17 json serialization Key: WFLY-12239 URL: https://issues.jboss.org/browse/WFLY-12239 Project: WildFly Issue Type: Feature Request 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 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] (WFCORE-944) truststore path is ignored if provider is not JKS

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-944?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-944: ------------------------------------ Fix Version/s: 10.0.0.Beta1 > truststore path is ignored if provider is not JKS > ------------------------------------------------- > > Key: WFCORE-944 > URL: https://issues.jboss.org/browse/WFCORE-944 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Arto Huusko > Priority: Major > Fix For: 10.0.0.Beta1 > > > truststore configuration ignores the path and relative-to parameters if the truststore provider is anything else than JKS. > This works as documented, but it is not correct. There can be and are truststore implementations that need to load parameters or whatever data from a file, and the current implementation prevents these truststore providers from working. > We have a custom truststore that is loaded from database, and database access parameters are read from a properties file. When trying to use this with Wildfly 9, the keystore engineLoad parameter is passed in as null, even though path and relative-to are configured. > Even standard java supports PKCS12 truststores, where the same problem would occur. > So I would suggest that > - if provider is JKS, path is mandatory > - if provider is not JKS, but path is specified, it is passed to the provider -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-944) truststore path is ignored if provider is not JKS

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-944?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-944: ------------------------------------ Issue Type: Bug (was: Feature Request) > truststore path is ignored if provider is not JKS > ------------------------------------------------- > > Key: WFCORE-944 > URL: https://issues.jboss.org/browse/WFCORE-944 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Arto Huusko > Priority: Major > > truststore configuration ignores the path and relative-to parameters if the truststore provider is anything else than JKS. > This works as documented, but it is not correct. There can be and are truststore implementations that need to load parameters or whatever data from a file, and the current implementation prevents these truststore providers from working. > We have a custom truststore that is loaded from database, and database access parameters are read from a properties file. When trying to use this with Wildfly 9, the keystore engineLoad parameter is passed in as null, even though path and relative-to are configured. > Even standard java supports PKCS12 truststores, where the same problem would occur. > So I would suggest that > - if provider is JKS, path is mandatory > - if provider is not JKS, but path is specified, it is passed to the provider -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3670) module defined with an alias in jboss-deployment-structure.xml with fails to parse when annotations=true

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFCORE-3670?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFCORE-3670: ----------------------------------- WFLY test case https://github.com/soul2zimate/wildfly/commit/438f85a71316838fe2a8815d772... > module defined with an alias in jboss-deployment-structure.xml with fails to parse when annotations=true > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3670 > URL: https://issues.jboss.org/browse/WFCORE-3670 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 4.0.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Major > > This is a follow up to JBEAP-13094. > Having a deployment with jboss-deployment-structure like this: > {code} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <module name="deployment.application-exception-api"> > <resources> > <resource-root path="application-exception-api.jar"/> > </resources> > <dependencies> > <module name="javax.ejb.api" export="true"/> > <module name="javaee.api" export="true"/> > <module name="javax.api" export="true"/> > </dependencies> > <module-alias name="deployment.api" /> > </module> > <sub-deployment name="application-exception-ejb.jar"> > <dependencies> > <module name="deployment.api" annotations="true" meta-inf="export"/> > </dependencies> > </sub-deployment> > </jboss-deployment-structure> > {code} > it fails to parse. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4249) Implement client-side marshalling

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4249?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-4249. ------------------------------------ Resolution: Done > Implement client-side marshalling > --------------------------------- > > Key: DROOLS-4249 > URL: https://issues.jboss.org/browse/DROOLS-4249 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > Implement a protoype for client-side marshalling -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4249) Implement client-side marshalling

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4249: ---------------------------------------- Summary: Implement client-side marshalling Key: DROOLS-4249 URL: https://issues.jboss.org/browse/DROOLS-4249 Project: Drools Issue Type: Sub-task Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Implement a protoype for client-side marshalling -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4108) Improve Test Scenario with DMN model with only inputs/decisions

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4108?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4108: ---------------------------------- Sprint: 2019 Week 26-28 > Improve Test Scenario with DMN model with only inputs/decisions > ---------------------------------------------------------------- > > Key: DROOLS-4108 > URL: https://issues.jboss.org/browse/DROOLS-4108 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > When user create a Test Scenario based on a DMN model with only inputs or only decisions the generated template contains only GIVEN (when only inputs) or EXPECT (when only decisions) without the possibility to add a column of the other type -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4247) DMN optimize DT evaluation

by Martin Weiler (Jira)

Martin Weiler created DROOLS-4247: ------------------------------------- Summary: DMN optimize DT evaluation Key: DROOLS-4247 URL: https://issues.jboss.org/browse/DROOLS-4247 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Martin Weiler Assignee: Matteo Mortari -- 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