January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-545) UI Automate 'Weight Sum' field from VS Overview

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-545?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-545: -------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/123 > UI Automate 'Weight Sum' field from VS Overview > ----------------------------------------------- > > Key: SWSQE-545 > URL: https://issues.jboss.org/browse/SWSQE-545 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-545) UI Automate 'Weight Sum' field from VS Overview

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-545?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-545. ---------------------------------- Resolution: Done > UI Automate 'Weight Sum' field from VS Overview > ----------------------------------------------- > > Key: SWSQE-545 > URL: https://issues.jboss.org/browse/SWSQE-545 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11120) org.jboss.ws.saaj-impl not referenced from org.jboss.as.webservices

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11120?page=com.atlassian.jira.plugin... ] Jan Blizňák commented on WFLY-11120: ------------------------------------ Actually, it looks like this org.jboss.ws.saaj-impl \[1\] module is completly unused; and there is a module \[2\] consuming the same dependencies. \[1\] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... \[2\] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... [~asoldano] should this \[1\] module be removed (given it is private and unused)? > org.jboss.ws.saaj-impl not referenced from org.jboss.as.webservices > ------------------------------------------------------------------- > > Key: WFLY-11120 > URL: https://issues.jboss.org/browse/WFLY-11120 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Jean-Francois Denise > Assignee: Alessio Soldano > Priority: Major > > This dependency seems to me required. This has an impact in galleon context. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-102) SNI - hostname notation for sni-mapping element does not conform generic rules

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFWIP-102?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFWIP-102: -------------------------------------- Assignee: Darran Lofthouse (was: Stuart Douglas) > SNI - hostname notation for sni-mapping element does not conform generic rules > ------------------------------------------------------------------------------ > > Key: WFWIP-102 > URL: https://issues.jboss.org/browse/WFWIP-102 > Project: WildFly WIP > Issue Type: Bug > Environment: Wildfly build with undertow and wildfly-core modules build from following sources: > * https://github.com/stuartwdouglas/undertow/tree/sni > * https://github.com/stuartwdouglas/wildfly-core/tree/sni > Reporter: Jan Stourac > Assignee: Darran Lofthouse > Priority: Major > > Way of configuration of {{sni-mapping}} element in {{server-ssl-sni-context}} is not nice from UX and also does not conform the way it is generally used. > With current implementation administrator has to use following notation: > {code} > .*\.example\.com > {code} > This is standard reg-exp notation and is not for easy reading. I think following notation is much better and also is commonly used for this cases: > {code} > *.example.com > {code} > In other words - simple asterisk is used to match any subdomain and dot in our case does not stand for 'any single character'. Note that is the way it was described in [analysis document|https://github.com/wildfly/wildfly-proposals/pull/67/files#diff-...]. > Truth is that with this change we loose some flexibility, e.g. administrator won't be able to configure following: > {code} > www\.exa.ple\.com > {code} > But I doubt this is a common use case. WDYT? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11571) Upgrade FasterXML Jackson from 2.9.5 to 2.9.8

by Bartosz Spyrko-Śmietanko (Jira)

[ https://issues.jboss.org/browse/WFLY-11571?page=com.atlassian.jira.plugin... ] Bartosz Spyrko-Śmietanko updated WFLY-11571: -------------------------------------------- Component/s: XML Frameworks (was: Server) > Upgrade FasterXML Jackson from 2.9.5 to 2.9.8 > --------------------------------------------- > > Key: WFLY-11571 > URL: https://issues.jboss.org/browse/WFLY-11571 > Project: WildFly > Issue Type: Component Upgrade > Components: XML Frameworks > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > Priority: Major > Labels: downstream_dependency > > Tag: > https://github.com/FasterXML/jackson-core/releases/tag/jackson-core-2.9.8 > https://github.com/FasterXML/jackson-annotations/releases/tag/jackson-ann... > https://github.com/FasterXML/jackson-databind/releases/tag/jackson-databi... > https://github.com/FasterXML/jackson-modules-java8/releases/tag/jackson-m... > https://github.com/FasterXML/jackson-jaxrs-providers/releases/tag/jackson... > https://github.com/FasterXML/jackson-modules-base/releases/tag/jackson-mo... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11120) org.jboss.ws.saaj-impl not referenced from org.jboss.as.webservices

by Jean-Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFLY-11120?page=com.atlassian.jira.plugin... ] Jean-Francois Denise closed WFLY-11120. --------------------------------------- Resolution: Rejected Closing it, this dependency is not required nor injected in deployment units. I missed something at some point. > org.jboss.ws.saaj-impl not referenced from org.jboss.as.webservices > ------------------------------------------------------------------- > > Key: WFLY-11120 > URL: https://issues.jboss.org/browse/WFLY-11120 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Jean-Francois Denise > Assignee: Alessio Soldano > Priority: Major > > This dependency seems to me required. This has an impact in galleon context. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3493) Drools Workbench execution of test scenarios hangs when rule has a bug.

