January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2254) Automate .proto files rebuild

by Dmitry Volodin (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2254?page=com.atlassian.jira.plugi... ] Dmitry Volodin updated DROOLS-2254: ----------------------------------- Summary: Automate .proto files rebuild (was: Automate .proto files rebuld) > Automate .proto files rebuild > ----------------------------- > > Key: DROOLS-2254 > URL: https://issues.jboss.org/browse/DROOLS-2254 > Project: Drools > Issue Type: Task > Components: tools > Affects Versions: 7.5.0.Final > Reporter: Dmitry Volodin > Assignee: Dmitry Volodin > Priority: Minor > Fix For: 7.6.0.Final > > > According to contribution guide, any .proto file or protobuf version changes it's necessary to download protoc utility and regenerate Java classes based on .proto files. > This will add automation for downloading protoc utility and Java classes generation based on Maven Protocol Buffers Plugin. There is no timestamps and other build related info inside generated Java files and no changes will be added on each new build. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2254) Automate .proto files rebuld

by Dmitry Volodin (JIRA)

Dmitry Volodin created DROOLS-2254: -------------------------------------- Summary: Automate .proto files rebuld Key: DROOLS-2254 URL: https://issues.jboss.org/browse/DROOLS-2254 Project: Drools Issue Type: Task Components: tools Affects Versions: 7.5.0.Final Reporter: Dmitry Volodin Assignee: Dmitry Volodin Priority: Minor Fix For: 7.6.0.Final According to contribution guide, any .proto file or protobuf version changes it's necessary to download protoc utility and regenerate Java classes based on .proto files. This will add automation for downloading protoc utility and Java classes generation based on Maven Protocol Buffers Plugin. There is no timestamps and other build related info inside generated Java files and no changes will be added on each new build. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2253) Upgrade protobuf-java from 2.6.0 to 2.6.1

by Dmitry Volodin (JIRA)

Dmitry Volodin created DROOLS-2253: -------------------------------------- Summary: Upgrade protobuf-java from 2.6.0 to 2.6.1 Key: DROOLS-2253 URL: https://issues.jboss.org/browse/DROOLS-2253 Project: Drools Issue Type: Task Components: core engine Affects Versions: 7.5.0.Final Reporter: Dmitry Volodin Assignee: Dmitry Volodin Priority: Minor Fix For: 7.6.0.Final This update requires for automate protobuf builds with Maven Protocol Buffers Plugin as starting version 2.6.1 Google publish protoc utility in the maven repository for all major releases and further change will rebuild .proto files depends on version or source changes. The prorobuf versions 2.6.0 and 2.6.1 are fully binary and source compatible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2250) Align Engine hints in Decision Table column wizard with BAPL-708

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2250?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2250: ----------------------------------- Sprint: 2018 Week 03-04 > Align Engine hints in Decision Table column wizard with BAPL-708 > ---------------------------------------------------------------- > > Key: DROOLS-2250 > URL: https://issues.jboss.org/browse/DROOLS-2250 > Project: Drools > Issue Type: Task > Components: Guided Decision Table Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: Screenshot from 2018-01-17 13-49-51.png, Screenshot from 2018-01-17 13-50-37.png > > > Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3512) ClassReflectionIndexUtil does not return default methods from findMethod

