June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4178) [DMN Designer] Selected Node Is selected also in Documentation

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4178: ----------------------------------- Summary: [DMN Designer] Selected Node Is selected also in Documentation Key: DROOLS-4178 URL: https://issues.jboss.org/browse/DROOLS-4178 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.24.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2019-06-13 11-31-38.png User has possibility to export documentation of a dmn diagram. Such documentation contains a picture of the diagram. The issue is the picture has highlighted some nodes, if those were selected in the designer model tab. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4118) [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4118?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4118: -------------------------------- Description: This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class. This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes. This JIRA covers only general information about the diagram, and its visual representation (not including DRD components). h2. Acceptance test Firefox (/) and Chrome (/) - Multiple data types (/) - Data types with constraints (/) - List data types (/) - Connected nodes (/) - Separated nodes (/) - Nodes exceeding canvas size (/) - Fonts (/) - Colors (/) Linux/Windows - Download and open (/) was: This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class. This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes. This JIRA covers only general information about the diagram, and its visual representation (not including DRD components). h2. Acceptance test Firefox (/) and Chrome (/) - Multiple data types (/) - Data types with constraints (/) - List data types (/) - Connected nodes (/) - Separated nodes (/) - Nodes exceeding canvas size (/) - Fonts (/) - Colors (x) Linux/Windows - Download and open (/) > [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-4118 > URL: https://issues.jboss.org/browse/DROOLS-4118 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class. > This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes. > This JIRA covers only general information about the diagram, and its visual representation (not including DRD components). > h2. Acceptance test > Firefox (/) and Chrome (/) > - Multiple data types (/) > - Data types with constraints (/) > - List data types (/) > - Connected nodes (/) > - Separated nodes (/) > - Nodes exceeding canvas size (/) > - Fonts (/) > - Colors (/) > Linux/Windows > - Download and open (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12192) Support for java.util.Optional on PathParam and QueryParam

by Weinan Li (Jira)

