July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13718) Update quick start references to "Red Hat Developer Studio" to new name "Red Hat CodeReady Studio"

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-13718?page=com.atlassian.jira.plugi... ] Eduardo Martins moved JBEAP-20009 to WFLY-13718: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13718 (was: JBEAP-20009) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Target Release: (was: 7.backlog.GA) Affects Version/s: (was: 7.2.3.CR1) > Update quick start references to "Red Hat Developer Studio" to new name "Red Hat CodeReady Studio" > -------------------------------------------------------------------------------------------------- > > Key: WFLY-13718 > URL: https://issues.redhat.com/browse/WFLY-13718 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Minor > > Red Hat Developer Studio has been renamed to Red Hat Code Ready Studio. Naming has been updated in the EAP documentation repository. We need to update the quickstart documentation as well. > One instance has a broken link. It looks like an unresolved attribute, but should be investigated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13717) Add expressions for the host/port attributes for the outbound socket binding used for mail

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13717?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13717: ------------------------------------ Description: We should make it easier for people to set the host/port of the remote mail server at runtime without having to edit the configuration. See https://github.com/bstansberry/wildfly/blob/ee-9-feature-pack/ee-9/featur... for a possible equivalent thing for a connection to a remote messaging broker. {code} <?xml version="1.0" encoding="UTF-8"?> <feature-group-spec name="messaging-sockets" xmlns="urn:jboss:galleon:feature-group:1.0"> <feature spec="socket-binding-group.remote-destination-outbound-socket-binding"> <param name="remote-destination-outbound-socket-binding" value="messaging-activemq"/> <param name="host" value="${jboss.messaging.connector.host:localhost}"/> <param name="port" value="${jboss.messaging.connector.port:61616}"/> </feature> </feature-group-spec> {code} was:We should make it easier for people to set the host/port of the remote mail server at runtime without having to edit the configuration. See https://github.com/bstansberry/wildfly/blob/ee-9-feature-pack/ee-9/featur... for a possible equivalent thing for a connection to a remote messaging broker. > Add expressions for the host/port attributes for the outbound socket binding used for mail > ------------------------------------------------------------------------------------------ > > Key: WFLY-13717 > URL: https://issues.redhat.com/browse/WFLY-13717 > Project: WildFly > Issue Type: Enhancement > Components: Mail > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Priority: Major > Fix For: 21.0.0.Beta1 > > > We should make it easier for people to set the host/port of the remote mail server at runtime without having to edit the configuration. See https://github.com/bstansberry/wildfly/blob/ee-9-feature-pack/ee-9/featur... for a possible equivalent thing for a connection to a remote messaging broker. > {code} > <?xml version="1.0" encoding="UTF-8"?> > <feature-group-spec name="messaging-sockets" xmlns="urn:jboss:galleon:feature-group:1.0"> > <feature spec="socket-binding-group.remote-destination-outbound-socket-binding"> > <param name="remote-destination-outbound-socket-binding" value="messaging-activemq"/> > <param name="host" value="${jboss.messaging.connector.host:localhost}"/> > <param name="port" value="${jboss.messaging.connector.port:61616}"/> > </feature> > </feature-group-spec> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13717) Add expressions for the host/port attributes for the outbound socket binding used for mail

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13717: --------------------------------------- Summary: Add expressions for the host/port attributes for the outbound socket binding used for mail Key: WFLY-13717 URL: https://issues.redhat.com/browse/WFLY-13717 Project: WildFly Issue Type: Enhancement Components: Mail Reporter: Brian Stansberry Assignee: Yeray Borges Santana Fix For: 21.0.0.Beta1 We should make it easier for people to set the host/port of the remote mail server at runtime without having to edit the configuration. See https://github.com/bstansberry/wildfly/blob/ee-9-feature-pack/ee-9/featur... for a possible equivalent thing for a connection to a remote messaging broker. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5072) Allow easy use of a Jakarta EE 9 variant of org.glassfish:jakarta-json

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5072?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5072: ------------------------------------- Fix Version/s: 13.0.0.Beta3 > Allow easy use of a Jakarta EE 9 variant of org.glassfish:jakarta-json > ---------------------------------------------------------------------- > > Key: WFCORE-5072 > URL: https://issues.redhat.com/browse/WFCORE-5072 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Labels: EE9 > Fix For: 13.0.0.Beta3 > > > Add an element equivalent to what we do for javax.* in https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/com... for the jakarta.* package namespace. > This has no effect when an EE 8 variant of the jar is used as the jakarta package does not exist. But having it in the module.xml makes it easy to swap in an EE9 variant of the jar. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5072) Allow easy use of a Jakarta EE 9 variant of org.glassfish:jakarta-json

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-5072: ---------------------------------------- Summary: Allow easy use of a Jakarta EE 9 variant of org.glassfish:jakarta-json Key: WFCORE-5072 URL: https://issues.redhat.com/browse/WFCORE-5072 Project: WildFly Core Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Add an element equivalent to what we do for javax.* in https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/com... for the jakarta.* package namespace. This has no effect when an EE 8 variant of the jar is used as the jakarta package does not exist. But having it in the module.xml makes it easy to swap in an EE9 variant of the jar. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5072) Allow easy use of a Jakarta EE 9 variant of org.glassfish:jakarta-json

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5072?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5072: ------------------------------------- Labels: EE9 (was: ) > Allow easy use of a Jakarta EE 9 variant of org.glassfish:jakarta-json > ---------------------------------------------------------------------- > > Key: WFCORE-5072 > URL: https://issues.redhat.com/browse/WFCORE-5072 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Labels: EE9 > > Add an element equivalent to what we do for javax.* in https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/com... for the jakarta.* package namespace. > This has no effect when an EE 8 variant of the jar is used as the jakarta package does not exist. But having it in the module.xml makes it easy to swap in an EE9 variant of the jar. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5553) In DMNContextFPAImpl getMetadata returns always a new object

