June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-193) Java EE 8 Specs BOMs

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/JBEE-193?page=com.atlassian.jira.plugin.s... ] Eduardo Martins commented on JBEE-193: -------------------------------------- Please note that on the submitted PR I did exclude jboss-servlet-api_3.1_spec from jboss-jacc-api_1.5_spec, but I'm not sure if that's the correct approach, perhaps a new release of such spec artifact should refer jboss-servlet-api_4.0_spec instead? > Java EE 8 Specs BOMs > -------------------- > > Key: JBEE-193 > URL: https://issues.jboss.org/browse/JBEE-193 > Project: JBoss JavaEE Spec APIs > Issue Type: Task > Components: jboss-javaee-specs > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > Update the JBoss Java EE Specs BOMs with respect to Java EE 8, to be consumed by projects such as WildFly BOMs and Quickstarts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-193) Java EE 8 Specs BOMs

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/JBEE-193?page=com.atlassian.jira.plugin.s... ] Eduardo Martins updated JBEE-193: --------------------------------- Git Pull Request: https://github.com/jboss/jboss-javaee-specs/pull/8 > Java EE 8 Specs BOMs > -------------------- > > Key: JBEE-193 > URL: https://issues.jboss.org/browse/JBEE-193 > Project: JBoss JavaEE Spec APIs > Issue Type: Task > Components: jboss-javaee-specs > Reporter: Eduardo Martins > Assignee: Scott Marlow > > Update the JBoss Java EE Specs BOMs with respect to Java EE 8, to be consumed by projects such as WildFly BOMs and Quickstarts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-193) Java EE 8 Specs BOMs

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/JBEE-193?page=com.atlassian.jira.plugin.s... ] Eduardo Martins reassigned JBEE-193: ------------------------------------ Assignee: Eduardo Martins (was: Scott Marlow) > Java EE 8 Specs BOMs > -------------------- > > Key: JBEE-193 > URL: https://issues.jboss.org/browse/JBEE-193 > Project: JBoss JavaEE Spec APIs > Issue Type: Task > Components: jboss-javaee-specs > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > Update the JBoss Java EE Specs BOMs with respect to Java EE 8, to be consumed by projects such as WildFly BOMs and Quickstarts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-193) Java EE 8 Specs BOMs

by Eduardo Martins (JIRA)

Eduardo Martins created JBEE-193: ------------------------------------ Summary: Java EE 8 Specs BOMs Key: JBEE-193 URL: https://issues.jboss.org/browse/JBEE-193 Project: JBoss JavaEE Spec APIs Issue Type: Task Components: jboss-javaee-specs Reporter: Eduardo Martins Assignee: Scott Marlow Update the JBoss Java EE Specs BOMs with respect to Java EE 8, to be consumed by projects such as WildFly BOMs and Quickstarts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2593) [Guided Decision Table] Trouble to add a row into table with WI

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2593?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2593: --------------------------------- Sprint: 2018 Week 23-24 > [Guided Decision Table] Trouble to add a row into table with WI > --------------------------------------------------------------- > > Key: DROOLS-2593 > URL: https://issues.jboss.org/browse/DROOLS-2593 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Environment: Firefox or IE11 > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Labels: Regression > > This issue appears just on *firefox* or *internet explorer*. If a table with *Work Item* execution is opened, the attached errors appears. Please notice that the errors differs slightly on *firefox* and *internet explorer*. > h3. Tests > [WebDTWIDTest|https://github.com/jboss-integration/bxms-qe-tests/blob/mast...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10541) default transactions node-identifier to jboss.node.name

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Brad Maxwell updated WFLY-10541: -------------------------------- Description: It is very common for environments to run multiple Wildfly instances on the same machine, it would be good to use 1 property such as jboss.node.name as a default for jboss.tx.node.id / node-identifier and any other property that needs to be unique when Wildfly instances are stacked on a machine. {code} WARN [org.jboss.as.txn] (ServerService Thread Pool -- 36) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. {code} {code} <subsystem xmlns="urn:jboss:domain:transactions:3.0"> <core-environment node-identifier="${jboss.node.name}"> {code} I was thinking messaging also had property that needed to be set but I am not seeing the warning currently. Also I have seen if jboss.node.name is not set, then ejb calls may not work as expected, so it would be good to have it warn if it is not set as well. was: It is very common for environments to run multiple Wildfly instances on the same machine, it would be good to use 1 property such as jboss.node.name as a default for jboss.tx.node.id / node-identifier and any other property that needs to be unique when Wildfly instances are stacked on a machine. {code} WARN [org.jboss.as.txn] (ServerService Thread Pool -- 36) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. {code} {code} <subsystem xmlns="urn:jboss:domain:transactions:3.0"> <core-environment node-identifier="${jboss.node.name}"> {code} > default transactions node-identifier to jboss.node.name > ------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Jason Greene > > It is very common for environments to run multiple Wildfly instances on the same machine, it would be good to use 1 property such as jboss.node.name as a default for jboss.tx.node.id / node-identifier and any other property that needs to be unique when Wildfly instances are stacked on a machine. > {code} > WARN [org.jboss.as.txn] (ServerService Thread Pool -- 36) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > {code} > {code} > <subsystem xmlns="urn:jboss:domain:transactions:3.0"> > <core-environment node-identifier="${jboss.node.name}"> > {code} > I was thinking messaging also had property that needed to be set but I am not seeing the warning currently. Also I have seen if jboss.node.name is not set, then ejb calls may not work as expected, so it would be good to have it warn if it is not set as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10541) default transactions node-identifier to jboss.node.name

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-10541: ----------------------------------- Summary: default transactions node-identifier to jboss.node.name Key: WFLY-10541 URL: https://issues.jboss.org/browse/WFLY-10541 Project: WildFly Issue Type: Enhancement Components: Server Affects Versions: 13.0.0.Final Reporter: Brad Maxwell Assignee: Jason Greene It is very common for environments to run multiple Wildfly instances on the same machine, it would be good to use 1 property such as jboss.node.name as a default for jboss.tx.node.id / node-identifier and any other property that needs to be unique when Wildfly instances are stacked on a machine. {code} WARN [org.jboss.as.txn] (ServerService Thread Pool -- 36) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. {code} {code} <subsystem xmlns="urn:jboss:domain:transactions:3.0"> <core-environment node-identifier="${jboss.node.name}"> {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2532: ------------------------------------- updated walk-thru attached: "DRAFT1.pdf" > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: DRAFT1.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2532: -------------------------------- Attachment: DRAFT1.pdf > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: DRAFT1.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2532: -------------------------------- Attachment: (was: RoundF2.pdf) > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 June 2018