by Daniel Bildhauer (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3512?page=com.atlassian.jira.plugi... ] Daniel Bildhauer commented on WFCORE-3512: ------------------------------------------ Hi, [~swd847] is there any chance to get this fix also back to the version that will be in Wildfly 11.1? Best regards Daniel > ClassReflectionIndexUtil does not return default methods from findMethod > ------------------------------------------------------------------------ > > Key: WFCORE-3512 > URL: https://issues.jboss.org/browse/WFCORE-3512 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Daniel Bildhauer > Assignee: Stuart Douglas > Fix For: 4.0.0.Alpha6 > > Attachments: ejb-in-ear.zip, wildfly-ejb-in-ear-ear.ear > > > This problem is in Wildfly Core, but manifests as an issue with EJB's in WildFly full. > Given the following class/interface inheritance structure, the interface method doMagic could not be called from a remote view, even if there is a default implementation as given in the mixin interface. A local call works, but the remote call fails with a message like > {code} > org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) > {code} > Example code: > {code} > @Remote > interface MyEJBInterface { > void doMagic(); > } > interface MyEJBMixin extends MyEJBInterface { > default void doMagic() { .... } > } > @Stateless > class MyEJBBean extends MyEJBMixin { > } > {code} > The problem is inside the fix for WFLY-4354 bug, which checks only for the default method implementation in the interface declaring the method the first time but not in other interfaces. > A example is attached and I will submitt a pull request with a fix. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9708) Wildfly 11.0.0.Final JSF 1.2 configuration error

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-9708?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-9708: ------------------------------------ It seems that {{org.jboss.as.jsf.injection.weld.WeldApplication}} is loaded because {{org.jboss.as.jsf.injection.weld.WeldApplicationFactory}} is declared in the {{faces-config.xml}} of the {{org.jboss.as.jsf-injection}} module. [~ssilvert] Is the injection module always added to the deployment? I cannot find the place where this dependency is added. > Wildfly 11.0.0.Final JSF 1.2 configuration error > ------------------------------------------------ > > Key: WFLY-9708 > URL: https://issues.jboss.org/browse/WFLY-9708 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 11.0.0.Final > Reporter: Luis Canales > Assignee: Martin Kouba > Priority: Optional > Attachments: log.txt > > > Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error: > _java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper_ > If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2252) "Unable to expand" error with acculumate in Guided Rule Editor with DSL

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2252?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2252: -------------------------------- Tester: Jozef Marko (was: Jan Hrcek) > "Unable to expand" error with acculumate in Guided Rule Editor with DSL > ----------------------------------------------------------------------- > > Key: DROOLS-2252 > URL: https://issues.jboss.org/browse/DROOLS-2252 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.5.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: support > > In Guided Rule Editor with DSL option, you can add "From Accumulate" but "Function"/"Custom Code" gets an error "Unable to expand". > Reproduce steps: > - Unzip the attached reproducer-repo.zip > - Clone the repo via business-central "Administration" > "Repositories" > "Clone Repository" > - Go to Project Explorer, choose the repo, choose "project1" > - Go to package org > kie > example > project1. You will find DataObject 'Person,' DSL, Test Scenario > - Create a new Guided Rule. Check "Use Domain Specific Language (DSL)" option > - Add conditions (See guidedrule01.png) > -- DSL "There is a person whose age is 20" > -- "From Accumulate ..." > --- Choose "Number" for the first "click to add pattern..." > --- Choose "Person" for the second "click to add pattern..." > --- Configure Variable name "$p" for "All Person with" > -- Write "count($p)" in Function > - Save > - Press "Validate" > - You will get an error "Unable to expand" (See error01.png) > This is because "count($p)" line doesn't have preceding ">". > {noformat} > rule "gr1" > dialect "mvel" > when > There is a person whose age is 20 > >Number( ) from accumulate ( $p : Person( ), > count($p)) > then > end > {noformat} > - If you add ">" at the begging of Function (See guidedrule02.png), you don't get the error. > - But if you close the Editor and reopen the rdslr, the condition is rendered as free form DRL (See guidedrule03.png). So it cannot be a workaround. > - "Custom Code" has the same problem as "Function". Furthermore, "Custom Code" cannot use ">" because ">" wouldn't be placed at the beginning of the line. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9706) Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values are not -1

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9706?page=com.atlassian.jira.plugin.... ] Erich Duda commented on WFLY-9706: ---------------------------------- I agree that it is unlikely that someone uses e.g. -2 instead of -1. Additionally if someone really does, the fix is easy and straightforward. I don't have any opinion how this should be handled. I think all proposed solutions (corrector, warning, do nothing) are OK. [~jmesnil] wdyt? > Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values are not -1 > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-9706 > URL: https://issues.jboss.org/browse/WFLY-9706 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Alpha1 > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > > This Jira is reaction to WFLY-9433. > The WFLY-9433 makes validator rules more strict for some attributes in messaging subsystem. Although there is no reason to use these values (which are newly considered as invalid), it was possible to configure them and they worked with Wildfly 11 and previous releases. > As it is proposed in JBEAP-14110, this change should be done in 2 steps: > * only WARN the user if the parameter is not valid (a negative value other than -1) > * in next release, reject the parameter > I am setting priority as Blocker, because this fix must be included in Wildfly 12 release. It makes no sense to do it later. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9712) Add test for WFCORE-3512

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9712: ------------------------------------ Summary: Add test for WFCORE-3512 Key: WFLY-9712 URL: https://issues.jboss.org/browse/WFLY-9712 Project: WildFly Issue Type: Task Reporter: Stuart Douglas Assignee: Stuart Douglas Even though this is a WFCORE issue it only really manifests via EJB. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9711) Move web tests in integration/web

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9711: ------------------------------------ Summary: Move web tests in integration/web Key: WFLY-9711 URL: https://issues.jboss.org/browse/WFLY-9711 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Stuart Douglas Assignee: Stuart Douglas At the moment web tests are split between integration/basic and integration/web, they should only be in integration/web -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018