January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5787) [DMN Designer] Show parameters list for Decision Services - Blog post

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5787?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5787: ----------------------------------- Epic Link: (was: BAPL-1775) > [DMN Designer] Show parameters list for Decision Services - Blog post > --------------------------------------------------------------------- > > Key: DROOLS-5787 > URL: https://issues.redhat.com/browse/DROOLS-5787 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > > Blog post on http://blog.kie.org about this feature. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14098) signature test failures in (JAX-RS) JAX-jakarta.ws.rs.core

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-14098?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-14098: ------------------------------------- I am closing my current PR as the forked repo is not the correct one. > signature test failures in (JAX-RS) JAX-jakarta.ws.rs.core > ---------------------------------------------------------- > > Key: WFLY-14098 > URL: https://issues.redhat.com/browse/WFLY-14098 > Project: WildFly > Issue Type: Sub-task > Components: REST > Reporter: Scott Marlow > Assignee: Parul Sharma > Priority: Major > Labels: EE9 > > The described as "missing" methods are very similar to the "added" methods except for one small change. Basically, the "missing" method signatures must match exactly what we have in the jakarta.ws.rs.core classes (protected method must be changed to public method).. > {quote} > Missing Superclasses or Superinterfaces > [javatest.batch] --------------------------------------- > [javatest.batch] > [javatest.batch] jakarta.ws.rs.core.AbstractMultivaluedMap: interface @ java.io.Serializable > [javatest.batch] > [javatest.batch] Missing Methods > [javatest.batch] --------------- > [javatest.batch] > [javatest.batch] jakarta.ws.rs.core.UriBuilder: method public static jakarta.ws.rs.core.UriBuilder jakarta.ws.rs.core.UriBuilder.newInstance() > [javatest.batch] > [javatest.batch] Added Methods > [javatest.batch] ------------- > [javatest.batch] > [javatest.batch] jakarta.ws.rs.core.UriBuilder: method protected static jakarta.ws.rs.core.UriBuilder jakarta.ws.rs.core.UriBuilder.newInstance() > [javatest.batch] > [javatest.batch] Missed Annotations > [javatest.batch] ------------------ > [javatest.batch] > [javatest.batch] jakarta.ws.rs.core.CacheControl: toString():anno 0 java.lang.Deprecated() > [javatest.batch] jakarta.ws.rs.core.CacheControl: valueOf(java.lang.String):anno 0 java.lang.Deprecated() > [javatest.batch] jakarta.ws.rs.core.Cookie: toString():anno 0 java.lang.Deprecated() > [javatest.batch] --- affected jakarta.ws.rs.core.NewCookie > [javatest.batch] jakarta.ws.rs.core.Cookie: valueOf(java.lang.String):anno 0 java.lang.Deprecated() > [javatest.batch] --- affected jakarta.ws.rs.core.NewCookie > [javatest.batch] jakarta.ws.rs.core.EntityTag: toString():anno 0 java.lang.Deprecated() > [javatest.batch] jakarta.ws.rs.core.EntityTag: valueOf(java.lang.String):anno 0 java.lang.Deprecated() > [javatest.batch] > [javatest.batch] duplicate messages suppressed: 2 > [javatest.batch] > {quote} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-603) Migrate Jenkins2 CI Pipeline to PSI

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-603?page=com.atlassian.jira.plugin... ] Filip Brychta reassigned SWSQE-603: ----------------------------------- Assignee: Filip Brychta (was: Matthew Mahoney) > Migrate Jenkins2 CI Pipeline to PSI > ------------------------------------ > > Key: SWSQE-603 > URL: https://issues.redhat.com/browse/SWSQE-603 > Project: Kiali QE > Issue Type: Story > Reporter: Matthew Mahoney > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > QE CI/CP Integration -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-603) Migrate Jenkins2 CI Pipeline to PSI

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-603?page=com.atlassian.jira.plugin... ] Filip Brychta updated SWSQE-603: -------------------------------- Sprint: Kiali Sprint #27, Kiali Sprint #51 (was: Kiali Sprint #27) > Migrate Jenkins2 CI Pipeline to PSI > ------------------------------------ > > Key: SWSQE-603 > URL: https://issues.redhat.com/browse/SWSQE-603 > Project: Kiali QE > Issue Type: Story > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > QE CI/CP Integration -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFWIP-361) keycloak-wildfly-adapter module is missing when using the keycloak-client-oidc layer

by Ondrej Kotek (Jira)

