October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-235) ${JBOSS_HOME}/extensions/postconfigure.sh gets executed at server boot time, does not block

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFWIP-235?page=com.atlassian.jira.plugin.... ] Michal Jurc closed WFWIP-235. ----------------------------- Resolution: Explained [~yersan], [~jdenise]: I am closing this issue as {{Explained}} based on our discussion. This was a test issue. > ${JBOSS_HOME}/extensions/postconfigure.sh gets executed at server boot time, does not block > ------------------------------------------------------------------------------------------- > > Key: WFWIP-235 > URL: https://issues.jboss.org/browse/WFWIP-235 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Michal Jurc > Assignee: Yeray Borges > Priority: Blocker > > {{$\{JBOSS_HOME\}/extensions/postconfigure.sh}} file does not get triggered before the boot of server is started and it does not block the current terminal session. > This is a change compared to previous behaviour. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12614) Duplicated ConstraintViolation message

by Ronald Sigal (Jira)

[ https://issues.jboss.org/browse/WFLY-12614?page=com.atlassian.jira.plugin... ] Ronald Sigal commented on WFLY-12614: ------------------------------------- Well, it's a minor variation of a problem I fixed for https://issues.jboss.org/browse/RESTEASY-1749. One of the differences is that I handled the problem for CDI proxies, and the attached test case runs with EJB proxies. 1. I can fix it, but when I try to turn the test case into an Aquillian test for the RESTEasy testsuite, I'm getting CDI proxies. When I turn off CDI in beans.xml, I'm getting POJOs. [~brian.stansberry], do you know how to force the creation of EJB proxies? 2. Another issue: I'm detecting CDI proxies using Classs.isSynthetic(), but it doesn't work for EJB proxies. I can test for classname.contains("$$$view"), but that seems awfully implementation dependent. Do you know a better way? Thanks. > Duplicated ConstraintViolation message > -------------------------------------- > > Key: WFLY-12614 > URL: https://issues.jboss.org/browse/WFLY-12614 > Project: WildFly > Issue Type: Bug > Components: Bean Validation, REST > Affects Versions: 17.0.1.Final, 18.0.0.Beta1 > Reporter: Robin Schimpf > Assignee: Alessio Soldano > Priority: Major > Attachments: wildfly-bug.zip > > > We currently are upgrading our application from Wildfly 13 to Wildfly 17.0.1 and are receiving duplicated constraint violations in the response of an invalid request. > Interestingly Wildfly 13 also seems to be not behaving correctly on the third request but in another way. There is the violation exception returned in the response instead of the duplicated value Wildfly 17 is returning now. > I also tested this on the currently available Wildfly 18 Beta 1 and the issue is also reproducible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12667) Upgrade Hibernate Validator to 6.0.17

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12667?page=com.atlassian.jira.plugin... ] Brian Stansberry moved JBEAP-17781 to WFLY-12667: ------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12667 (was: JBEAP-17781) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Bean Validation (was: Server) Fix Version/s: 19.0.0.Beta1 (was: 7.3.0.CD18) > Upgrade Hibernate Validator to 6.0.17 > ------------------------------------- > > Key: WFLY-12667 > URL: https://issues.jboss.org/browse/WFLY-12667 > Project: WildFly > Issue Type: Component Upgrade > Components: Bean Validation > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 19.0.0.Beta1 > > > Tracker for Hibernate Validator upgrade to pick up incorporated fixes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12666) JPA jipijapa use optional dependencies instead of modifying the system module

by Brad Maxwell (Jira)

Brad Maxwell created WFLY-12666: ----------------------------------- Summary: JPA jipijapa use optional dependencies instead of modifying the system module Key: WFLY-12666 URL: https://issues.jboss.org/browse/WFLY-12666 Project: WildFly Issue Type: Enhancement Components: JPA / Hibernate Affects Versions: 18.0.0.Final Reporter: Brad Maxwell Assignee: Scott Marlow As per [1] it requires modifying the modules under system/layers/base, these are system modules which users really should not modify. When applying patches it will complain because the module has been modified. It would be better if these modules depended on an optional module which would not exist unless the user configured this. So for example a user could create modules/org/eclipse/persistence/impl/main/module.xml modules/system/layers/base/org/eclipse/persistence/main/module.xml It looks like this almost works with just adding the optional dependency, except there is an exception where it looks like the classloader may not be set correctly for some reason when the module is split into 2. {code} <module name="org.eclipse.persistence" xmlns="urn:jboss:module:1.5"> ... <module name="org.eclipse.persistence.impl" optional="true" services="import"/> {code} {code} <?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.5" name="org.eclipse.persistence.impl"> <resources>  <resource-root path="eclipselink.jar"> <filter> <exclude path="javax/**"/> </filter> </resource-root> </resources> <dependencies> <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="org.antlr"/> <module name="org.dom4j"/> <module name="org.jboss.as.jpa.spi"/> <module name="org.jboss.logging"/> <module name="org.jboss.vfs"/> <module name="org.eclipse.persistence"/>  </dependencies> </module> {code} {code} Caused by: java.lang.IllegalArgumentException: Object: com.jboss.examples.jpa.model.User@4fbcb157 is not a known Entity type. at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNewObjectForPersist(UnitOfWorkImpl.java:4326) at org.eclipse.persistence.internal.jpa.EntityManagerImpl.persist(EntityManagerImpl.java:596) at org.jboss.as.jpa.container.AbstractEntityManager.persist(AbstractEntityManager.java:580) at com.jboss.examples.jpa.TestSingleton.test(TestSingleton.java:29) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:79) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:126) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:112) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:53) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:112) {code} [1] https://docs.jboss.org/author/display/WFLY10/JPA+Reference+Guide#JPARefer... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12627) Upgrade wildfly-http-client to 1.0.17.Final

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12627?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12627: --------------------------------------- Fix Version/s: 19.0.0.Beta1 Assignee: Brian Stansberry (was: Cheng Fang) Resolution: Done > Upgrade wildfly-http-client to 1.0.17.Final > ------------------------------------------- > > Key: WFLY-12627 > URL: https://issues.jboss.org/browse/WFLY-12627 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Tomas Hofman > Assignee: Brian Stansberry > Priority: Major > Fix For: 19.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12665) Duplicated ConstraintViolation message

