October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10837) IIOP subsystem requires port binding to be defined which was not necessary in prior WFLY versions

by Tomasz Adamski (Jira)

[ https://issues.jboss.org/browse/WFLY-10837?page=com.atlassian.jira.plugin... ] Tomasz Adamski commented on WFLY-10837: --------------------------------------- [~pkremens] I have pushed the PR to upstream. [~brian.stansberry] Thanks for the implementation suggestions - helped me a lot :) > IIOP subsystem requires port binding to be defined which was not necessary in prior WFLY versions > ------------------------------------------------------------------------------------------------- > > Key: WFLY-10837 > URL: https://issues.jboss.org/browse/WFLY-10837 > Project: WildFly > Issue Type: Bug > Components: IIOP > Reporter: Ondra Chaloupka > Assignee: Tomasz Adamski > Priority: Blocker > Fix For: 14.0.0.Final > > > If the {{standalone-*.xml}} configuration defines to use IIOP subsystem but it does not defines the port binding element > {code} > <orb socket-binding="iiop"/> > {code} > The server starts with error > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.iiop-openjdk.orb-service: org.jboss.msc.service.StartException in service jboss.iiop-openjdk.orb-service: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have been configured > at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:150) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have been configured > at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:109) > ... 8 more > {code} > The attribute of the {{socket-binding}} in the model is not defined as {{required}}. > {code} > "socket-binding" => { > "type" => STRING, > "description" => "The name of the socket binding configuration that specifies the ORB port.", > "attribute-group" => "orb", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-constraints" => {"sensitive" => {"socket-binding-ref" => {"type" => "core"}}}, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {code} > Up to that declaring the iiop socket binding was not necessary in WildFly 13.0.0.Final. Could that be a backward compatibility problem too? > Up to that -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3025) [DMN Designer] Data Types - Set a Data Type as a collection Data Type

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3025?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3025: --------------------------------------- Story Points: 5 (was: 3) > [DMN Designer] Data Types - Set a Data Type as a collection Data Type > --------------------------------------------------------------------- > > Key: DROOLS-3025 > URL: https://issues.jboss.org/browse/DROOLS-3025 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: edit-mode-closed.png, interaction.gif > > > - A Data Type must be set as a collection data type; > - Interaction: > !interaction.gif|thumbnail! > - When edit mode is closed, it should show "✔ Yes" for a collection data type and none for a non-collection data type: > !edit-mode-closed.png|thumbnail! > - PatternFly base element for the switch button https://www.patternfly.org/pattern-library/widgets/#bootstrap-switch > h2. Manual acceptance test > - Construct top level item definition > - Use in other structure as list > - Build and deploy > - Interact with kie-server -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3025) [DMN Designer] Data Types - Set a Data Type as a collection Data Type

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3025?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3025: --------------------------------------- Sprint: 2018 Week 42-44 > [DMN Designer] Data Types - Set a Data Type as a collection Data Type > --------------------------------------------------------------------- > > Key: DROOLS-3025 > URL: https://issues.jboss.org/browse/DROOLS-3025 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: edit-mode-closed.png, interaction.gif > > > - A Data Type must be set as a collection data type; > - Interaction: > !interaction.gif|thumbnail! > - When edit mode is closed, it should show "✔ Yes" for a collection data type and none for a non-collection data type: > !edit-mode-closed.png|thumbnail! > - PatternFly base element for the switch button https://www.patternfly.org/pattern-library/widgets/#bootstrap-switch > h2. Manual acceptance test > - Construct top level item definition > - Use in other structure as list > - Build and deploy > - Interact with kie-server -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3137) [DMN Designer] Data Types Type - Constraints - MVP component

by Guilherme Carreiro (Jira)

Guilherme Carreiro created DROOLS-3137: ------------------------------------------ Summary: [DMN Designer] Data Types Type - Constraints - MVP component Key: DROOLS-3137 URL: https://issues.jboss.org/browse/DROOLS-3137 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Carreiro Assignee: Guilherme Carreiro - When the "Add Constraints" check box is selected, the Constraints component must be loaded; - When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component; - When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save); - When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save); - When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11179) Messaging http-acceptor should expose a capability and use it to control dependencies

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11179: --------------------------------------- Summary: Messaging http-acceptor should expose a capability and use it to control dependencies Key: WFLY-11179 URL: https://issues.jboss.org/browse/WFLY-11179 Project: WildFly Issue Type: Bug Components: JMS Reporter: Brian Stansberry Assignee: Jeff Mesnil An HTTPAcceptor brings some config and classloading deps that can probably be better controlled if a capability were used. 1) Once WFCORE-4166 is done a capability requirement can be used for the required HttpListenerRegistryService, which will help ensure config consistency by making the config links clear. 2) If there are any module dependencies the messaging subsystem module has that are only needed to support an HTTPAcceptor, then those can be made optional, and then the RuntimeCapability.Builder.addAdditionalRequiredPackages method can be used to record the requirement for those optional packages if the new capability is present. (Actually, at a glance it looks like the relevant module deps are already optional, so this bit is about telling Galleon when they are required.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4166) HttpListenerRegistryService is not exposed via a capability

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4166?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4166: ------------------------------------- Description: HttpListenerRegistryService.SERVICE_NAME should be deprecated and the remoting subsystem should add a RuntimeCapability that exposes ListenerRegistry. The HttpListenerRegistryService should then be exposed under that capability's ServiceName, with an alias added for the legacy HttpListenerRegistryService.SERVICE_NAME. This will help eliminate a hard dependency on the org.jboss.as.remoting module from the messaging subsystem in full. was: HttpListenerRegistryService.SERVICE_NAME should be deprecated and the remoting subsystem should add a RuntimeCapability the exposes ListenerRegistry. The HttpListenerRegistryService should then be exposed under that capability's ServiceName, with an alias added for the legacy HttpListenerRegistryService.SERVICE_NAME. This will help eliminate a hard dependency on the org.jboss.as.remoting module from the messaging subsystem in full. > HttpListenerRegistryService is not exposed via a capability > ----------------------------------------------------------- > > Key: WFCORE-4166 > URL: https://issues.jboss.org/browse/WFCORE-4166 > Project: WildFly Core > Issue Type: Bug > Components: Management, Remoting > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > HttpListenerRegistryService.SERVICE_NAME should be deprecated and the remoting subsystem should add a RuntimeCapability that exposes ListenerRegistry. The HttpListenerRegistryService should then be exposed under that capability's ServiceName, with an alias added for the legacy HttpListenerRegistryService.SERVICE_NAME. > This will help eliminate a hard dependency on the org.jboss.as.remoting module from the messaging subsystem in full. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3024?page=com.atlassian.jira.plugi... ] Guilherme Carreiro resolved DROOLS-3024. ---------------------------------------- Resolution: Done > [DMN Designer] Data Types - Add nested data types > ------------------------------------------------- > > Key: DROOLS-3024 > URL: https://issues.jboss.org/browse/DROOLS-3024 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, options.png > > > - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu: > !options.png|thumbnail! > h2. Manual Acceptance Test > h3. Insert above > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > - no warning in browser console (/) > h3. Insert below > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > h3. Insert nested > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > h3. Build and deploy > - Build and deploy model that uses new created data type (x) > -- DROOLS-3110 > -- DROOLS-3111 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3024?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3024: --------------------------------------- Sprint: 2018 Week 39-41 (was: 2018 Week 39-41, 2018 Week 42-44) > [DMN Designer] Data Types - Add nested data types > ------------------------------------------------- > > Key: DROOLS-3024 > URL: https://issues.jboss.org/browse/DROOLS-3024 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, options.png > > > - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu: > !options.png|thumbnail! > h2. Manual Acceptance Test > h3. Insert above > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > - no warning in browser console (/) > h3. Insert below > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > h3. Insert nested > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > h3. Build and deploy > - Build and deploy model that uses new created data type (x) > -- DROOLS-3110 > -- DROOLS-3111 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3022) [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3022?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3022: --------------------------------------- Sprint: 2018 Week 39-41 (was: 2018 Week 39-41, 2018 Week 42-44) > [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-3022 > URL: https://issues.jboss.org/browse/DROOLS-3022 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: validation.png > > > The Data Type name must be unique at the level that it's defined; e.g. > - tPerson > -- uuid > -- name > -- city (Structure) > --- uuid > --- name > The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels. > ---- > Prototype: > !validation.png|thumbnail! > h2. Manaul Acceptance Test > - Try to put same name by Typing (/) > - Try to put same name by Copy and paste (/) > - Do not allow empty name (/) > - Allow spaces in name (/) > - Allow multibyte chars in name (/) > - Allow special characters in name (/) > - Allow lower upper case in name (/) > - Save when error shown (/) > - Cancel edit when error shown (/) > - Invoke other edit when error shown (/) > -- https://github.com/kiegroup/kie-wb-common/pull/2161#issuecomment-427978978 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3024?page=com.atlassian.jira.plugi... ] Guilherme Carreiro reopened DROOLS-3024: ---------------------------------------- > [DMN Designer] Data Types - Add nested data types > ------------------------------------------------- > > Key: DROOLS-3024 > URL: https://issues.jboss.org/browse/DROOLS-3024 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, options.png > > > - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu: > !options.png|thumbnail! > h2. Manual Acceptance Test > h3. Insert above > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > - no warning in browser console (/) > h3. Insert below > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > h3. Insert nested > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > h3. Build and deploy > - Build and deploy model that uses new created data type (x) > -- DROOLS-3110 > -- DROOLS-3111 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 October 2018