May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10347) Workmanager persistence is not in xsd order

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10347?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-10347: --------------------------------------- Assignee: Brian Stansberry (was: Stefano Maestri) > Workmanager persistence is not in xsd order > ------------------------------------------- > > Key: WFLY-10347 > URL: https://issues.jboss.org/browse/WFLY-10347 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > The JcaExtension.writeWorkManagers method is not ensuring that ordering of xml elements follows the xsd order. Persisters should follow the xsd as the ensures consistent output. > There are two issues: > 1) The 'default-work-manager' element will only go first if the name of the first wm in the model is 'default'. If the one with that name is 2nd or later, the element will be below some 'work-manager' elements. > 2) The short-running-threads element will only be before long-running-threads if the child resources happen to be ordered that way. This one is easy to correct as the persister is using a for loop when it could simply be checking for the existence of the pool resources. > This kind of thing becomes more significant as we move to galleon for generating configs instead of hand coding them. The potential for resources getting added into the model in a different order than the xsd is higher. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10348) Picketlink federation XML writer should not rely on the ordering in the ModelNode

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFLY-10348: ---------------------------------------- Summary: Picketlink federation XML writer should not rely on the ordering in the ModelNode Key: WFLY-10348 URL: https://issues.jboss.org/browse/WFLY-10348 Project: WildFly Issue Type: Bug Components: Security Reporter: Alexey Loubyansky Assignee: Darran Lofthouse AFAICS, FederationSubsystemWriter is relying on the ordering of the children of the root ModelNode when persisting the subsystem configuration. If one was to create a configuration using management operations from scratch, the operations would have to be ordered according to the order of the corresponding elements defined in the XSD schema. Which is not very practical and increases the chance of getting errors that could be avoided by making the writer persist the elements in the valid order. E.g. in the current implementation if a management operation configuring key-store appeared after the one(s) configuring service-providers the resulting subsystem XML would be invalid according to the XSD. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10347) Workmanager persistence is not in xsd order

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10347: --------------------------------------- Summary: Workmanager persistence is not in xsd order Key: WFLY-10347 URL: https://issues.jboss.org/browse/WFLY-10347 Project: WildFly Issue Type: Bug Components: JCA Reporter: Brian Stansberry Assignee: Stefano Maestri Priority: Minor The JcaExtension.writeWorkManagers method is not ensuring that ordering of xml elements follows the xsd order. Persisters should follow the xsd as the ensures consistent output. There are two issues: 1) The 'default-work-manager' element will only go first if the name of the first wm in the model is 'default'. If the one with that name is 2nd or later, the element will be below some 'work-manager' elements. 2) The short-running-threads element will only be before long-running-threads if the child resources happen to be ordered that way. This one is easy to correct as the persister is using a for loop when it could simply be checking for the existence of the pool resources. This kind of thing becomes more significant as we move to galleon for generating configs instead of hand coding them. The potential for resources getting added into the model in a different order than the xsd is higher. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

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: -------------------------------- Description: 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 was: 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 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 > 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: 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3811) Upgrade to WildFly Galleon Plugins 1.0.0.Alpha20

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-3811: ----------------------------------------- Summary: Upgrade to WildFly Galleon Plugins 1.0.0.Alpha20 Key: WFCORE-3811 URL: https://issues.jboss.org/browse/WFCORE-3811 Project: WildFly Core Issue Type: Task Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky 1.0.0.Alpha20 eliminates the need for the change committed in WFCORE-3808. The maven plugin building the feature-pack properly attaches the feature-archive as a project artifact. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

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: ------------------------------------- [~dzonca] [~anbaker] Created this jira to cover design work. > 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: 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 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, 2 months

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: -------------------------------- Description: 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 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 was: As Aimee or Cameron I want to: * Easily create a test scenario template so that I can define test scenarios. * Concisely express test scenario steps (through the use of variable/data object placeholders) so that I can run a test simulation. * Get started with basic task scenario creation, with minimal engagement from IT. * Better understand the business ecosystem as it related to scenario simulation. > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Enhancement > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: 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 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, 2 months

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: -------------------------------- Issue Type: Task (was: Enhancement) > 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: 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 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, 2 months

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: -------------------------------- Description: As Aimee or Cameron I want to: * Easily create a test scenario template so that I can define test scenarios. * Concisely express test scenario steps (through the use of variable/data object placeholders) so that I can run a test simulation. * Get started with basic task scenario creation, with minimal engagement from IT. * Better understand the business ecosystem as it related to scenario simulation. was: As Aimee or Cameron I want to: * Easily create test scenarios through the application UI, rather than needing to rely on using text files, spreadsheets, etc. * Get started with basic task scenario creation, with minimal engagement from IT. * Better understand the business ecosystem as it related to scenario simulation. > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Enhancement > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > > As Aimee or Cameron I want to: > * Easily create a test scenario template so that I can define test scenarios. > * Concisely express test scenario steps (through the use of variable/data object placeholders) so that I can run a test simulation. > * Get started with basic task scenario creation, with minimal engagement from IT. > * Better understand the business ecosystem as it related to scenario simulation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10346) Upgrade JBeret from 1.2.4.Final to 1.3.0.Final

by James Perkins (JIRA)

James Perkins created WFLY-10346: ------------------------------------ Summary: Upgrade JBeret from 1.2.4.Final to 1.3.0.Final Key: WFLY-10346 URL: https://issues.jboss.org/browse/WFLY-10346 Project: WildFly Issue Type: Component Upgrade Components: Batch Reporter: James Perkins Assignee: James Perkins Upgrade JBeret to 1.3.0.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 May 2018