May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12083) Deployment failure if an explicit bean archive contain a Pojo with @NotNull annotation

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-12083?page=com.atlassian.jira.plugin... ] Tomas Hofman commented on WFLY-12083: ------------------------------------- The interceptor being applied is {code}Interceptor [class org.hibernate.validator.cdi.internal.interceptor.ValidationInterceptor intercepts @MethodValidated]{code} Interesting passage from CDI spec is {quote} 3.11. Unproxyable bean types The container uses proxies to provide certain functionality. Certain legal bean types cannot be proxied by the container: * classes which don’t have a non-private constructor with no parameters, * ... A bean type must be proxyable if an injection point resolves to a bean: * ... * that has a bound interceptor. Otherwise, the container automatically detects the problem, and treats it as a deployment problem. {quote} So that would look as an application problem - defining non-proxyable bean but requesting a functionality (validation) that requires a proxy? There's already a configuration option in Weld that causes it to print a warning (instead of failing a deployment) when a *final* method is being intercepted: {code} InterceptionModelInitializer: private void initInterceptor(InterceptionType interceptionType, AnnotatedMethod<?> method, Set<Annotation> methodBindingAnnotations) { List<Interceptor<?>> methodBoundInterceptors = manager.resolveInterceptors(interceptionType, methodBindingAnnotations); if (methodBoundInterceptors != null && methodBoundInterceptors.size() > 0) { Method javaMethod = method.getJavaMember(); if (Reflections.isFinal(javaMethod)) { if (configuration.isFinalMethodIgnored(javaMethod.getDeclaringClass().getName())) { BeanLogger.LOG.finalMethodNotIntercepted(javaMethod, methodBoundInterceptors.get(0).getBeanClass().getName()); } else { throw BeanLogger.LOG.finalInterceptedBeanMethodNotAllowed(method, methodBoundInterceptors.get(0).getBeanClass().getName()); } } else { builder.interceptMethod(interceptionType, javaMethod, asInterceptorMetadata(methodBoundInterceptors), methodBindingAnnotations); } } } {code} So similar condition could be added to check for non-private constructor? > Deployment failure if an explicit bean archive contain a Pojo with @NotNull annotation > -------------------------------------------------------------------------------------- > > Key: WFLY-12083 > URL: https://issues.jboss.org/browse/WFLY-12083 > Project: WildFly > Issue Type: Bug > Components: Bean Validation > Affects Versions: 17.0.0.Alpha1 > Reporter: Joerg Baesner > Assignee: Brian Stansberry > Priority: Major > Attachments: playground.zip > > > If an exlicit bean archive ({{META-INF}} contains an empty {{beans.xml}}) contain a Pojo without any Bean defining annotations and it has {{@NotNull}} annotations, the deployment of that module fails with: > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."playground-jar.jar".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."playground-jar.jar".WeldStartService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001436: Type org.jboss.playground.PlaygroundToStringUtil is not proxyable because it has a private constructor [EnhancedAnnotatedConstructorImpl] private org.jboss.playground.PlaygroundToStringUtil() - class org.jboss.playground.PlaygroundToStringUtil. > at org.jboss.weld.injection.producer.InterceptionModelInitializer.init(InterceptionModelInitializer.java:117) > at org.jboss.weld.injection.producer.BeanInjectionTarget.buildInterceptionModel(BeanInjectionTarget.java:94) > at org.jboss.weld.injection.producer.BeanInjectionTarget.initializeInterceptionModel(BeanInjectionTarget.java:89) > at org.jboss.weld.injection.producer.BeanInjectionTarget.initializeAfterBeanDiscovery(BeanInjectionTarget.java:99) > at org.jboss.weld.injection.producer.InjectionTargetInitializationContext.initialize(InjectionTargetInitializationContext.java:42) > at org.jboss.weld.injection.producer.InjectionTargetService.initialize(InjectionTargetService.java:63) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:481) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:86) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:97) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700) > ... 6 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1819) The logout handler registration should be reworked

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1819: ------------------------------------- Summary: The logout handler registration should be reworked Key: ELY-1819 URL: https://issues.jboss.org/browse/ELY-1819 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.9.2.CR1 Presently the logout handler is just a Runnable, the problem with this is if it needs any state it means a lambda or an instance of a class tends to be needed to hold the state e.g. {noformat} private void setupProgramaticLogout(HttpScope sessionScope) { logoutHandlerConsumer.accept(() -> { sessionScope.setAttachment(AUTHENTICATED_IDENTITY_KEY, null); }); } {noformat} It would likely be better for the logout handler to be able to request the scope it needs so maybe pass in the 'org.wildfly.security.http.HttpServerScopes' at the very least. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4089) EvaluatedExpression not well resolved with JIT during race