[ https://issues.jboss.org/browse/WFLY-12192?page=com.atlassian.jira.plugin... ] Weinan Li moved RESTEASY-2276 to WFLY-12192: -------------------------------------------- Project: WildFly (was: RESTEasy) Key: WFLY-12192 (was: RESTEASY-2276) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: REST (was: jaxrs) Fix Version/s: (was: 4.1.0.Final) (was: 3.8.0.Final) > Support for java.util.Optional on PathParam and QueryParam > ---------------------------------------------------------- > > Key: WFLY-12192 > URL: https://issues.jboss.org/browse/WFLY-12192 > Project: WildFly > Issue Type: Feature Request > Components: REST > Reporter: Claudio Tagliola > Assignee: Weinan Li > Priority: Major > > Currently, PathParam and QueryParam support the following construct (from https://docs.jboss.org/resteasy/docs/3.0.17.Final/userguide/html_single/#...): > {quote}The parameter type you inject into can be any primitive type, a String, or any Java object that has a constructor that takes a String parameter, or a static valueOf method that takes a String as a parameter.{quote} > Proposal is to also support java.util.Optional.ofNullable as a wrapper object for Strings, which is always called. This will eliminate all null checks for optional parameters in resource classes with the different Optional followup methods, such as optional.ifPresent. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12191) StackOverflowError is thrown when invoking a REST end-point, with ClientRequestFilter/ClientResponseFilter registered

by Deny Wuysan (Jira)

Deny Wuysan created WFLY-12191: ---------------------------------- Summary: StackOverflowError is thrown when invoking a REST end-point, with ClientRequestFilter/ClientResponseFilter registered Key: WFLY-12191 URL: https://issues.jboss.org/browse/WFLY-12191 Project: WildFly Issue Type: Bug Components: REST Affects Versions: 17.0.0.Final Environment: Fedora 30, Oracle JDK 1.8.0_181 Reporter: Deny Wuysan Assignee: Alessio Soldano Attachments: Authenticator.java, BatchManager.java Please find attached the two Java files corresponding to the error. When setting debugger on line 50 for Authenticator.java, notice repetitive calls occurred, ONLY on Wildfly 17.0.0.Final. Have re-tested this case on Wildfly 16.0.0.Final and the REST call made successfully. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12048) outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12048?page=com.atlassian.jira.plugin... ] Radoslav Husar reassigned WFLY-12048: ------------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-12048 > URL: https://issues.jboss.org/browse/WFLY-12048 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 16.0.0.Final > Reporter: Wolf-Dieter Fink > Assignee: Radoslav Husar > Priority: Major > > JGroups configuration can use two different ways to configure cluster detection > ------ older configuration is via protocol properties -- > <protocol type="TCPPING"> > <property name="initial_hosts">host[7600]</property> > ------ new configuration via socket reference > <socket-discovery-protocol type="TCPPING" socket-bindings="ref-a ref-b"/> > ... > <outbound-socket-binding name="ref-a"> > <remote-destination host="127.0.0.1" port="7600"/> > </outbound-socket-binding> > ----------- > with the old option it is possible to use an expression to set all hosts in a cluster. > The new one need to have all outbound connections listed which is harder to maintain. > As an administrator I want to have the possibility to group the connections and only have one reference and the number of connections can be vary without changing multiple point in the configuration. > So a configuration like this would enhance that > <outbound-socket-binding-group> > <outbound-socket-binding name="ref-a"> > <remote-destination host="host1" port="7600"/> > </outbound-socket-binding> > <outbound-socket-binding name="ref-b"> > <remote-destination host="host2" port="7600"/> > </outbound-socket-binding> > </outbound-socket-binding-group> -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4459) outbound-socket-binding element should allow grouping which subsystems can reference

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFCORE-4459?page=com.atlassian.jira.plugi... ] Radoslav Husar reassigned WFCORE-4459: -------------------------------------- Assignee: Radoslav Husar (was: Jeff Mesnil) > outbound-socket-binding element should allow grouping which subsystems can reference > ------------------------------------------------------------------------------------ > > Key: WFCORE-4459 > URL: https://issues.jboss.org/browse/WFCORE-4459 > Project: WildFly Core > Issue Type: Feature Request > Components: Server > Affects Versions: 9.0.0.Beta4 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Useful especially for clustering subsystems like jgroups discovery protocols, infinispan hotrod servers, and mod_cluster balancers. > ---- > JGroups configuration can use two different ways to configure cluster detection > ------ older configuration is via protocol properties -- > <protocol type="TCPPING"> > <property name="initial_hosts">host[7600]</property> > ------ new configuration via socket reference > <socket-discovery-protocol type="TCPPING" socket-bindings="ref-a ref-b"/> > ... > <outbound-socket-binding name="ref-a"> > <remote-destination host="127.0.0.1" port="7600"/> > </outbound-socket-binding> > ----------- > with the old option it is possible to use an expression to set all hosts in a cluster. > The new one need to have all outbound connections listed which is harder to maintain. > As an administrator I want to have the possibility to group the connections and only have one reference and the number of connections can be vary without changing multiple point in the configuration. > So a configuration like this would enhance that > <outbound-socket-binding-group> > <outbound-socket-binding name="ref-a"> > <remote-destination host="host1" port="7600"/> > </outbound-socket-binding> > <outbound-socket-binding name="ref-b"> > <remote-destination host="host2" port="7600"/> > </outbound-socket-binding> > </outbound-socket-binding-group> -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4177) Error in compiling BigLiteral binding as literal

by Erik Smith (Jira)

