July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12298) Allow to change RESTEasy settings via CLI

by Ronald Sigal (Jira)

[ https://issues.jboss.org/browse/WFLY-12298?page=com.atlassian.jira.plugin... ] Ronald Sigal moved RESTEASY-2303 to WFLY-12298: ----------------------------------------------- Project: WildFly (was: RESTEasy) Key: WFLY-12298 (was: RESTEASY-2303) Workflow: GIT Pull Request workflow (was: classic default workflow) Fix Version/s: 18.0.0.Beta1 (was: 3.9.0.Final) (was: 4.2.0.Final) > Allow to change RESTEasy settings via CLI > ----------------------------------------- > > Key: WFLY-12298 > URL: https://issues.jboss.org/browse/WFLY-12298 > Project: WildFly > Issue Type: Feature Request > Reporter: Marek Kopecky > Assignee: Ronald Sigal > Priority: Major > Fix For: 18.0.0.Beta1 > > > Many RESTEasy properties can be set in web.xml. CLI should be able to show values of these properties per each deployment by this command: > {noformat} > /deployment=${NAME_OF_DEPLOYMENT}/subsystem=jaxrs:read-resource > {noformat} > CLI should be able to set values of this properties per each deployment: > {noformat} > /deployment=${NAME_OF_DEPLOYMENT}/subsystem=jaxrs:write-attribute(name=resteasy.use.builtin.providers,value=false) > {noformat} > CLI should be able to specify values of this attributes globally for all deployments (global settings override deployment settings): > {noformat} > /subsystem=jaxrs:write-attribute(name=resteasy.media.type.mappings,value="html : text/html, txt : text/plain") > {noformat} > We should consider which properties should be available via CLI. > ---- > Default providers, interceptors, etc. are set in many javax.ws.rs.ext.Providers files in RESTEasy sources: > {noformat} > ./providers/jackson2/src/main/resources/META-INF/services/javax.ws.rs.ext.Providers > ./providers/yaml/src/main/resources/META-INF/services/javax.ws.rs.ext.Providers > ./resteasy-jaxrs/src/main/resources/META-INF/services/javax.ws.rs.ext.Providers > ... > {noformat} > CLI shoud allow to add other providers, interceptors, etc., or disable some in global level for all deployments. CLI should allow to add or disable it for specific deployment. Disabling should have higher priority then allowing. Global settings override deployment settings. > Proposal for CLI attributes (list-add is standard CLI function) - examples: > {noformat} > /subsystem=jaxrs:list-add(name=disabled-providers,value=org.jboss.resteasy.plugins.providers.DataSourceProvider) > /subsystem=jaxrs:list-add(name=allowed-providers,value=org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor) > /deployment=${NAME_OF_DEPLOYMENT}/subsystem=jaxrs:list-add(name=disabled-providers,value=org.jboss.resteasy.plugins.providers.DataSourceProvider) > /deployment=${NAME_OF_DEPLOYMENT}/subsystem=jaxrs:list-add(name=allowed-providers,value=org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor) > {noformat} > ---- > *Example without this RFE:* > Let's say that server admin needs to disable DataSourceProvider for all deployments on server. Now, AFAIK, he needs to: > * set "resteasy.use.builtin.providers" property in web.xml of all deployments to "false" > ** It disable all default providers. > * explicitly set providers used in each deployment by "resteasy.providers" property in web.xml of all deployments > These steps are really uncomfortable, server admin needs to manually update all deployments in server -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-832) Add MongoDB and MySQL options on Bookinfo Job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-832?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-832: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo > Add MongoDB and MySQL options on Bookinfo Job > --------------------------------------------- > > Key: SWSQE-832 > URL: https://issues.jboss.org/browse/SWSQE-832 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > > Add options to remove bookinfo and MySQL option on bookinfo job -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-832) Add MongoDB and MySQL options on Bookinfo Job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-832?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-832: ------------------------------------------ Labels: infrastructure (was: ) Sprint: Kiali Sprint #25 > Add MongoDB and MySQL options on Bookinfo Job > --------------------------------------------- > > Key: SWSQE-832 > URL: https://issues.jboss.org/browse/SWSQE-832 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > > Add options to remove bookinfo and MySQL option on bookinfo job -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-832) Add MongoDB and MySQL options on Bookinfo Job

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-832: --------------------------------------------- Summary: Add MongoDB and MySQL options on Bookinfo Job Key: SWSQE-832 URL: https://issues.jboss.org/browse/SWSQE-832 Project: Kiali QE Issue Type: Task Reporter: Guilherme Baufaker Rêgo Add options to remove bookinfo and MySQL option on bookinfo job -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4306) [DMN Designer] Search feature - Apply UX and enable search feature

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4306?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4306: ------------------------------------ Attachment: prototype.png > [DMN Designer] Search feature - Apply UX and enable search feature > ------------------------------------------------------------------ > > Key: DROOLS-4306 > URL: https://issues.jboss.org/browse/DROOLS-4306 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: prototype.png > > > Update the {{SearchBarComponentView}} and related classes with the expected user experience. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4306) [DMN Designer] Search feature - Apply UX and enable search feature

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4306?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4306: ------------------------------------ Attachment: (was: prototype.png) > [DMN Designer] Search feature - Apply UX and enable search feature > ------------------------------------------------------------------ > > Key: DROOLS-4306 > URL: https://issues.jboss.org/browse/DROOLS-4306 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Update the {{SearchBarComponentView}} and related classes with the expected user experience. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4333) DMN PMML integration wrong lookup when null field name

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-4333: -------------------------------------- Summary: DMN PMML integration wrong lookup when null field name Key: DROOLS-4333 URL: https://issues.jboss.org/browse/DROOLS-4333 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-7418) Batch deployments with a large number of executed jobs can lock up or slow down the web console

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-7418?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-7418: ------------------------------------- Hi [~timonz], unfortunately I've not looked at this in some time as we've not heard of any issues with it. I had just happened to find it during testing with large amounts of batch jobs. At this point the only real workaround I'm aware of is to reduce the number of batch entries. I suppose one option would be to add an option in the subsystem which disables the runtime batch job resources. This would mean batch jobs can't be viewed or restarted from management operations including the web console and CLI, but may be okay for large numbers of batch jobs anyway. > Batch deployments with a large number of executed jobs can lock up or slow down the web console > ----------------------------------------------------------------------------------------------- > > Key: WFLY-7418 > URL: https://issues.jboss.org/browse/WFLY-7418 > Project: WildFly > Issue Type: Enhancement > Components: Batch, Web Console > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Labels: move_to_halnext > > Batch deployments which contain a large number of executed jobs can be extremely slow to process as the {{/deployment=batch.war/subsystem=batch-jberet}} processes each job instance then each job execution of that job instance. > One possibly helpful option for the web console would be to add a new description attribute to indicate the resource may be slow to process. The web console might be able to run a background task to populate data rather than locking up the UI. There would still be an issue with a large memory footprint here however. > JBeret might want to consider having a way to archive jobs too rather than just purge them. Some users may want to keep all job execution data. Archiving this data could reduce the size of the current data being retrieved. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12297) Jakarta EE 8 Certification for WildFly

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12297?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12297: ------------------------------------ Priority: Critical (was: Major) > Jakarta EE 8 Certification for WildFly > -------------------------------------- > > Key: WFLY-12297 > URL: https://issues.jboss.org/browse/WFLY-12297 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Scott Marlow > Priority: Critical > Fix For: 18.0.0.Final > > > Certify WildFly 18 as Jakarta EE 8 compatible. Publish the certification results on https://github.com/wildfly/certifications -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12297) Jakarta EE 8 Certification for WildFly

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12297?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12297: ------------------------------------ Fix Version/s: 18.0.0.Final > Jakarta EE 8 Certification for WildFly > -------------------------------------- > > Key: WFLY-12297 > URL: https://issues.jboss.org/browse/WFLY-12297 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Scott Marlow > Priority: Major > Fix For: 18.0.0.Final > > > Certify WildFly 18 as Jakarta EE 8 compatible. Publish the certification results on https://github.com/wildfly/certifications -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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