by Jacopo Rota (Jira)

Jacopo Rota created DROOLS-5553: ----------------------------------- Summary: In DMNContextFPAImpl getMetadata returns always a new object Key: DROOLS-5553 URL: https://issues.redhat.com/browse/DROOLS-5553 Project: Drools Issue Type: Bug Reporter: Jacopo Rota Assignee: Jacopo Rota Since the method getMetadata in DMNContextFPAImpl is returning every time a new object, the consumer that is setting a property in the metadata (like the kogito tracing addon that is storing the execution id) can not retrieve it back. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5552) An accumulate with more than one binding is wrongly generated in the executable model

by Martin Weiler (Jira)

Martin Weiler created DROOLS-5552: ------------------------------------- Summary: An accumulate with more than one binding is wrongly generated in the executable model Key: DROOLS-5552 URL: https://issues.redhat.com/browse/DROOLS-5552 Project: Drools Issue Type: Bug Reporter: Martin Weiler Assignee: Mario Fusco Reproducer {code:java} @Test public void testAccumulateWithManyBindings() { String str = "import " + Person.class.getCanonicalName() + ";\n" + "rule R when\n" + " accumulate (\n" + " Person($age : age, $name : name), $max : max( $name.length() ) " + " )" + "then\n" + " insert($max);\n" + "end"; KieSession ksession = getKieSession( str ); ksession.insert( new Person( "Mario", 40 ) ); ksession.insert( new Person( "Mark", 40 ) ); ksession.insert( new Person( "Luca", 40 ) ); ksession.fireAllRules(); List<Number> results = getObjectsIntoList(ksession, Number.class); assertEquals(1, results.size()); assertEquals(5, results.get(0).intValue()); }{code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13716) Integration tests for Elytron failover-realm

by Ondrej Kotek (Jira)

Ondrej Kotek created WFLY-13716: ----------------------------------- Summary: Integration tests for Elytron failover-realm Key: WFLY-13716 URL: https://issues.redhat.com/browse/WFLY-13716 Project: WildFly Issue Type: Task Components: Test Suite Affects Versions: 21.0.0.Beta1 Reporter: Ondrej Kotek Assignee: Ondrej Kotek Implement integration tests for Elytron failover-realm, see WFLY-13146 and WFCORE-4486. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5548) Model compiler cannot generate code for method calls using variable accessors

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5548?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5548: --------------------------------- Sprint: 2020 Week 31-33 (from Jul 27) > Model compiler cannot generate code for method calls using variable accessors > ----------------------------------------------------------------------------- > > Key: DROOLS-5548 > URL: https://issues.redhat.com/browse/DROOLS-5548 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.31.0.Final, 7.32.0.Final, 7.33.0.Final, 7.34.0.Final, 7.35.0.Final, 7.36.0.Final, 7.37.0.Final, 7.38.0.Final, 7.39.0.Final, 7.40.0.Final > Reporter: Ciprian Chiru > Assignee: Luca Molteni > Priority: Major > > Given the example rule below (based on the drools example rule) > > {code:java} > global java.util.Set controlSet; > declare A > x: String > end > declare B > a: A > end > function String dummyFunction(B b) { > return "test"; > } > rule "will execute per each Measurement having ID color" > no-loop > when > Measurement( id == "color", $colorVal : val ) > $b: B() > $val: String() from dummyFunction($b.a) > then > controlSet.add($colorVal); > end{code} > > > When compiling the rule with _kie-maven-plugin_ it fails with : > {noformat} > ...target/generated-sources/drools-model-compiler/main/java/rules/Rules5937a2896da74f01bfa36d294bcf0858RuleMethods0.java:[32,107] cannot find symbol > [ERROR] symbol: variable $b > [ERROR] location: class rules.Rules5937a2896da74f01bfa36d294bcf0858RuleMethods0{noformat} > It transpiles and compiles fine with: > {code:java} > $val: String() from dummyFunction($b){code} > > This can probably be reproduced on all version. > It works when the rules are not pre-compiled. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020