October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12535) Container does not pass the beanManager when creating eclipselink EntityManagerFactory

by charles ghislain (Jira)

[ https://issues.jboss.org/browse/WFLY-12535?page=com.atlassian.jira.plugin... ] charles ghislain updated WFLY-12535: ------------------------------------ Attachment: server.log > Container does not pass the beanManager when creating eclipselink EntityManagerFactory > -------------------------------------------------------------------------------------- > > Key: WFLY-12535 > URL: https://issues.jboss.org/browse/WFLY-12535 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 16.0.0.Final > Reporter: charles ghislain > Assignee: Scott Marlow > Priority: Major > Attachments: server.log, server.log > > > When creating the entity manager factory for eclipseliknk using `javax.persistence.spi.PersistenceProvider#createContainerEntityManagerFactory`, wildfly does not pass the properties required by the jee8 spec, as specified in the javadoc of this method: > {code} > If a Bean Validation provider is present in the classpath, the container must pass the ValidatorFactory instance in the map with the key "javax.persistence.validation.factory". If the containing archive is a bean archive, the container must pass the BeanManager instance in the map with the key "javax.persistence.bean.manager" > {code} > Debugging the eclipselink implementation of this method, `org.eclipse.persistence.jpa.PersistenceProvider#createContainerEntityManagerFactory`, the properties set by the container contains the following 3 entries: > {code:java} > eclipselink.logging.logger -> org.jipijapa.eclipselink.JBossLogger > eclipselink.archive.factory -> org.jipijapa.eclipselink.JBossArchiveFactoryImpl > eclipselink.target-server -> org.jipijapa.eclipselink.WildFlyServerPlatform > {code} > I think this prevents CDI injection in custom ConstraintValidators, as mentionned on an old eclipselink thread: https://www.eclipse.org/lists/eclipselink-users/msg08503.html. > I have a `ConstraintValidator` with an `@Inject`ed EJB, but when validation is triggered on the call to `javax.persistence.EntityManager#merge`, the injected field is null. > The wildfly installation has been updated to include eclipselink as per documentation: > the org.eclipse.persistence module has been updated to include the eclipselink jar with the following descriptor: > {code:java} > <module xmlns="urn:jboss:module:1.1" name="org.eclipse.persistence"> > <resources> >  > <resource-root path="eclipselink.jar"> > <filter> > <exclude path="javax/**" /> > </filter> > </resource-root> > </resources> > <dependencies> > <module name="asm.asm"/> > <module name="javax.api"/> > <module name="javax.annotation.api"/> > <module name="javax.enterprise.api"/> > <module name="javax.persistence.api"/> > <module name="javax.transaction.api"/> > <module name="javax.validation.api"/> > <module name="javax.xml.bind.api"/> > <module name="javax.ws.rs.api"/> > <module name="org.antlr"/> > <module name="org.apache.commons.collections"/> > <module name="org.dom4j"/> > <module name="org.jboss.as.jpa.spi"/> > <module name="org.jboss.logging"/> > <module name="org.jboss.vfs"/> > </dependencies> > </module> > {code} > The persistence unit provider has been set to `org.eclipse.persistence.jpa.PersistenceProvider` in the persistence.xml file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12535) Container does not pass the beanManager when creating eclipselink EntityManagerFactory

by charles ghislain (Jira)

[ https://issues.jboss.org/browse/WFLY-12535?page=com.atlassian.jira.plugin... ] charles ghislain updated WFLY-12535: ------------------------------------ Attachment: server.log > Container does not pass the beanManager when creating eclipselink EntityManagerFactory > -------------------------------------------------------------------------------------- > > Key: WFLY-12535 > URL: https://issues.jboss.org/browse/WFLY-12535 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 16.0.0.Final > Reporter: charles ghislain > Assignee: Scott Marlow > Priority: Major > Attachments: server.log > > > When creating the entity manager factory for eclipseliknk using `javax.persistence.spi.PersistenceProvider#createContainerEntityManagerFactory`, wildfly does not pass the properties required by the jee8 spec, as specified in the javadoc of this method: > {code} > If a Bean Validation provider is present in the classpath, the container must pass the ValidatorFactory instance in the map with the key "javax.persistence.validation.factory". If the containing archive is a bean archive, the container must pass the BeanManager instance in the map with the key "javax.persistence.bean.manager" > {code} > Debugging the eclipselink implementation of this method, `org.eclipse.persistence.jpa.PersistenceProvider#createContainerEntityManagerFactory`, the properties set by the container contains the following 3 entries: > {code:java} > eclipselink.logging.logger -> org.jipijapa.eclipselink.JBossLogger > eclipselink.archive.factory -> org.jipijapa.eclipselink.JBossArchiveFactoryImpl > eclipselink.target-server -> org.jipijapa.eclipselink.WildFlyServerPlatform > {code} > I think this prevents CDI injection in custom ConstraintValidators, as mentionned on an old eclipselink thread: https://www.eclipse.org/lists/eclipselink-users/msg08503.html. > I have a `ConstraintValidator` with an `@Inject`ed EJB, but when validation is triggered on the call to `javax.persistence.EntityManager#merge`, the injected field is null. > The wildfly installation has been updated to include eclipselink as per documentation: > the org.eclipse.persistence module has been updated to include the eclipselink jar with the following descriptor: > {code:java} > <module xmlns="urn:jboss:module:1.1" name="org.eclipse.persistence"> > <resources> >  > <resource-root path="eclipselink.jar"> > <filter> > <exclude path="javax/**" /> > </filter> > </resource-root> > </resources> > <dependencies> > <module name="asm.asm"/> > <module name="javax.api"/> > <module name="javax.annotation.api"/> > <module name="javax.enterprise.api"/> > <module name="javax.persistence.api"/> > <module name="javax.transaction.api"/> > <module name="javax.validation.api"/> > <module name="javax.xml.bind.api"/> > <module name="javax.ws.rs.api"/> > <module name="org.antlr"/> > <module name="org.apache.commons.collections"/> > <module name="org.dom4j"/> > <module name="org.jboss.as.jpa.spi"/> > <module name="org.jboss.logging"/> > <module name="org.jboss.vfs"/> > </dependencies> > </module> > {code} > The persistence unit provider has been set to `org.eclipse.persistence.jpa.PersistenceProvider` in the persistence.xml file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4619) Hard to figure out how to select what type of expression the DMN decision will be

by Alexandre Bakos (Jira)

[ https://issues.jboss.org/browse/DROOLS-4619?page=com.atlassian.jira.plugi... ] Alexandre Bakos reassigned DROOLS-4619: --------------------------------------- Assignee: Elizabeth Clayton (was: Mario Fusco) > Hard to figure out how to select what type of expression the DMN decision will be > --------------------------------------------------------------------------------- > > Key: DROOLS-4619 > URL: https://issues.jboss.org/browse/DROOLS-4619 > Project: Drools > Issue Type: Enhancement > Reporter: Alexandre Bakos > Assignee: Elizabeth Clayton > Priority: Major > Attachments: Screen Shot 2019-10-08 at 4.42.38 PM.png > > > I had a hard time to figure out that I had to click the cell to select what type of expression I'd like, that in my case was a decision table. > I right-clicked, I double-clicked the "Decision-1" header and took me a while to just click the cell that says: Select expression. > A very quick win for a very short time would change the message to something like: "click here to select expression"... but likely that a better interaction is needed to replace the current empty cell. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4619) Hard to figure out how to select what type of expression the DMN decision will be

by Alexandre Bakos (Jira)

[ https://issues.jboss.org/browse/DROOLS-4619?page=com.atlassian.jira.plugi... ] Alexandre Bakos updated DROOLS-4619: ------------------------------------ Attachment: Screen Shot 2019-10-08 at 4.42.38 PM.png > Hard to figure out how to select what type of expression the DMN decision will be > --------------------------------------------------------------------------------- > > Key: DROOLS-4619 > URL: https://issues.jboss.org/browse/DROOLS-4619 > Project: Drools > Issue Type: Enhancement > Reporter: Alexandre Bakos > Assignee: Elizabeth Clayton > Priority: Major > Attachments: Screen Shot 2019-10-08 at 4.42.38 PM.png > > > I had a hard time to figure out that I had to click the cell to select what type of expression I'd like, that in my case was a decision table. > I right-clicked, I double-clicked the "Decision-1" header and took me a while to just click the cell that says: Select expression. > A very quick win for a very short time would change the message to something like: "click here to select expression"... but likely that a better interaction is needed to replace the current empty cell. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4619) Hard to figure out how to select what type of expression the DMN decision will be

by Alexandre Bakos (Jira)

Alexandre Bakos created DROOLS-4619: --------------------------------------- Summary: Hard to figure out how to select what type of expression the DMN decision will be Key: DROOLS-4619 URL: https://issues.jboss.org/browse/DROOLS-4619 Project: Drools Issue Type: Enhancement Reporter: Alexandre Bakos Assignee: Mario Fusco I had a hard time to figure out that I had to click the cell to select what type of expression I'd like, that in my case was a decision table. I right-clicked, I double-clicked the "Decision-1" header and took me a while to just click the cell that says: Select expression. A very quick win for a very short time would change the message to something like: "click here to select expression"... but likely that a better interaction is needed to replace the current empty cell. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12535) Container does not pass the beanManager when creating eclipselink EntityManagerFactory

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12535?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-12535: ------------------------------------- possible workaround, update persistence.xml to set jboss.as.jpa.classtransformer to false: {code} <property name="jboss.as.jpa.classtransformer" value="false"/> {code} > Container does not pass the beanManager when creating eclipselink EntityManagerFactory > -------------------------------------------------------------------------------------- > > Key: WFLY-12535 > URL: https://issues.jboss.org/browse/WFLY-12535 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 16.0.0.Final > Reporter: charles ghislain > Assignee: Scott Marlow > Priority: Major > > When creating the entity manager factory for eclipseliknk using `javax.persistence.spi.PersistenceProvider#createContainerEntityManagerFactory`, wildfly does not pass the properties required by the jee8 spec, as specified in the javadoc of this method: > {code} > If a Bean Validation provider is present in the classpath, the container must pass the ValidatorFactory instance in the map with the key "javax.persistence.validation.factory". If the containing archive is a bean archive, the container must pass the BeanManager instance in the map with the key "javax.persistence.bean.manager" > {code} > Debugging the eclipselink implementation of this method, `org.eclipse.persistence.jpa.PersistenceProvider#createContainerEntityManagerFactory`, the properties set by the container contains the following 3 entries: > {code:java} > eclipselink.logging.logger -> org.jipijapa.eclipselink.JBossLogger > eclipselink.archive.factory -> org.jipijapa.eclipselink.JBossArchiveFactoryImpl > eclipselink.target-server -> org.jipijapa.eclipselink.WildFlyServerPlatform > {code} > I think this prevents CDI injection in custom ConstraintValidators, as mentionned on an old eclipselink thread: https://www.eclipse.org/lists/eclipselink-users/msg08503.html. > I have a `ConstraintValidator` with an `@Inject`ed EJB, but when validation is triggered on the call to `javax.persistence.EntityManager#merge`, the injected field is null. > The wildfly installation has been updated to include eclipselink as per documentation: > the org.eclipse.persistence module has been updated to include the eclipselink jar with the following descriptor: > {code:java} > <module xmlns="urn:jboss:module:1.1" name="org.eclipse.persistence"> > <resources> >  > <resource-root path="eclipselink.jar"> > <filter> > <exclude path="javax/**" /> > </filter> > </resource-root> > </resources> > <dependencies> > <module name="asm.asm"/> > <module name="javax.api"/> > <module name="javax.annotation.api"/> > <module name="javax.enterprise.api"/> > <module name="javax.persistence.api"/> > <module name="javax.transaction.api"/> > <module name="javax.validation.api"/> > <module name="javax.xml.bind.api"/> > <module name="javax.ws.rs.api"/> > <module name="org.antlr"/> > <module name="org.apache.commons.collections"/> > <module name="org.dom4j"/> > <module name="org.jboss.as.jpa.spi"/> > <module name="org.jboss.logging"/> > <module name="org.jboss.vfs"/> > </dependencies> > </module> > {code} > The persistence unit provider has been set to `org.eclipse.persistence.jpa.PersistenceProvider` in the persistence.xml file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-970) Create Jenkins Job for Quay Operator Source

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-970: --------------------------------------------- Summary: Create Jenkins Job for Quay Operator Source Key: SWSQE-970 URL: https://issues.jboss.org/browse/SWSQE-970 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo We need to deploy from different operator sources for OLM. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-969) Create OLM Job for Production Images

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-969: --------------------------------------------- Summary: Create OLM Job for Production Images Key: SWSQE-969 URL: https://issues.jboss.org/browse/SWSQE-969 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-969) Create OLM Job for Production Images

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-969?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-969: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo > Create OLM Job for Production Images > ------------------------------------ > > Key: SWSQE-969 > URL: https://issues.jboss.org/browse/SWSQE-969 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-950) Separate Istio bookinfo from Maistra Bookinfo

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-950?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo closed SWSQE-950. ----------------------------------------- Resolution: Done > Separate Istio bookinfo from Maistra Bookinfo > --------------------------------------------- > > Key: SWSQE-950 > URL: https://issues.jboss.org/browse/SWSQE-950 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Today, > We handling Maistra bookinfo and Istio bookinfo as one thing but that needs to change to accomodate the changes istio is doing upstream -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 October 2019