May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3872) Upgrade to WildFly Galleon plugins 1.0.0.CR10 and fork embedded in the build

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3872?page=com.atlassian.jira.plugi... ] Alexey Loubyansky updated WFCORE-3872: -------------------------------------- Summary: Upgrade to WildFly Galleon plugins 1.0.0.CR10 and fork embedded in the build (was: Upgrade to WildFly Galleon plugins 1.0.0.CR9 and fork embedded in the build) > Upgrade to WildFly Galleon plugins 1.0.0.CR10 and fork embedded in the build > ---------------------------------------------------------------------------- > > Key: WFCORE-3872 > URL: https://issues.jboss.org/browse/WFCORE-3872 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > 1.0.0.CR9 significantly reduces the classpath prepared by the plugins to launch the embedded server and also adds an option to execute the embedded in a separate process to avoid FD leaks in jboss-modules. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3872) Upgrade to WildFly Galleon plugins 1.0.0.CR10 and fork embedded in the build

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3872?page=com.atlassian.jira.plugi... ] Alexey Loubyansky updated WFCORE-3872: -------------------------------------- Description: 1.0.0.CR10 significantly reduces the classpath prepared by the plugins to launch the embedded server and also adds an option to execute the embedded in a separate process to avoid FD leaks in jboss-modules. (was: 1.0.0.CR9 significantly reduces the classpath prepared by the plugins to launch the embedded server and also adds an option to execute the embedded in a separate process to avoid FD leaks in jboss-modules.) > Upgrade to WildFly Galleon plugins 1.0.0.CR10 and fork embedded in the build > ---------------------------------------------------------------------------- > > Key: WFCORE-3872 > URL: https://issues.jboss.org/browse/WFCORE-3872 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > 1.0.0.CR10 significantly reduces the classpath prepared by the plugins to launch the embedded server and also adds an option to execute the embedded in a separate process to avoid FD leaks in jboss-modules. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10425) With Hibernate ORM 5.3, protect against NPE in WildFlyCustomRegionFactoryInitiator for non-container-managed JPA deployment

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10425?page=com.atlassian.jira.plugin... ] Scott Marlow reopened WFLY-10425: --------------------------------- > With Hibernate ORM 5.3, protect against NPE in WildFlyCustomRegionFactoryInitiator for non-container-managed JPA deployment > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10425 > URL: https://issues.jboss.org/browse/WFLY-10425 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 13.0.0.Beta1 > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 13.0.0.CR1 > > > WildFlyCustomRegionFactoryInitiator needs to test for jpa_shared_code_mode being null. > {code} > at org.jboss.as.jpa.hibernate5.service.WildFlyCustomRegionFactoryInitiator.resolveRegionFactory(WildFlyCustomRegionFactoryInitiator.java:44) > at org.hibernate.cache.internal.RegionFactoryInitiator.initiateService(RegionFactoryInitiator.java:47) > at org.hibernate.cache.internal.RegionFactoryInitiator.initiateService(RegionFactoryInitiator.java:32) > at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214) > - locked <0x4fcc> (a org.hibernate.boot.registry.internal.StandardServiceRegistryImpl) > at org.hibernate.boot.internal.MetadataBuilderImpl$MetadataBuildingOptionsImpl.<init>(MetadataBuilderImpl.java:688) > at org.hibernate.boot.internal.MetadataBuilderImpl.<init>(MetadataBuilderImpl.java:123) > at org.hibernate.boot.MetadataSources.getMetadataBuilder(MetadataSources.java:136) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<init>(EntityManagerFactoryBuilderImpl.java:213) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<init>(EntityManagerFactoryBuilderImpl.java:169) > at org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:76) > at org.hibernate.jpa.HibernatePersistenceProvider.getEntityManagerFactoryBuilder(HibernatePersistenceProvider.java:179) > at org.hibernate.jpa.HibernatePersistenceProvider.getEntityManagerFactoryBuilderOrNull(HibernatePersistenceProvider.java:127) > at org.hibernate.jpa.HibernatePersistenceProvider.getEntityManagerFactoryBuilderOrNull(HibernatePersistenceProvider.java:69) > at org.hibernate.jpa.HibernatePersistenceProvider.generateSchema(HibernatePersistenceProvider.java:164) > at javax.persistence.Persistence.generateSchema(Persistence.java:114) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1586) Update the testsuite to make use of the utilities for certificate generation instead of using pre-generated CAs and certs

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-1586?page=com.atlassian.jira.plugin.s... ] Farah Juma reassigned ELY-1586: ------------------------------- Assignee: Justin Cook > Update the testsuite to make use of the utilities for certificate generation instead of using pre-generated CAs and certs > -------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1586 > URL: https://issues.jboss.org/browse/ELY-1586 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Farah Juma > Assignee: Justin Cook > > Our testsuite currently makes use of pre-generated CAs and certs. This results in issues when the certificates expire since the testsuite then needs to be updated with newly generated CAs and certs. This task is to update our testsuite to dynamically generate the needed certificates using Elytron's certificate generation utilities (e.g., {{org.wildfly.security.x500.cert.X509CertificateBuilder}}, {{org.wildfly.security.x500.cert.SelfSignedX509CertificateAndSigningKey.builder()}}, etc.). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2561) [DMN Editor] Graph View - Add support for using FEEL built-in data-types

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2561?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2561: --------------------------------------- The type checking is done by the dmn-validator API in the backend. The front end just needs to be able show the error and maybe suggest a fix. > [DMN Editor] Graph View - Add support for using FEEL built-in data-types > ------------------------------------------------------------------------ > > Key: DROOLS-2561 > URL: https://issues.jboss.org/browse/DROOLS-2561 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Fix For: 7.8.0.Final > > > Decision, BKM and InputData can have an "output data-type" selected. > Add support for selecting FEELs built-in types. > h2. PR Acceptance test > For Decision, BKM and InputData > # Check data type can be changed (/) > ## Check built-in data type can be selected > ## Check state after save and reopen > ## Change Selection > ## Check state after save and reopen > # Check data type can be loaded (/) > ## Repeat the scenario above with file not created by RedHat DMN Designer > # Mouse/keyboard operations with select box DROOLS-2583 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2559) Drools 7 KieServices.Factory.get() returns null

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2559?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-2559: ------------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > Drools 7 KieServices.Factory.get() returns null > ----------------------------------------------- > > Key: DROOLS-2559 > URL: https://issues.jboss.org/browse/DROOLS-2559 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.5.0.Final > Environment: JBoss Fuse 6.3.0.redhat-187 > Drools version: 7.5.0.Final-redhat-4 > Reporter: Tom Dalbo > Assignee: Mario Fusco > > It seems that there might be a regression from Drools 6.x. This line in my code worked fine: > {{KieServices ks = KieServices.Factory.get()}} > But now does not. The only thing I did was upgrade these dependencies in my pom.xml (as well as updated my OSGi features to install the right bundles) > org.drools.drools-core > org.drools.drools-compiler > org.kie.kie-api > org.kie.soup.kie-soup-project-datamodel-api > org.kie.soup.kie-soup-commons > org.kie.soup.kie-soup-project-datamodel-commons > Lastly, there have been a few StackOverflows related to this, but none of the answers are overwhelmingly positive: > https://stackoverflow.com/questions/49295671/kieservices-factory-get-retu... > https://stackoverflow.com/questions/47556233/drools-7-4-1-kieservices-fac... > https://groups.google.com/forum/#!topic/jbpm-usage/aD58UTCqu-c -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1287) Update CLIENT_CERT mechanism to use Scope.SSL_SESSION instead of SSLSession