[ https://issues.redhat.com/browse/WFWIP-361?page=com.atlassian.jira.plugin... ] Ondrej Kotek closed WFWIP-361. ------------------------------ > keycloak-wildfly-adapter module is missing when using the keycloak-client-oidc layer > ------------------------------------------------------------------------------------ > > Key: WFWIP-361 > URL: https://issues.redhat.com/browse/WFWIP-361 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Ondrej Kotek > Assignee: Darran Lofthouse > Priority: Major > > When we compare the KeyCloak WildFly OIDC installations (layer vs. zip), _keycloak-wildfly-adapter_ module is missing when we use the _keycloak-client-oidc_ layer. > Does it limit the adapter functionality somehow? -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFWIP-361) keycloak-wildfly-adapter module is missing when using the keycloak-client-oidc layer

by Ondrej Kotek (Jira)

[ https://issues.redhat.com/browse/WFWIP-361?page=com.atlassian.jira.plugin... ] Ondrej Kotek resolved WFWIP-361. -------------------------------- Resolution: Explained > keycloak-wildfly-adapter module is missing when using the keycloak-client-oidc layer > ------------------------------------------------------------------------------------ > > Key: WFWIP-361 > URL: https://issues.redhat.com/browse/WFWIP-361 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Ondrej Kotek > Assignee: Darran Lofthouse > Priority: Major > > When we compare the KeyCloak WildFly OIDC installations (layer vs. zip), _keycloak-wildfly-adapter_ module is missing when we use the _keycloak-client-oidc_ layer. > Does it limit the adapter functionality somehow? -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (JBJCA-1416) Make resource-adapter validation logs more user friendly

by Tomasz Adamski (Jira)

Tomasz Adamski created JBJCA-1416: ------------------------------------- Summary: Make resource-adapter validation logs more user friendly Key: JBJCA-1416 URL: https://issues.redhat.com/browse/JBJCA-1416 Project: IronJacamar Issue Type: Enhancement Reporter: Tomasz Adamski Assignee: Tomasz Adamski Currently resource adapter validation logs are written to hidden ".logs" file. The goal of this issue is to make the log name dependent on resource adapter archive name and print information about this name to log. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14266) Connector: enable configuration of resource adapter validation log directory

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-14266?page=com.atlassian.jira.plugi... ] Tomasz Adamski updated WFLY-14266: ---------------------------------- Description: Currently resource-adapter validation logs are not created because report-directory property that IronJacamar uses is always null. The goal of this issue is to implement such config so that customers can see result of the validation. > Connector: enable configuration of resource adapter validation log directory > ---------------------------------------------------------------------------- > > Key: WFLY-14266 > URL: https://issues.redhat.com/browse/WFLY-14266 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > > Currently resource-adapter validation logs are not created because report-directory property that IronJacamar uses is always null. The goal of this issue is to implement such config so that customers can see result of the validation. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14266) Connector: enable configuration of resource adapter validation log directory

by Tomasz Adamski (Jira)

Tomasz Adamski created WFLY-14266: ------------------------------------- Summary: Connector: enable configuration of resource adapter validation log directory Key: WFLY-14266 URL: https://issues.redhat.com/browse/WFLY-14266 Project: WildFly Issue Type: Enhancement Components: JCA Reporter: Tomasz Adamski Assignee: Tomasz Adamski -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14258) The first websocket that gets triggered from any deployed war file on server prevents all websockets in all other deployed war files from working

by Ronald Feicht (Jira)

[ https://issues.redhat.com/browse/WFLY-14258?page=com.atlassian.jira.plugi... ] Ronald Feicht commented on WFLY-14258: -------------------------------------- When you click the Push button it should also show a message in the javascript console and of course in the message tab of the websocket entry of the browser's developer tools -> network. While debugging I could see the websocket's id which indicates it was created but it does not process any messages leading me to assume it may be closed? > The first websocket that gets triggered from any deployed war file on server prevents all websockets in all other deployed war files from working > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-14258 > URL: https://issues.redhat.com/browse/WFLY-14258 > Project: WildFly > Issue Type: Bug > Components: JSF, Web Sockets > Reporter: Ronald Feicht > Assignee: Farah Juma > Priority: Major > Attachments: ws1.tar.gz, ws2.tar.gz > > > *Two* war files are deployed on the same Wildfly instance and both use websockets. The *first* page with f:websocket that gets loaded by the browser works perfectly well. Any websocket on any other page of the *same* war file also works perfectly well. Yet, any websocket of the *second* war file will not work until the server is restartet. Then the first page with a websocket that gets loaded determines which war file's websockets will work. > Example: > # WS1/index.xhtml --> websocket works > # WS2/index.xhtml --> websocket does not work (because it seems to be closed on the server side?) > # restart Wildfly > # WS2/index.xhtml --> websocket works > # WS1/index.xhtml --> websocket does not work (because it seems to be closed on the server side?) > # if we had a WS3/index.xhtml its websockets would also not work > issue found on: Mojarra 2.3.9.SP11 on WildFly Full 20.0.1.Final (WildFly Core 12.0.3.Final) > Example war files attached for you to easily confirm this issue: > ws1.tar.gz > ws2.tar.gz > > Created the same bug report here because I cannot tell whether the bug is in Mojarra or the Wildfly integration of Mojarra: [https://github.com/eclipse-ee4j/mojarra/issues/4799] -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 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 2021