March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-623) UI Automation - Istio Config - Support "Kind:"

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-623?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan reassigned SWSQE-623: ------------------------------------ Assignee: Hayk Hovsepyan > UI Automation - Istio Config - Support "Kind:" > ---------------------------------------------- > > Key: SWSQE-623 > URL: https://issues.jboss.org/browse/SWSQE-623 > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2684) Highlight test result in the grid

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-2684?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2684: --------------------------------- Issue Type: Task (was: Story) > Highlight test result in the grid > --------------------------------- > > Key: DROOLS-2684 > URL: https://issues.jboss.org/browse/DROOLS-2684 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > Priority: Major > > As user I want to see errors of test run directly in the grid -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2495) ContainerXFilter not invoked when registered via DynamicFeature in JAX-RS

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-2495?page=com.atlassian.jira.plugin.... ] Marek Kopecký commented on WFLY-2495: ------------------------------------- [~ron_sigal]: I'm not able to reproduce this issue on WF16, both FeatureContext.register(Class...) and FeatureContext.register(Object...) works correctly. Can you close this issue as out-of-date? If [~aslak] or [~kf777] still see this issue, they can reopen this with a reproducer. > ContainerXFilter not invoked when registered via DynamicFeature in JAX-RS > ------------------------------------------------------------------------- > > Key: WFLY-2495 > URL: https://issues.jboss.org/browse/WFLY-2495 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 8.0.0.Beta1, 8.1.0.Final > Reporter: Aslak Knutsen > Assignee: Ron Sigal > Priority: Major > > {code} > @Provider > public class DynamicServerLogggingFilterFeature implements DynamicFeature { > @Override > public void configure(ResourceInfo ri, FeatureContext fc) { > if (MyResource.class.isAssignableFrom(ri.getResourceClass()) > && ri.getResourceMethod().isAnnotationPresent(GET.class)) { > fc.register(new ServerLoggingFilter()); > } > } > } > @Provider > @ServerLogged > public class ServerLoggingFilter implements ContainerRequestFilter, ContainerResponseFilter { > ... > } > {code} > DynamicServerLogggingFilterFeature is called the the ServerLoggingFilter is registered in the FeatureContext, but the filter(ContainerXContext crc) is never called on the ServerLoggingFilter. > Sample: https://github.com/arun-gupta/javaee7-samples/tree/master/jaxrs/dynamicfi... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2495) ContainerXFilter not invoked when registered via DynamicFeature in JAX-RS

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-2495?page=com.atlassian.jira.plugin.... ] Marek Kopecký reassigned WFLY-2495: ----------------------------------- Assignee: Ron Sigal (was: Bill Burke) > ContainerXFilter not invoked when registered via DynamicFeature in JAX-RS > ------------------------------------------------------------------------- > > Key: WFLY-2495 > URL: https://issues.jboss.org/browse/WFLY-2495 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 8.0.0.Beta1, 8.1.0.Final > Reporter: Aslak Knutsen > Assignee: Ron Sigal > Priority: Major > > {code} > @Provider > public class DynamicServerLogggingFilterFeature implements DynamicFeature { > @Override > public void configure(ResourceInfo ri, FeatureContext fc) { > if (MyResource.class.isAssignableFrom(ri.getResourceClass()) > && ri.getResourceMethod().isAnnotationPresent(GET.class)) { > fc.register(new ServerLoggingFilter()); > } > } > } > @Provider > @ServerLogged > public class ServerLoggingFilter implements ContainerRequestFilter, ContainerResponseFilter { > ... > } > {code} > DynamicServerLogggingFilterFeature is called the the ServerLoggingFilter is registered in the FeatureContext, but the filter(ContainerXContext crc) is never called on the ServerLoggingFilter. > Sample: https://github.com/arun-gupta/javaee7-samples/tree/master/jaxrs/dynamicfi... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-623) UI Automation - Istio Config - Support "Kind:"

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-623: ------------------------------------ Summary: UI Automation - Istio Config - Support "Kind:" Key: SWSQE-623 URL: https://issues.jboss.org/browse/SWSQE-623 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-61) Support alternate JVM in domain scripts

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFCORE-61?page=com.atlassian.jira.plugin.... ] Marek Kopecký commented on WFCORE-61: ------------------------------------- [~jamezp]: This looks like "feature request" more than bug. What is your plan with this? There is no action here for ~4.5 years. Close this? > Support alternate JVM in domain scripts > --------------------------------------- > > Key: WFCORE-61 > URL: https://issues.jboss.org/browse/WFCORE-61 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > The domain scripts don't support adding a separate JVM for the {{\-jvm}} and {{--default-jvm}} options. The scripts should support these, e.g. check the {{$JAVA_FROM_JVM}} value before assigning it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-61) Support alternate JVM in domain scripts

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFCORE-61?page=com.atlassian.jira.plugin.... ] Marek Kopecký updated WFCORE-61: -------------------------------- Issue Type: Feature Request (was: Bug) > Support alternate JVM in domain scripts > --------------------------------------- > > Key: WFCORE-61 > URL: https://issues.jboss.org/browse/WFCORE-61 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > The domain scripts don't support adding a separate JVM for the {{\-jvm}} and {{--default-jvm}} options. The scripts should support these, e.g. check the {{$JAVA_FROM_JVM}} value before assigning it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3077: ------------------------------------- [~manstis] +1, will discuss. I created another alternative for the discussion: https://redhat.invisionapp.com/share/SFQT5JRMAQ4 It imposes some limitations: * If the data type already has constraints, the user will either need to go to the Manage section to work with the data type, or they enter additional Input constraints inline, but only as an expression. Note: I don't think the input expression bit is correct in my mock, so please disregard for now. :) * I removed the "Apply to Data Type" option in this round. Rather user would need to work with the data type directly in the Manage section. > Enhance data type restrictions UX - Decision Table/properties > ------------------------------------------------------------- > > Key: DROOLS-3077 > URL: https://issues.jboss.org/browse/DROOLS-3077 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1387) Add VisualVm launch scripts to the AS7 distribution

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFCORE-1387?page=com.atlassian.jira.plugi... ] Marek Kopecký updated WFCORE-1387: ---------------------------------- Affects Version/s: 8.0.0.Final > Add VisualVm launch scripts to the AS7 distribution > --------------------------------------------------- > > Key: WFCORE-1387 > URL: https://issues.jboss.org/browse/WFCORE-1387 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Affects Versions: 8.0.0.Final > Environment: All > Reporter: John O'Hara > Priority: Optional > > Launching VisualVM with remoting-jmx requires additional jars to be on the classpath, in the same way that launching jconsole does. > Can we provice a .sh and a .bat with the correct classpath in the AS7 distribution to launch visualvm -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10448) Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-10448?page=com.atlassian.jira.plugin... ] Marek Kopecký updated WFLY-10448: --------------------------------- Affects Version/s: 16.0.0.Final > Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh > ------------------------------------------------------------------------------------------------ > > Key: WFLY-10448 > URL: https://issues.jboss.org/browse/WFLY-10448 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 13.0.0.Final, 16.0.0.Final > Reporter: R Searls > Assignee: R Searls > Priority: Minor > > bin\scripts domain.sh, standalone.sh and appclient.sh have a section of code that uses java option -d32 and -d64 when calling java to check the HotSpot type. These 2 options have been removed from JDK-10. They are marked as deprecated in JDK-9 but still function. > These options are used in determining if '-server' is added to JAVA_OPTS. Enhancements need to be made to the scripts to check the JDK version and take appropriate action is assigning the value '-server'. > The code affected > {code:java} > # Check for -d32/-d64 in JAVA_OPTS > JVM_OPTVERSION="-version" > JVM_D64_OPTION=`echo $JAVA_OPTS | $GREP "\-d64"` > JVM_D32_OPTION=`echo $JAVA_OPTS | $GREP "\-d32"` > test "x$JVM_D64_OPTION" != "x" && JVM_OPTVERSION="-d64 $JVM_OPTVERSION" > test "x$JVM_D32_OPTION" != "x" && JVM_OPTVERSION="-d32 $JVM_OPTVERSION" > # If -server not set in JAVA_OPTS, set it, if supported > SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"` > if [ "x$SERVER_SET" = "x" ]; then > # Check for SUN(tm) JVM w/ HotSpot support > if [ "x$HAS_HOTSPOT" = "x" ]; then > HAS_HOTSPOT=`"$JAVA" $JVM_OPTVERSION -version 2>&1 | $GREP -i HotSpot` > fi > # Check for OpenJDK JVM w/server support > if [ "x$HAS_OPENJDK" = "x" ]; then > HAS_OPENJDK=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i OpenJDK` > fi > # Check for IBM JVM w/server support > if [ "x$HAS_IBM" = "x" ]; then > HAS_IBM=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i "IBM J9"` > fi > # Enable -server if we have Hotspot or OpenJDK, unless we can't > if [ "x$HAS_HOTSPOT" != "x" -o "x$HAS_OPENJDK" != "x" -o "x$HAS_IBM" != "x" ]; then > # MacOS does not support -server flag > if [ "$darwin" != "true" ]; then > PROCESS_CONTROLLER_JAVA_OPTS="-server $PROCESS_CONTROLLER_JAVA_OPTS" > HOST_CONTROLLER_JAVA_OPTS="-server $HOST_CONTROLLER_JAVA_OPTS" > JVM_OPTVERSION="-server $JVM_OPTVERSION" > fi > fi > else > JVM_OPTVERSION="-server $JVM_OPTVERSION" > fi > {code} > Here is the output of the currently supported java versions > Doc for jdk-8 states > > java -help > where options include: > -d32 use a 32-bit data model if available > -d64 use a 64-bit data model if available > Using these options tell if the version supports 32-bit or 64-bit > > java -d32 -version > Error: This Java instance does not support a 32-bit JVM. > Please install the desired version. > > java -d64 -version > java version "1.8.0_72" > Java(TM) SE Runtime Environment (build 1.8.0_72-b15) > Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode) > Doc for jdk-9 states > > java -help > where options include: > -d32 Deprecated, will be removed in a future release > -d64 Deprecated, will be removed in a future release > > java -d32 -version > Error: This Java instance does not support a 32-bit JVM. > Please install the desired version. > > java -d64 -version > openjdk version "9.0.4" > OpenJDK Runtime Environment (build 9.0.4+11) > OpenJDK 64-Bit Server VM (build 9.0.4+11, mixed mode) > Doc for jdk-10 > > java -help > No documentation for these options listed > > java -d32 -version > Unrecognized option: -d32 > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > > java -d64 -version > Unrecognized option: -d64 > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 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 March 2019