by Ronald Sigal (Jira)

Ronald Sigal created WFLY-12665: ----------------------------------- Summary: Duplicated ConstraintViolation message Key: WFLY-12665 URL: https://issues.jboss.org/browse/WFLY-12665 Project: WildFly Issue Type: Bug Components: Bean Validation, REST Affects Versions: 17.0.1.Final, 18.0.0.Beta1 Reporter: Robin Schimpf Assignee: Alessio Soldano We currently are upgrading our application from Wildfly 13 to Wildfly 17.0.1 and are receiving duplicated constraint violations in the response of an invalid request. Interestingly Wildfly 13 also seems to be not behaving correctly on the third request but in another way. There is the violation exception returned in the response instead of the duplicated value Wildfly 17 is returning now. I also tested this on the currently available Wildfly 18 Beta 1 and the issue is also reproducible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4642) Stunner: "inline" node label editor stops working if mouse is out of textbox

by Roger Martinez (Jira)

[ https://issues.jboss.org/browse/DROOLS-4642?page=com.atlassian.jira.plugi... ] Roger Martinez reassigned DROOLS-4642: -------------------------------------- Assignee: Dmitrii Tikhomirov (was: Roger Martinez) > Stunner: "inline" node label editor stops working if mouse is out of textbox > ---------------------------------------------------------------------------- > > Key: DROOLS-4642 > URL: https://issues.jboss.org/browse/DROOLS-4642 > Project: Drools > Issue Type: Bug > Components: Stunner > Reporter: Matteo Mortari > Assignee: Dmitrii Tikhomirov > Priority: Major > Labels: Stunner, drools-tools > Attachments: Screen Recording 2019-10-11 at 10.28.05.mov > > > See attachment: I am typing on the keyboard but as I move the mouse away to see what I'm typing, I cannot type anymore as the textfield seems ~"looses focus and closes" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4642) Stunner: "inline" node label editor stops working if mouse is out of textbox

by Roger Martinez (Jira)

[ https://issues.jboss.org/browse/DROOLS-4642?page=com.atlassian.jira.plugi... ] Roger Martinez updated DROOLS-4642: ----------------------------------- Labels: Stunner drools-tools (was: drools-tools) > Stunner: "inline" node label editor stops working if mouse is out of textbox > ---------------------------------------------------------------------------- > > Key: DROOLS-4642 > URL: https://issues.jboss.org/browse/DROOLS-4642 > Project: Drools > Issue Type: Bug > Components: Stunner > Reporter: Matteo Mortari > Assignee: Roger Martinez > Priority: Major > Labels: Stunner, drools-tools > Attachments: Screen Recording 2019-10-11 at 10.28.05.mov > > > See attachment: I am typing on the keyboard but as I move the mouse away to see what I'm typing, I cannot type anymore as the textfield seems ~"looses focus and closes" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4628) [Drools-4628] Fix PodAsALeaderSnapshotTest random failure

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4628?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4628: --------------------------------------- Summary: [Drools-4628] Fix PodAsALeaderSnapshotTest random failure (was: Fix PodAsALeaderSnapshotTest random failure) > [Drools-4628] Fix PodAsALeaderSnapshotTest random failure > --------------------------------------------------------- > > Key: DROOLS-4628 > URL: https://issues.jboss.org/browse/DROOLS-4628 > Project: Drools > Issue Type: Bug > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4628) [Drools-4628] Fix PodAsALeaderSnapshotTest random failure

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4628?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-4628. ---------------------------------------- Resolution: Done > [Drools-4628] Fix PodAsALeaderSnapshotTest random failure > --------------------------------------------------------- > > Key: DROOLS-4628 > URL: https://issues.jboss.org/browse/DROOLS-4628 > Project: Drools > Issue Type: Bug > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- 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