March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13253) CommandDispatcher cannot optimize marshalling of user commands

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13253: ----------------------------------- Summary: CommandDispatcher cannot optimize marshalling of user commands Key: WFLY-13253 URL: https://issues.redhat.com/browse/WFLY-13253 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 19.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, all CommandDispatcher instances created from a given CommandDispatcherFactory share a single marshaller. This means that the marshaller used by WF for its internal commands is the same as the one used to marshal user commands. This limits the extent to which commands may optimize their marshalling, or indeed, use a different marshaller (e.g. ProtoStream). We can remove the limitations above by using a distinct mashaller for each CommandDispatcher. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4875) Provide common capability for Remoting connectors

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFCORE-4875?page=com.atlassian.jira.plug... ] Richard Achmatowicz updated WFCORE-4875: ---------------------------------------- Description: The EJB3 subsystem has an element <remote/> which performs a few different functions relating to external clients accessing EJBs on the server: * sets up a Remoting connector service so that external clients may connect to the server using EJB / Remoting or EJB / HTTP Upgrade / Remoting * sets up client mappings entries for those remote clients which are used in topology updates to allow the client to find the server's connectors The Remoting subsystem has two connector types which may be supplied to the <remote connector-ref/> attribute. <connector name="remoting-connector"/> represents a Remoting endpoint and <http-connector name="http-connector"/> represents an Undertow listener which may be used with HTTP Upgrade. At present, in the Remoting subsystem, these connectors have two separately defined capabilities: // for <connector/> private static final String CONNECTOR_CAPABILITY_NAME ="org.wildfly.remoting.connector"; static final RuntimeCapability<Void> CONNECTOR_CAPABILITY = RuntimeCapability.Builder.of(CONNECTOR_CAPABILITY_NAME, true).build(); // for <http-connector/> private static final String HTTP_CONNECTOR_CAPABILITY_NAME = "org.wildfly.remoting.http-connector"; static final RuntimeCapability<Void> HTTP_CONNECTOR_CAPABILITY = RuntimeCapability.Builder.of(HTTP_CONNECTOR_CAPABILITY_NAME, true).build(); The proposal here is to allow referencing both connectors using a single capability base name, "org.wildfly.remoting.connector" to simplify specification of the capabilities which the <remote/> element needs (i.e. it may depend on one or the other). These are both dynamically named capabilities, so their names will vary based on the name of the management resource instance they represent. Because capability names are considered public API, the existing capability name for org.wildfly.remoting.http-connector cannot be removed to further simplify. was: The EJB3 subsystem has an element <remote/> which performs a few different functions relating to external clients accessing EJBs on the server: * sets up a Remoting connector service so that external clients may connect to the server using EJB / Remoting or EJB / HTTP Upgrade / Remoting * sets up client mappings entries for those remote clients which are used in topology updates to allow the client to find the server's connectors The Remoting subsystem has two connector types which may be supplied to the <remote connector-ref/> attribute. <connector name="remoting-connector"/> represents a Remoting endpoint and <http-connector name="http-connector"/> represents an Undertow listener which may be used with HTTP Upgrade. At present, in the Remoting subsystem, these connectors have two separately defined capabilities: // for <connector/> private static final String CONNECTOR_CAPABILITY_NAME ="org.wildfly.remoting.connector"; static final RuntimeCapability<Void> CONNECTOR_CAPABILITY = RuntimeCapability.Builder.of(CONNECTOR_CAPABILITY_NAME, true).build(); // for <http-connector/> private static final String HTTP_CONNECTOR_CAPABILITY_NAME = "org.wildfly.remoting.http-connector"; static final RuntimeCapability<Void> HTTP_CONNECTOR_CAPABILITY = RuntimeCapability.Builder.of(HTTP_CONNECTOR_CAPABILITY_NAME, true).build(); The proposal here is to allow referencing both connectors using a single capability base name, "org.wildfly.remoting.connector" to simplify specification of the capabilities which the <remote/> element needs (i.e. it may depend on one or the other). > Provide common capability for Remoting connectors > ------------------------------------------------- > > Key: WFCORE-4875 > URL: https://issues.redhat.com/browse/WFCORE-4875 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Affects Versions: 11.0.0.Final > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 11.0.1.Final > > > The EJB3 subsystem has an element <remote/> which performs a few different functions relating to external clients accessing EJBs on the server: > * sets up a Remoting connector service so that external clients may connect to the server using EJB / Remoting or EJB / HTTP Upgrade / Remoting > * sets up client mappings entries for those remote clients which are used in topology updates to allow the client to find the server's connectors > The Remoting subsystem has two connector types which may be supplied to the <remote connector-ref/> attribute. <connector name="remoting-connector"/> represents a Remoting endpoint and <http-connector name="http-connector"/> represents an Undertow listener which may be used with HTTP Upgrade. > At present, in the Remoting subsystem, these connectors have two separately defined capabilities: > // for <connector/> > private static final String CONNECTOR_CAPABILITY_NAME ="org.wildfly.remoting.connector"; > static final RuntimeCapability<Void> CONNECTOR_CAPABILITY = RuntimeCapability.Builder.of(CONNECTOR_CAPABILITY_NAME, true).build(); > // for <http-connector/> > private static final String HTTP_CONNECTOR_CAPABILITY_NAME = "org.wildfly.remoting.http-connector"; > static final RuntimeCapability<Void> HTTP_CONNECTOR_CAPABILITY = RuntimeCapability.Builder.of(HTTP_CONNECTOR_CAPABILITY_NAME, true).build(); > The proposal here is to allow referencing both connectors using a single capability base name, "org.wildfly.remoting.connector" to simplify specification of the capabilities which the <remote/> element needs (i.e. it may depend on one or the other). These are both dynamically named capabilities, so their names will vary based on the name of the management resource instance they represent. Because capability names are considered public API, the existing capability name for org.wildfly.remoting.http-connector cannot be removed to further simplify. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4681) Add Phase entries for Microprofile OpenAPI Extension

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4681?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4681: ------------------------------------- Issue Type: Task (was: Feature Request) > Add Phase entries for Microprofile OpenAPI Extension > ---------------------------------------------------- > > Key: WFCORE-4681 > URL: https://issues.redhat.com/browse/WFCORE-4681 > Project: WildFly Core > Issue Type: Task > Components: Server > Affects Versions: 10.0.0.Final > Reporter: Michael Edgar > Assignee: Jeff Mesnil > Priority: Major > Fix For: 11.0.0.Beta1, 11.0.0.Final > > > Add the following entries to {{Phase}} and bump Jandex version to 2.1.1.Final, required by SmallRye OpenAPI implementation. > {code:java}public static final int DEPENDENCIES_MICROPROFILE_OPENAPI = 0x1890; > public static final int POST_MODULE_MICROPROFILE_OPENAPI = 0x3790;{code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4701) SecurityCommandsTestCase and SyslogAuditLogTestCase cleanup

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4701?page=com.atlassian.jira.plug... ] Brian Stansberry reopened WFCORE-4701: -------------------------------------- Resetting to Resolved to allow .Final release processing. > SecurityCommandsTestCase and SyslogAuditLogTestCase cleanup > ----------------------------------------------------------- > > Key: WFCORE-4701 > URL: https://issues.redhat.com/browse/WFCORE-4701 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > Fix For: 11.0.0.Beta1 > > > SecurityCommandsTestCase and SyslogAuditLogTestCase cleanup > Removal of unused or logically dead code -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4701) SecurityCommandsTestCase and SyslogAuditLogTestCase cleanup

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4701?page=com.atlassian.jira.plug... ] Brian Stansberry resolved WFCORE-4701. -------------------------------------- Resolution: Done > SecurityCommandsTestCase and SyslogAuditLogTestCase cleanup > ----------------------------------------------------------- > > Key: WFCORE-4701 > URL: https://issues.redhat.com/browse/WFCORE-4701 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > Fix For: 11.0.0.Beta1 > > > SecurityCommandsTestCase and SyslogAuditLogTestCase cleanup > Removal of unused or logically dead code -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13031) EAP quickstart 'messaging-clustering-singleton' shows errors after import

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13031?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13031: ----------------------------------------- Reopening to move back to Resolved state. We close issues when a Final release with the fix is done. > EAP quickstart 'messaging-clustering-singleton' shows errors after import > ------------------------------------------------------------------------- > > Key: WFLY-13031 > URL: https://issues.redhat.com/browse/WFLY-13031 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 18.0.1.Final > Reporter: Zbyněk Červinka > Assignee: Parul Sharma > Priority: Major > Fix For: 19.0.0.Beta2 > > Attachments: Problems view.png, Project Explorer.png, jboss-ejb3.xml file.png > > > h1. EAP quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import: > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13031) EAP quickstart 'messaging-clustering-singleton' shows errors after import

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13031?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFLY-13031: ------------------------------------- > EAP quickstart 'messaging-clustering-singleton' shows errors after import > ------------------------------------------------------------------------- > > Key: WFLY-13031 > URL: https://issues.redhat.com/browse/WFLY-13031 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 18.0.1.Final > Reporter: Zbyněk Červinka > Assignee: Parul Sharma > Priority: Major > Fix For: 19.0.0.Beta2 > > Attachments: Problems view.png, Project Explorer.png, jboss-ejb3.xml file.png > > > h1. EAP quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import: > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13031) EAP quickstart 'messaging-clustering-singleton' shows errors after import

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13031?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-13031. ------------------------------------- Resolution: Done > EAP quickstart 'messaging-clustering-singleton' shows errors after import > ------------------------------------------------------------------------- > > Key: WFLY-13031 > URL: https://issues.redhat.com/browse/WFLY-13031 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 18.0.1.Final > Reporter: Zbyněk Červinka > Assignee: Parul Sharma > Priority: Major > Fix For: 19.0.0.Beta2 > > Attachments: Problems view.png, Project Explorer.png, jboss-ejb3.xml file.png > > > h1. EAP quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import: > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5173) Can't create a child field under Data Types

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5173?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5173: ----------------------------------- Writer: Stetson Robinson > Can't create a child field under Data Types > ------------------------------------------- > > Key: DROOLS-5173 > URL: https://issues.redhat.com/browse/DROOLS-5173 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final, 7.34.0.Final > Reporter: xiaodong zhang > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Fix For: 7.34.0.Final > > Attachments: 1111.png > > > Can't create a child field under Data Types -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5173) Can't create a child field under Data Types

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5173?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-5173: ---------------------------------------- {{bbb}} needs to be defined as a type _structure_ to be able to add child fields. > Can't create a child field under Data Types > ------------------------------------------- > > Key: DROOLS-5173 > URL: https://issues.redhat.com/browse/DROOLS-5173 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final, 7.34.0.Final > Reporter: xiaodong zhang > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Fix For: 7.34.0.Final > > Attachments: 1111.png > > > Can't create a child field under Data Types -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 March 2020