October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11198) Session draining on stopped worker won'

by Jan Kašík (Jira)

[ https://issues.jboss.org/browse/WFLY-11198?page=com.atlassian.jira.plugin... ] Jan Kašík updated WFLY-11198: ----------------------------- Summary: Session draining on stopped worker won' (was: Session draining on stopped worker won;') > Session draining on stopped worker won' > --------------------------------------- > > Key: WFLY-11198 > URL: https://issues.jboss.org/browse/WFLY-11198 > Project: WildFly > Issue Type: Bug > Reporter: Jan Kašík > Assignee: Jason Greene > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11198) Session draining on stopped worker won'

by Jan Kašík (Jira)

[ https://issues.jboss.org/browse/WFLY-11198?page=com.atlassian.jira.plugin... ] Jan Kašík reassigned WFLY-11198: -------------------------------- Assignee: Radoslav Husar (was: Jason Greene) > Session draining on stopped worker won' > --------------------------------------- > > Key: WFLY-11198 > URL: https://issues.jboss.org/browse/WFLY-11198 > Project: WildFly > Issue Type: Bug > Reporter: Jan Kašík > Assignee: Radoslav Husar > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3061) [DMN Designer] Automatic Layout Feature

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3061?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3061: ------------------------------------- [~roger600] Hello, thanks for the update, one comment from my site, could you please add task for ??even could be the case the elements must be resized?? and link it to this DROOLS-3061 epic? Thanks! > [DMN Designer] Automatic Layout Feature > --------------------------------------- > > Key: DROOLS-3061 > URL: https://issues.jboss.org/browse/DROOLS-3061 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > DMN Designer should *autolayout* new imported DMN models. The *autolayout* should position DRG diagram nodes into horizontal layers to minimize crossing of connectors with respect of *Top-Down* importance. It means if nodes *Layer B* are inputs for nodes in *Layer A* then the *Layer B* will be below *Layer A*. The *autolayout* should also try to minimize scrolling needed to see whole DRG diagram. > User should also have possibility to invoke *autolayout* feature any time during designing the diagram. In this case the action should be undoable with the *Undo* toolbar button. > The approach used to achieve this is the Sugiyama Method, which is done in 4 steps. Each step have its own set of algorithms. For each step, we selected one of the available algorithms to implement, based on our current needs and time to develop: > *Step 1 - Cycle breaking:* We break cycles in diagram by reversing some edges (they are de-reversed in the end). This step are required because we need ending points in step 2 while sweeping through graph; > *Step 2 - Layering:* We sweep through graph (diagram) and put each node (vertex) in a layer, based on it's distance from others node. For edges that crosses multiple layers, we create virtual vertices connecting those. They are removed at the end. > This approach usually puts the start nodes at the top and the deepest nodes at the end. In the current implementation we're using Longest Path algorithm. A better approach can be developed in future using Network Simplex; > *Step 3 - Node Ordering:* We order each node (vertex) inside its layers in order to reduce crossing, using median. Another approach that can be used is barycenter. > *Step 4 - Node Positioning:* We de-reverse nodes reversed in step 1 and remove virtual nodes reconnecting the concrete nodes. Then we calculate the position of each node. This step can be divided in two steps: one for horizontal position and other for vertical for better positioning. Currently we're using a simple approach: every block of nodes inside the layers is centered and the distance between layers is the same. So it will produce results like the attachment "Automatic Layout Demo". > *Architecture* > From the design of view the goals are: > * +Layout Public interface & DMN implementation+ > ** The goal for this API is to provide the layout declaration data for an input Graph (DMN, BPMN, etc) instance. It will NOT mutate the graph structure and/or data at all. This way it will provide methods for calculating the candidate locations for the graph elements. even could be the case the elements must be resized as well, and it returns on some result data object that specifies the necessary updates to be done on the elements. So the resulting layout data will be consumed by another component that will use the _command API_ in order to perform the necessary updates (location, size) for the graph' elements. > ** Build a well defined layout API (shared) on some _api_ module > ** Build the requested layout implementation specific for DMN inside some DMN shared module (considering the implementation is shared between client and server) > ** Any other common or base classes can be placed inside the _commons_ module > * +Designer integration+ > ** Once having the layout API and implementations, next step is to consume this API in order to obtain the layout data and use it to mutate the graph structure. So we need some kind of component for this, for example we can name it as _LayoutExecutor_. > ** Create some default layout executor which will consume the layout API and use the command API to perform the updates on the model (graph) via "commands", this way we can undo/redo all the operations on the designer > ** [Optional] This designer integration can be done as generic, and so reuse it for other domains like BPMN, or just specific for DMN -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-458) Upgrade Clusters to OpenShift 3.11

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-458?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-458: ------------------------------------------ Sprint: Kiali Sprint #12 > Upgrade Clusters to OpenShift 3.11 > ---------------------------------- > > Key: SWSQE-458 > URL: https://issues.jboss.org/browse/SWSQE-458 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AG-96) Exception sorter functionality

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-96?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-96. ----------------------------- Resolution: Done > Exception sorter functionality > ------------------------------ > > Key: AG-96 > URL: https://issues.jboss.org/browse/AG-96 > Project: Agroal > Issue Type: Enhancement > Components: pool > Reporter: Jesper Pedersen > Assignee: Luis Barreiro > Priority: Major > > It should be possible to register an exception sorter that determines if a SQLException is fatal for the connection, and hence should be flushed upon return to the pool -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11171) Test in Elytron integration tests rely on the BatchPermission in wildfly-jberet

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11171?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-11171: -------------------------------------- [~dlofthouse] If we have the {{org.wildfly.extension.batch.jberet.deployment.BatchPermission}} extend the new permission, say {{org.jberet.BatchPermission}}, will using the old permission name still work? I'm not sure how inheritance with permissions work. > Test in Elytron integration tests rely on the BatchPermission in wildfly-jberet > ------------------------------------------------------------------------------- > > Key: WFLY-11171 > URL: https://issues.jboss.org/browse/WFLY-11171 > Project: WildFly > Issue Type: Bug > Components: Batch, Test Suite > Reporter: James Perkins > Assignee: Cheng Fang > Priority: Major > > Tests in the Elytron integration test suite rely on {{org.wildfly.extension.batch.jberet.deployment.BatchPermission}} which is in private module. This permission should likely be moved to a public JBeret API or a new public API should be create within WildFly that exposes this permission. There is a chance this permission may be required for users. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11171) Test in Elytron integration tests rely on the BatchPermission in wildfly-jberet

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-11171?page=com.atlassian.jira.plugin... ] Cheng Fang commented on WFLY-11171: ----------------------------------- BatchPermission class in current repo: https://github.com/wildfly/wildfly/blob/master/batch-jberet/src/main/java... Sounds good. This permission class is also useful in JBeret SE applications so we may consider moving it to some JBeret api module. > Test in Elytron integration tests rely on the BatchPermission in wildfly-jberet > ------------------------------------------------------------------------------- > > Key: WFLY-11171 > URL: https://issues.jboss.org/browse/WFLY-11171 > Project: WildFly > Issue Type: Bug > Components: Batch, Test Suite > Reporter: James Perkins > Assignee: Cheng Fang > Priority: Major > > Tests in the Elytron integration test suite rely on {{org.wildfly.extension.batch.jberet.deployment.BatchPermission}} which is in private module. This permission should likely be moved to a public JBeret API or a new public API should be create within WildFly that exposes this permission. There is a chance this permission may be required for users. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AG-99) Enforce setting "max size"

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-99?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-99. ----------------------------- Resolution: Done > Enforce setting "max size" > -------------------------- > > Key: AG-99 > URL: https://issues.jboss.org/browse/AG-99 > Project: Agroal > Issue Type: Bug > Components: api > Affects Versions: 1.2 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.3 > > > The default value for {{maxSize}} is {{java.lang.Integer#MAX_VALUE}} which can lead to the database rejecting connections (for apparently no good reason). > The {{maxSize}} attribute should be made mandatory. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11193) Upgrade Hibernate ORM from 5.3.6 to 5.3.7

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11193?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-11193: -------------------------------------- The diff looks okay to me https://github.com/hibernate/hibernate-orm/compare/5.3.6...5.3.7. The large chunks are tests. The other bug fixes don't look like they have much risk. > Upgrade Hibernate ORM from 5.3.6 to 5.3.7 > ----------------------------------------- > > Key: WFLY-11193 > URL: https://issues.jboss.org/browse/WFLY-11193 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Gail Badner > Priority: Blocker > Fix For: 15.0.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11197) The bean-validation subsystem should provide a capability; other subsystems should check for it before using classes

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11197: --------------------------------------- Summary: The bean-validation subsystem should provide a capability; other subsystems should check for it before using classes Key: WFLY-11197 URL: https://issues.jboss.org/browse/WFLY-11197 Project: WildFly Issue Type: Enhancement Components: Bean Validation, JPA / Hibernate, JSF Reporter: Brian Stansberry Assignee: Brian Stansberry JPA and JSF should not use BeanValidationAttachments.VALIDATOR_FACTORY without first checking for a capability. This will allow JPA and JSF to make their dependencies on the org.wildfly.extension.bean-validation module be optional, which will allow Galleon to skip provisioning the module (and its dependencies) if the subsystem is not configured. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 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