by vincent palau (Jira)

[ https://issues.jboss.org/browse/DROOLS-4089?page=com.atlassian.jira.plugi... ] vincent palau updated DROOLS-4089: ---------------------------------- Affects Version/s: 7.22.0.Final > EvaluatedExpression not well resolved with JIT during race > ------------------------------------------------------------ > > Key: DROOLS-4089 > URL: https://issues.jboss.org/browse/DROOLS-4089 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.20.0.Final, 7.22.0.Final > Reporter: vincent palau > Assignee: Mario Fusco > Priority: Major > Attachments: debugging-1.png > > > We recently moved from Drools 7.9.0 to 7.20. > Some errors started appearing in ours tests when calling static methods in LHS drools. > This started happening when all tests were run simultaneously. > It seems the mvel JIT compiler kicks in and it incorrectly evaluates the property name: > A simple call to {noformat}ValidationUtils.isNullOrEmpty(interestedPartyNumber){noformat} ends up with this kind of error: > {noformat} > "java.lang.RuntimeException: Unknown property 'nullOrEmpty' on class tech.stage.utils.cwr.model.PublisherRecord" > {noformat} > Debugging info: > Related source-code: https://github.com/kiegroup/drools/blob/7.20.0.Final/drools-core/src/main... > !debugging-1.png|full! > 1) is the current evaluated property > 2) Should be the right property of WriterRecord > 3) Perhaps the expression which should be executed instead of invocations.get(0) > We fixed that somehow disabling JIT with {noformat}ConstraintJittingThresholdOption{noformat} > Is there any chance to this bug fixed? > Do you need more info? > Thanks in advance for your support. > {panel:title=Reproducer} > https://github.com/vp-stage/evaluatedexpressionandjit > {panel} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-768) Maistra - Create TP11 Polarion PQI reports

by Sunil Kondkar (Jira)

Sunil Kondkar created SWSQE-768: ----------------------------------- Summary: Maistra - Create TP11 Polarion PQI reports Key: SWSQE-768 URL: https://issues.jboss.org/browse/SWSQE-768 Project: Kiali QE Issue Type: QE Task Reporter: Sunil Kondkar Get PQI reports for Maistra: 1) Test case Quality Audit report(No missing data) 2) PQI reports - Create TP11 test iteration, link this iteration to Jaeger TP11 test runs 3) Check polarion test case execution reports -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-767) Jaeger - Create TP11 Polarion PQI reports

by Sunil Kondkar (Jira)

Sunil Kondkar created SWSQE-767: ----------------------------------- Summary: Jaeger - Create TP11 Polarion PQI reports Key: SWSQE-767 URL: https://issues.jboss.org/browse/SWSQE-767 Project: Kiali QE Issue Type: QE Task Reporter: Sunil Kondkar Get PQI reports for Jaeger: 1) Test case Quality Audit report(No missing data) 2) PQI reports - Create TP11 test iteration, link this iteration to Jaeger TP11 test runs 3) Check polarion test case execution reports -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-766) Kiali - Create TP11 Polarion PQI reports

by Sunil Kondkar (Jira)

Sunil Kondkar created SWSQE-766: ----------------------------------- Summary: Kiali - Create TP11 Polarion PQI reports Key: SWSQE-766 URL: https://issues.jboss.org/browse/SWSQE-766 Project: Kiali QE Issue Type: QE Task Reporter: Sunil Kondkar Get PQI reports: 1) Test case Quality Audit report(There are some automated test cases without automation script) 2) PQI reports - Create TP11 test iteration, link this iteration to Kiali TP11 test runs 3) Test case execution reports -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-766) Kiali - Create TP11 Polarion PQI reports

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-766?page=com.atlassian.jira.plugin.... ] Sunil Kondkar reassigned SWSQE-766: ----------------------------------- Assignee: Sunil Kondkar > Kiali - Create TP11 Polarion PQI reports > ---------------------------------------- > > Key: SWSQE-766 > URL: https://issues.jboss.org/browse/SWSQE-766 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Assignee: Sunil Kondkar > Priority: Major > Labels: pqi > > Get PQI reports: > 1) Test case Quality Audit report(There are some automated test cases without automation script) > 2) PQI reports - Create TP11 test iteration, link this iteration to Kiali TP11 test runs > 3) Test case execution reports -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1818) Don't use a lambda for the disposal of mechanisms in forEach

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1818: ------------------------------------- Summary: Don't use a lambda for the disposal of mechanisms in forEach Key: ELY-1818 URL: https://issues.jboss.org/browse/ELY-1818 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.9.2.CR1 A simple for loop will be sufficient without needing a lambda defining and instantiating. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12142) Move Java EE 8 BOM import to each Quickstart

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12142: -------------------------------------- Summary: Move Java EE 8 BOM import to each Quickstart Key: WFLY-12142 URL: https://issues.jboss.org/browse/WFLY-12142 Project: WildFly Issue Type: Enhancement Components: Quickstarts Reporter: Eduardo Martins Assignee: Eduardo Martins Each quickstart code should be independent from parent as much as possible wrt to dependency management, and expose directly important snippets, such as the import of the javaee8-with-tools BOM in its dependency management. In concrete this enhancement means that the dependency management import of the javaee8-with-tools BOM, currently in the project root pom.xml, should be moved to each Quickstart root pom.xml that needs it. To minimise maintenance between releases the definition of the BOM version may be kept in the parent tho. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4086) [GSS-RFE] Search feature in GDST