Erik Smith created DROOLS-4177: ---------------------------------- Summary: Error in compiling BigLiteral binding as literal Key: DROOLS-4177 URL: https://issues.jboss.org/browse/DROOLS-4177 Project: Drools Issue Type: Bug Reporter: Erik Smith Assignee: Luca Molteni When beta joining two fields with a BigDecimal or BigInteger field, if a field is assigned as a binding the drools-model-compiler fails the compilation. "import " + Result.class.getCanonicalName() + ";" + "import " + Person.class.getCanonicalName() + ";" + "rule R when\n" + " $r : Result()\n" + " $markV : Person(name == \"Mark\", $markMoney : money)\n" + " $richerV : Person(name != \"Mark\", money > $markMoney)\n" + "then\n" + " $r.setValue($richerV.getName() + \" is richer than \" + $markV.getName());\n" + "end"; -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4176) Error in compiling BigLiteral binding as literal

by Erik Smith (Jira)

Erik Smith created DROOLS-4176: ---------------------------------- Summary: Error in compiling BigLiteral binding as literal Key: DROOLS-4176 URL: https://issues.jboss.org/browse/DROOLS-4176 Project: Drools Issue Type: Bug Reporter: Erik Smith Assignee: Luca Molteni When beta joining two fields with a BigDecimal or BigInteger field, if a field is assigned as a binding the drools-model-compiler fails the compilation. "import " + Result.class.getCanonicalName() + ";" + "import " + Person.class.getCanonicalName() + ";" + "rule R when\n" + " $r : Result()\n" + " $markV : Person(name == \"Mark\", $markMoney : money)\n" + " $richerV : Person(name != \"Mark\", money > $markMoney)\n" + "then\n" + " $r.setValue($richerV.getName() + \" is richer than \" + $markV.getName());\n" + "end"; -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4176) Error in compiling BigLiteral binding as literal

by Erik Smith (Jira)

[ https://issues.jboss.org/browse/DROOLS-4176?page=com.atlassian.jira.plugi... ] Erik Smith deleted DROOLS-4176: ------------------------------- > Error in compiling BigLiteral binding as literal > ------------------------------------------------ > > Key: DROOLS-4176 > URL: https://issues.jboss.org/browse/DROOLS-4176 > Project: Drools > Issue Type: Bug > Reporter: Erik Smith > Assignee: Luca Molteni > Priority: Major > > When beta joining two fields with a BigDecimal or BigInteger field, if a field is assigned as a binding the drools-model-compiler fails the compilation. > "import " + Result.class.getCanonicalName() + ";" + > "import " + Person.class.getCanonicalName() + ";" + > "rule R when\n" + > " $r : Result()\n" + > " $markV : Person(name == \"Mark\", $markMoney : money)\n" + > " $richerV : Person(name != \"Mark\", money > $markMoney)\n" + > "then\n" + > " $r.setValue($richerV.getName() + \" is richer than \" + $markV.getName());\n" + > "end"; -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12190) Reintroduce EJB over HTTP/HTTPS capability with HTTP Loadbalancer - server to server config

by Brad Maxwell (Jira)

Brad Maxwell created WFLY-12190: ----------------------------------- Summary: Reintroduce EJB over HTTP/HTTPS capability with HTTP Loadbalancer - server to server config Key: WFLY-12190 URL: https://issues.jboss.org/browse/WFLY-12190 Project: WildFly Issue Type: Feature Request Components: EJB Reporter: Brad Maxwell Assignee: Flavia Rainone Wildfly/EAP added EJB over HTTP through load balancer, but we missed adding the ability to configure this server to server in the standalone.xml remoting subsystem like the other EJB server to server configs. The remoting outbound connection would need an http option , currently it only allows http*-remoting, remote and remote+http*. {code} /subsystem=remoting/remote-outbound-connection=remote-ejb-connection:write-attribute(name=protocol, value=) http-remoting https-remoting remote remote+http remote+https {code} Also, Undertow defaults to http://host:8080/wildfly-services for the provider URL to be used, the remote-outbound-configuration for http would need to be able to accept the path, as the path can be configured to a different path from wildfly-services. It might be good to default to wildfly-services if no path is specified. {code} /subsystem=undertow/server=default-server/host=default-host/setting=http-invoker:write-attribute(name=path,value=ejbOverHttp) {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019