by Justin Cook (JIRA)

[ https://issues.jboss.org/browse/ELY-1287?page=com.atlassian.jira.plugin.s... ] Justin Cook reassigned ELY-1287: -------------------------------- Assignee: (was: Justin Cook) > Update CLIENT_CERT mechanism to use Scope.SSL_SESSION instead of SSLSession > --------------------------------------------------------------------------- > > Key: ELY-1287 > URL: https://issues.jboss.org/browse/ELY-1287 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > > This would mean even if the actual SSLSession is unavailable the integration still has the opportunity to provide a scope that represents the session. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10264) Resteasy JSON provider fails in EE7 module

by Katerina Novotna (JIRA)

[ https://issues.jboss.org/browse/WFLY-10264?page=com.atlassian.jira.plugin... ] Katerina Novotna reopened WFLY-10264: ------------------------------------- The PR https://github.com/wildfly/wildfly/pull/11150/files causes several issues for json tests in Resteasy integration testsuite. See RESTEASY-1911 for the details. > Resteasy JSON provider fails in EE7 module > ------------------------------------------ > > Key: WFLY-10264 > URL: https://issues.jboss.org/browse/WFLY-10264 > Project: WildFly > Issue Type: Bug > Components: REST > Reporter: Stuart Douglas > Assignee: Jim Ma > Priority: Blocker > Fix For: 13.0.0.Beta1 > > > org.jboss.resteasy.plugins.providers.jsonb.AbstractJsonBindingProvider depends on org.eclipse.yasoon classes, however these are not present when in EE7 mode -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10264) Resteasy JSON provider fails in EE7 module

by Katerina Novotna (JIRA)

[ https://issues.jboss.org/browse/WFLY-10264?page=com.atlassian.jira.plugin... ] Katerina Novotna edited comment on WFLY-10264 at 5/23/18 11:51 AM: ------------------------------------------------------------------- The PR https://github.com/wildfly/wildfly/pull/11150 causes several issues for json tests in Resteasy integration testsuite. See RESTEASY-1911 for the details. was (Author: kanovotn): The PR https://github.com/wildfly/wildfly/pull/11150/files causes several issues for json tests in Resteasy integration testsuite. See RESTEASY-1911 for the details. > Resteasy JSON provider fails in EE7 module > ------------------------------------------ > > Key: WFLY-10264 > URL: https://issues.jboss.org/browse/WFLY-10264 > Project: WildFly > Issue Type: Bug > Components: REST > Reporter: Stuart Douglas > Assignee: Jim Ma > Priority: Blocker > Fix For: 13.0.0.Beta1 > > > org.jboss.resteasy.plugins.providers.jsonb.AbstractJsonBindingProvider depends on org.eclipse.yasoon classes, however these are not present when in EE7 mode -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10433) allow JPA apps to disable WildFly JTA platform/2lc initiators for Hibernate ORM 5.3+

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10433?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-10433: -------------------------------- Description: Some applications (e.g. Spring) may not want to use the WF 2lc RegionFactoryInitiator + JtaPlatform classes. To accommodate that need, following persistence unit configuration properties will help: * wildfly.jpa.jtaplatform will default to true but if set to false, the WildFly JtaPlatform initiator for ORM 5.3+ (WildFlyCustomJtaPlatformInitiator), will not control Jta use in the Hibernate persistence unit (or session factory). * wildfly.jpa.regionfactory will default to true but if set to false,the WildFly 2lc cache initiator for ORM (WildFlyCustomRegionFactoryInitiator) will not control 2lc use in the Hibernate persistence unit (or session factory). Instead, the Hibernate ORM 2lc cache initiator will be used. was: Some applications (e.g. Spring) may not want to use the WF 2lc RegionFactoryInitiator + JtaPlatform classes. To accommodate that need, following persistence unit configuration properties will help: * wildfly.jpa.jtaplatform will default to true but if set to false, the WildFly JtaPlatform initiator for ORM 5.3+ (WildFlyCustomJtaPlatformInitiator), will not control Jta use in the Hibernate persistence unit (or session factory). * wildfly.jpa.regionfactory will default to true but if set to false,the WildFly 2lc cache initiator for ORM (WildFlyCustomRegionFactoryInitiator) will not control 2lc use in the Hibernate persistence unit (or session factory). > allow JPA apps to disable WildFly JTA platform/2lc initiators for Hibernate ORM 5.3+ > ------------------------------------------------------------------------------------ > > Key: WFLY-10433 > URL: https://issues.jboss.org/browse/WFLY-10433 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 13.0.0.CR1 > > > Some applications (e.g. Spring) may not want to use the WF 2lc RegionFactoryInitiator + JtaPlatform classes. To accommodate that need, following persistence unit configuration properties will help: > * wildfly.jpa.jtaplatform will default to true but if set to false, the WildFly JtaPlatform initiator for ORM 5.3+ (WildFlyCustomJtaPlatformInitiator), will not control Jta use in the Hibernate persistence unit (or session factory). > * wildfly.jpa.regionfactory will default to true but if set to false,the WildFly 2lc cache initiator for ORM (WildFlyCustomRegionFactoryInitiator) will not control 2lc use in the Hibernate persistence unit (or session factory). Instead, the Hibernate ORM 2lc cache initiator will be used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 May 2018