by Yevgeniy Fomin (Jira)

[ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugi... ] Yevgeniy Fomin commented on DROOLS-4086: ---------------------------------------- [~manstis] Hi, I will just share my opinion about some of questions: # We discuss with Jozef and we thinking the most important thing need to be searchable is "Data cells". # We may have a small button with magnifier among other functional buttons and if you navigate the cursor on it or click, the search field will appear !Example.png|thumbnail! # If we will create search only for "Expression editor", I suppose it will be enough just highlight needed result as if we use the browser search. # In [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279] if I understand right, Edson ask you to estimate implementation of search for DMN models and GDT, but customer mention only GDT. So I think we need search for GDT or for both. > [GSS-RFE] Search feature in GDST > -------------------------------- > > Key: DROOLS-4086 > URL: https://issues.jboss.org/browse/DROOLS-4086 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Yevgeniy Fomin > Assignee: Yevgeniy Fomin > Priority: Major > Labels: drools-tools > Attachments: Example.png > > > This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation. > h1. Requirement > - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it. > - We may add auto-suggestion mechanism > - Do we need search history? > - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed. > - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty. > h1. UX design > - Add magnifying-glass icon. > - Search-box can be popup window after clicking on icon or just pop field > - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both. > h1. Documentation > - Replace picture of GDT and DMN editor where they become obsolete > h1. Acceptance test > - Enter to large amount of data in search box > - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed. > - Set of inputs: > *- A-Z > *- a-z > *- 0-9 > *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - + > *- Blank spaces -- This message was sent by Atlassian Jira (v7.12.1#712002)

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