by Philip Usatine (Jira)

Philip Usatine created DROOLS-3493: -------------------------------------- Summary: Drools Workbench execution of test scenarios hangs when rule has a bug. Key: DROOLS-3493 URL: https://issues.jboss.org/browse/DROOLS-3493 Project: Drools Issue Type: Bug Affects Versions: 7.15.0.Final Environment: Drools Workbench container downloaded from Docker Hub - 7.15.0.Final Reporter: Philip Usatine Assignee: Mario Fusco Attachments: image-2019-01-08-12-13-43-386.png In the workbench, any error in a decision table or guided rule will cause web UI to hang when running test scenarios that cause that rule to execute. Reloading the page allows you to access the web interface again, but you need to navigate back to where you were. This makes iterative development and testing extremely cumbersome. The web UI reports the following error: An unexpected error happened. Please try again in a few minutes and the 'Building and running scenario' wait spinner spins forever. (See attached screenshot). Copy error details returns the following text: {"ToSubject":"org.drools.workbench.screens.testscenario.service.ScenarioTestEditorService:RPC.runScenario:java.lang.String:org.uberfire.backend.vfs.Path:org.drools.workbench.models.testscenarios.shared.Scenario::88:RespondTo:RPC"} | Uncaught exception: Client-side exception occurred although RPC call succeeded. Caused by: undefined !image-2019-01-08-12-13-43-386.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11573) Remove Servlet 3.1 dependency

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11573?page=com.atlassian.jira.plugin... ] Jan Blizňák updated WFLY-11573: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/11986 PR with proposed fix sent https://github.com/wildfly/wildfly/pull/11986 > Remove Servlet 3.1 dependency > ----------------------------- > > Key: WFLY-11573 > URL: https://issues.jboss.org/browse/WFLY-11573 > Project: WildFly > Issue Type: Task > Components: EE > Affects Versions: 15.0.1.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > There is JBoss Servlet API dependency declared in two different versions 3.1 and 4.0 which is probably a leftover from transition period during EE8 support development. > Since server built from sources contains only dist/target/wildfly-16.0.0.Beta1-SNAPSHOT/modules/system/layers/base/javax/servlet/api/main/jboss-servlet-api_4.0_spec-1.0.0.Final.jar file it should be safe to remove this from WF project. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3098) UX: Add support for data object List/Map

by Amy Glass (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Amy Glass commented on DROOLS-3098: ----------------------------------- Thanks [~zhutaojiajia] > UX: Add support for data object List/Map > ---------------------------------------- > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps. > Preconditions: New feature of current implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11573) Remove Servlet 3.1 dependency

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11573?page=com.atlassian.jira.plugin... ] Jan Blizňák reassigned WFLY-11573: ---------------------------------- Assignee: Jan Blizňák > Remove Servlet 3.1 dependency > ----------------------------- > > Key: WFLY-11573 > URL: https://issues.jboss.org/browse/WFLY-11573 > Project: WildFly > Issue Type: Task > Components: EE > Affects Versions: 15.0.1.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > There is JBoss Servlet API dependency declared in two different versions 3.1 and 4.0 which is probably a leftover from transition period during EE8 support development. > Since server built from sources contains only dist/target/wildfly-16.0.0.Beta1-SNAPSHOT/modules/system/layers/base/javax/servlet/api/main/jboss-servlet-api_4.0_spec-1.0.0.Final.jar file it should be safe to remove this from WF project. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2019