[JBoss JIRA] (WFCORE-4256) Review the requirement for the modular.jdk.args defined in the pom's
by James Perkins (Jira)
James Perkins created WFCORE-4256:
-------------------------------------
Summary: Review the requirement for the modular.jdk.args defined in the pom's
Key: WFCORE-4256
URL: https://issues.jboss.org/browse/WFCORE-4256
Project: WildFly Core
Issue Type: Task
Components: Test Suite
Reporter: James Perkins
There are test utilities that rely on the {{modular.jdk.args}} to be set in the POM. This could potentially be hiding issues with entry points which should using these parameters. At a minimum we should reduce the places the parameters are used and only use them where required.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11525) Review the requirement for the modular.jdk.args defined in the pom's
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11525?page=com.atlassian.jira.plugin... ]
James Perkins moved WFCORE-4256 to WFLY-11525:
----------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-11525 (was: WFCORE-4256)
Component/s: Test Suite
(was: Test Suite)
> Review the requirement for the modular.jdk.args defined in the pom's
> --------------------------------------------------------------------
>
> Key: WFLY-11525
> URL: https://issues.jboss.org/browse/WFLY-11525
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Reporter: James Perkins
> Priority: Major
>
> There are test utilities that rely on the {{modular.jdk.args}} to be set in the POM. This could potentially be hiding issues with entry points which should using these parameters. At a minimum we should reduce the places the parameters are used and only use them where required.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3406) [DMN Designer] Decision Service splitter should be movable
by Roger Martínez (Jira)
[ https://issues.jboss.org/browse/DROOLS-3406?page=com.atlassian.jira.plugi... ]
Roger Martínez edited comment on DROOLS-3406 at 12/17/18 5:24 PM:
------------------------------------------------------------------
Hey [~manstis]
Well probably I'm still not familiar with this things you're doing and the issues behind, as we never did something like this before on to of Stunner shapes... So good to see you are feeling brave hehe :) I'll help as much as possible.
Soo some comments:
* TBH I don't understand how the actual resize stuff works for a Line, I mean by using _view.addHandler(ViewEventType.RESIZE, new ResizeHandler()...)_ . Are really the resize CPs appearing? on top of the line? and what's being resized? Can you please attach some screenshot or video?? it would help to have an idea...
* *About (a)* - Add a CP to the line and fire some commands
** I see two parts here - the lienzo and stunner sides
** On lienzo size it's necessary to implement this new CP and its behavior in some way - maybe implementing the IControlHandle interface as others? not really sure if makes sense, but once given the ability, for your shape, to show/hide the CP, it should also provide some callback to let stunner know the CP has been "updated". As usually you can do this in different ways... options could be using an interface (like we do with the IContainmentAcceptor etc) or using the event bus by creating your own eventhandlers.
** On Stunner side I would implement a new "CavnasControl" and register it to your DMNSession.
** This way, once the control is enabled, it checks the elements being [registered|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-c...] on the diagram/canvas. When the element being added is a DecisionService, you can obtain the Shape and ShapeView instances and register the new CP handler for the shape view instance. Once the lienzo handler do the callback call, on this new canvas control class you can then execute the commands in order to move the shape up / down
** once the control is disabled, you can remove any listener or whatever state added to the shape view instance.
* *About (b)* - Resizing the DecisionService
** Well probably there is some (maksed) bug on the resize stuff on the core as well.. :/ sorry, let's to see if we can fix/improve this :)
** The idea is that the size value is always given by the "bean". So let's consider your DecisionService needs a width and height values - you should create both stunner properties for width and height as usually (annotations, forms, etc) and also specify the _PropertyMetaType.WIDTH/HEIGHT_ via annotations (eg: [BPMN Width property|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-com...]).
** The ShapeView implementation must implement or either _HasSize_/_HasRadiius_, or use a custom _ShapeViewHandler_ in order to update the right attributes given some size
** Once the bean has both properties and they're available from Stunner domain handlers (_PropertyMetaType.WIDTH/HEIGHT_) and the shape views are able to obtain these values and apply the updates on the lienzo side:
*** When updating the value from the properties panel (or any other component), it updates the values on the bean side, so it will update the width and height properties for the DecisionService bean. At thsi point, once a property has been updated, it should also refresh the shape on the canvas, so it uses the new size from the bean values.
*** When resizing from the canvas, it actually uses a canvas control - the _ResizeControl_. The idea is the same as commented on above point (a) - register some handlers on the lienzo size when the element/shape is being added into the canvas, and listen for the callbacks in order to execute the right stunner commands
*** This way the idea is that both properties panel or resizing from the canvas will update the bean values, and the (related) shape/s will be "refreshed" in order to use the new "size" given from the (updated) bean
Well TBH not sure if I answered what you was expecting .... but at least could help a bit. Anyway please ping me or reach me out if you think we should do some call for this, np for me!! I'm now always starting so late hehe :).....seriously, np, just lemme know if you need me, I'll be on PTO for a couple of weeks this xmas so let's try to have this clear during this week, if you think so
Thanks!!
was (Author: roger600):
Hey [~manstis]
Well probably I'm still not familiar with this things you're doing and the issues behind, as we never did something like this before on to of Stunner shapes... So good to see you are feeling brave hehe :) I'll help as much as possible.
Soo some comments:
* TBH I don't understand how the actual resize stuff works for a Line, I mean by using _view.addHandler(ViewEventType.RESIZE, new ResizeHandler()...)_ . Are really the resize CPs appearing? on top of the line? and what's being resized? Can you please attach some screenshot or video?? it would help to have an idea...
* *About (a)* - Add a CP to the line and fire some commands
** I see two parts here - the lienzo and stunner sides
** On lienzo size it's necessary to implement this new CP and its behavior in some way - maybe implementing the IControlHandle interface as others? not really sure if makes sense, but once given the ability, for your shape, to show/hide the CP, it should also provide some callback to let stunner know the CP has been "updated". As usually you can do this in different ways... options could be using an interface (like we do with the IContainmentAcceptor etc) or using the event bus by creating your own eventhandlers.
** On Stunner side I would implement a new "CavnasControl" and register it to your DMNSession.
** This way, once the control is enabled, it checks the elements being [registered|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-c...] on the diagram/canvas. When the element being added is a DecisionService, you can obtain the Shape and ShapeView instances and register the new CP handler for the shape view instance. Once the lienzo handler do the callback call, on this new canvas control class you can then execute the commands in order to move the shape up / down
** once the control is disabled, you can remove any listener or whatever state added to the shape view instance.
* *About (b)* - Resizing the DecisionService
** Well probably there is some (maksed) bug on the resize stuff on the core as well.. :/ sorry, let's to see if we can fix/improve this :)
** The idea is that the size value is always given by the "bean". So let's consider your DecisionService needs a width and height values - you should create both stunner properties for width and height as usually (annotations, forms, etc) and also specify the _PropertyMetaType.WIDTH/HEIGHT_ via annotations.
** The ShapeView implementation must implement or either _HasSize_/_HasRadiius_, or use a custom _ShapeViewHandler_ in order to update the right attributes given some size
** Once the bean has both properties and they're available from Stunner domain handlers (_PropertyMetaType.WIDTH/HEIGHT_) and the shape views are able to obtain these values and apply the updates on the lienzo side:
*** When updating the value from the properties panel (or any other component), it updates the values on the bean side, so it will update the width and height properties for the DecisionService bean. At thsi point, once a property has been updated, it should also refresh the shape on the canvas, so it uses the new size from the bean values.
*** When resizing from the canvas, it actually uses a canvas control - the _ResizeControl_. The idea is the same as commented on above point (a) - register some handlers on the lienzo size when the element/shape is being added into the canvas, and listen for the callbacks in order to execute the right stunner commands
*** This way the idea is that both properties panel or resizing from the canvas will update the bean values, and the (related) shape/s will be "refreshed" in order to use the new "size" given from the (updated) bean
Well TBH not sure if I answered what you was expecting .... but at least could help a bit. Anyway please ping me or reach me out if you think we should do some call for this, np for me!! I'm now always starting so late hehe :).....seriously, np, just lemme know if you need me, I'll be on PTO for a couple of weeks this xmas so let's try to have this clear during this week, if you think so
Thanks!!
> [DMN Designer] Decision Service splitter should be movable
> ----------------------------------------------------------
>
> Key: DROOLS-3406
> URL: https://issues.jboss.org/browse/DROOLS-3406
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> The _splitter_ within a Decision Service is static.
> It needs to be movable (vertically) maintaining it's alignment with the Decision Service bounds. At this point we need to either decide to add _result_ decision(s) and _encapsulated_ decisions to the Decision Service by Command (depending on where the node is dropped) or update the Marshaller to determine the type of decision based on its vertical positioning and location of the _splitter_.
> h2. Acceptance test
> Decision state is updated according to _splitter_ movement. Example if area of result decision expanded so some decision belongs there now, this decision should have state _rusult decision_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3406) [DMN Designer] Decision Service splitter should be movable
by Roger Martínez (Jira)
[ https://issues.jboss.org/browse/DROOLS-3406?page=com.atlassian.jira.plugi... ]
Roger Martínez edited comment on DROOLS-3406 at 12/17/18 5:23 PM:
------------------------------------------------------------------
Hey [~manstis]
Well probably I'm still not familiar with this things you're doing and the issues behind, as we never did something like this before on to of Stunner shapes... So good to see you are feeling brave hehe :) I'll help as much as possible.
Soo some comments:
* TBH I don't understand how the actual resize stuff works for a Line, I mean by using _view.addHandler(ViewEventType.RESIZE, new ResizeHandler()...)_ . Are really the resize CPs appearing? on top of the line? and what's being resized? Can you please attach some screenshot or video?? it would help to have an idea...
* *About (a)* - Add a CP to the line and fire some commands
** I see two parts here - the lienzo and stunner sides
** On lienzo size it's necessary to implement this new CP and its behavior in some way - maybe implementing the IControlHandle interface as others? not really sure if makes sense, but once given the ability, for your shape, to show/hide the CP, it should also provide some callback to let stunner know the CP has been "updated". As usually you can do this in different ways... options could be using an interface (like we do with the IContainmentAcceptor etc) or using the event bus by creating your own eventhandlers.
** On Stunner side I would implement a new "CavnasControl" and register it to your DMNSession.
** This way, once the control is enabled, it checks the elements being [registered|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-c...] on the diagram/canvas. When the element being added is a DecisionService, you can obtain the Shape and ShapeView instances and register the new CP handler for the shape view instance. Once the lienzo handler do the callback call, on this new canvas control class you can then execute the commands in order to move the shape up / down
** once the control is disabled, you can remove any listener or whatever state added to the shape view instance.
* *About (b)* - Resizing the DecisionService
** Well probably there is some (maksed) bug on the resize stuff on the core as well.. :/ sorry, let's to see if we can fix/improve this :)
** The idea is that the size value is always given by the "bean". So let's consider your DecisionService needs a width and height values - you should create both stunner properties for width and height as usually (annotations, forms, etc) and also specify the _PropertyMetaType.WIDTH/HEIGHT_ via annotations.
** The ShapeView implementation must implement or either _HasSize_/_HasRadiius_, or use a custom _ShapeViewHandler_ in order to update the right attributes given some size
** Once the bean has both properties and they're available from Stunner domain handlers (_PropertyMetaType.WIDTH/HEIGHT_) and the shape views are able to obtain these values and apply the updates on the lienzo side:
*** When updating the value from the properties panel (or any other component), it updates the values on the bean side, so it will update the width and height properties for the DecisionService bean. At thsi point, once a property has been updated, it should also refresh the shape on the canvas, so it uses the new size from the bean values.
*** When resizing from the canvas, it actually uses a canvas control - the _ResizeControl_. The idea is the same as commented on above point (a) - register some handlers on the lienzo size when the element/shape is being added into the canvas, and listen for the callbacks in order to execute the right stunner commands
*** This way the idea is that both properties panel or resizing from the canvas will update the bean values, and the (related) shape/s will be "refreshed" in order to use the new "size" given from the (updated) bean
Well TBH not sure if I answered what you was expecting .... but at least could help a bit. Anyway please ping me or reach me out if you think we should do some call for this, np for me!! I'm now always starting so late hehe :).....seriously, np, just lemme know if you need me, I'll be on PTO for a couple of weeks this xmas so let's try to have this clear during this week, if you think so
Thanks!!
was (Author: roger600):
Hey [~manstis]
Well probably I'm still not familiar with this things you're doing and the issues behind, as we never did something like this before on to of Stunner shapes... So good to see you are feeling brave hehe :) I'll help as much as possible.
Soo some comments:
* TBH I don't understand how the actual resize stuff works for a Line, I mean by using _view.addHandler(ViewEventType.RESIZE, new ResizeHandler()...)_ . Are really the resize CPs appearing? on top of the line? and what's being resized? Can you please attach some screenshot or video?? it would help to have an idea...
* About (a) - Add a CP to the line and fire some commands
** I see two parts here - the lienzo and stunner sides
** On lienzo size it's necessary to implement this new CP and its behavior in some way - maybe implementing the IControlHandle interface as others? not really sure if makes sense, but once given the ability, for your shape, to show/hide the CP, it should also provide some callback to let stunner know the CP has been "updated". As usually you can do this in different ways... options could be using an interface (like we do with the IContainmentAcceptor etc) or using the event bus by creating your own eventhandlers.
** On Stunner side I would implement a new "CavnasControl" and register it to your DMNSession.
** This way, once the control is enabled, it checks the elements being [registered|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-c...] on the diagram/canvas. When the element being added is a DecisionService, you can obtain the Shape and ShapeView instances and register the new CP handler for the shape view instance. Once the lienzo handler do the callback call, on this new canvas control class you can then execute the commands in order to move the shape up / down
** once the control is disabled, you can remove any listener or whatever state added to the shape view instance.
* About (b) - Resizing the DecisionService
** Well probably there is some (maksed) bug on the resize stuff on the core as well.. :/ sorry, let's to see if we can fix/improve this :)
** The idea is that the size value is always given by the "bean". So let's consider your DecisionService needs a width and height values - you should create both stunner properties for width and height as usually (annotations, forms, etc) and also specify the _PropertyMetaType.WIDTH/HEIGHT_ via annotations.
** The ShapeView implementation must implement or either _HasSize_/_HasRadiius_, or use a custom _ShapeViewHandler_ in order to update the right attributes given some size
** Once the bean has both properties and they're available from Stunner domain handlers (_PropertyMetaType.WIDTH/HEIGHT_) and the shape views are able to obtain these values and apply the updates on the lienzo side:
*** When updating the value from the properties panel (or any other component), it updates the values on the bean side, so it will update the width and height properties for the DecisionService bean. At thsi point, once a property has been updated, it should also refresh the shape on the canvas, so it uses the new size from the bean values.
*** When resizing from the canvas, it actually uses a canvas control - the _ResizeControl_. The idea is the same as commented on above point (a) - register some handlers on the lienzo size when the element/shape is being added into the canvas, and listen for the callbacks in order to execute the right stunner commands
*** This way the idea is that both properties panel or resizing from the canvas will update the bean values, and the (related) shape/s will be "refreshed" in order to use the new "size" given from the (updated) bean
Well TBH not sure if I answered what you was expecting .... but at least could help a bit. Anyway please ping me or reach me out if you think we should do some call for this, np for me!! I'm now always starting so late hehe :).....seriously, np, just lemme know if you need me, I'll be on PTO for a couple of weeks this xmas so let's try to have this clear during this week, if you think so
Thanks!!
> [DMN Designer] Decision Service splitter should be movable
> ----------------------------------------------------------
>
> Key: DROOLS-3406
> URL: https://issues.jboss.org/browse/DROOLS-3406
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> The _splitter_ within a Decision Service is static.
> It needs to be movable (vertically) maintaining it's alignment with the Decision Service bounds. At this point we need to either decide to add _result_ decision(s) and _encapsulated_ decisions to the Decision Service by Command (depending on where the node is dropped) or update the Marshaller to determine the type of decision based on its vertical positioning and location of the _splitter_.
> h2. Acceptance test
> Decision state is updated according to _splitter_ movement. Example if area of result decision expanded so some decision belongs there now, this decision should have state _rusult decision_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3406) [DMN Designer] Decision Service splitter should be movable
by Roger Martínez (Jira)
[ https://issues.jboss.org/browse/DROOLS-3406?page=com.atlassian.jira.plugi... ]
Roger Martínez edited comment on DROOLS-3406 at 12/17/18 5:22 PM:
------------------------------------------------------------------
Hey [~manstis]
Well probably I'm still not familiar with this things you're doing and the issues behind, as we never did something like this before on to of Stunner shapes... So good to see you are feeling brave hehe :) I'll help as much as possible.
Soo some comments:
* TBH I don't understand how the actual resize stuff works for a Line, I mean by using _view.addHandler(ViewEventType.RESIZE, new ResizeHandler()...)_ . Are really the resize CPs appearing? on top of the line? and what's being resized? Can you please attach some screenshot or video?? it would help to have an idea...
* About (a) - Add a CP to the line and fire some commands
** I see two parts here - the lienzo and stunner sides
** On lienzo size it's necessary to implement this new CP and its behavior in some way - maybe implementing the IControlHandle interface as others? not really sure if makes sense, but once given the ability, for your shape, to show/hide the CP, it should also provide some callback to let stunner know the CP has been "updated". As usually you can do this in different ways... options could be using an interface (like we do with the IContainmentAcceptor etc) or using the event bus by creating your own eventhandlers.
** On Stunner side I would implement a new "CavnasControl" and register it to your DMNSession.
** This way, once the control is enabled, it checks the elements being [registered|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-c...] on the diagram/canvas. When the element being added is a DecisionService, you can obtain the Shape and ShapeView instances and register the new CP handler for the shape view instance. Once the lienzo handler do the callback call, on this new canvas control class you can then execute the commands in order to move the shape up / down
** once the control is disabled, you can remove any listener or whatever state added to the shape view instance.
* About (b) - Resizing the DecisionService
** Well probably there is some (maksed) bug on the resize stuff on the core as well.. :/ sorry, let's to see if we can fix/improve this :)
** The idea is that the size value is always given by the "bean". So let's consider your DecisionService needs a width and height values - you should create both stunner properties for width and height as usually (annotations, forms, etc) and also specify the _PropertyMetaType.WIDTH/HEIGHT_ via annotations.
** The ShapeView implementation must implement or either _HasSize_/_HasRadiius_, or use a custom _ShapeViewHandler_ in order to update the right attributes given some size
** Once the bean has both properties and they're available from Stunner domain handlers (_PropertyMetaType.WIDTH/HEIGHT_) and the shape views are able to obtain these values and apply the updates on the lienzo side:
*** When updating the value from the properties panel (or any other component), it updates the values on the bean side, so it will update the width and height properties for the DecisionService bean. At thsi point, once a property has been updated, it should also refresh the shape on the canvas, so it uses the new size from the bean values.
*** When resizing from the canvas, it actually uses a canvas control - the _ResizeControl_. The idea is the same as commented on above point (a) - register some handlers on the lienzo size when the element/shape is being added into the canvas, and listen for the callbacks in order to execute the right stunner commands
*** This way the idea is that both properties panel or resizing from the canvas will update the bean values, and the (related) shape/s will be "refreshed" in order to use the new "size" given from the (updated) bean
Well TBH not sure if I answered what you was expecting .... but at least could help a bit. Anyway please ping me or reach me out if you think we should do some call for this, np for me!! I'm now always starting so late hehe :).....seriously, np, just lemme know if you need me, I'll be on PTO for a couple of weeks this xmas so let's try to have this clear during this week, if you think so
Thanks!!
was (Author: roger600):
Hey [~manstis]
Well probably I'm still not familiar with this things you're doing and the issues behind, as we never did something like this before on to of Stunner shapes... So good to see you are feeling brave hehe :) I'll help as much as possible.
Soo some comments:
* TBH I don't understand how the actual resize stuff works for a Line, I mean by using _view.addHandler(ViewEventType.RESIZE, new ResizeHandler()...)_ . Are really the resize CPs appearing? on top of the line? and what's being resized? Can you please attach some screenshot or video?? it would help to have an idea...
* About (a) - Add a CP to the line and fire some commands
** I see two parts here - the lienzo and stunner sides
** On lienzo size it's necessary to implement this new CP and its behavior in some way - maybe implementing the IControlHandle interface as others? not really sure if makes sense, but once given the ability, for your shape, to show/hide the CP, it should also provide some callback to let stunner know the CP has been "updated". As usually you can do this in different ways... options could be using an interface (like we do with the IContainmentAcceptor etc) or using the event bus by creating your own eventhandlers.
** On Stunner side I would implement a new "CavnasControl" and register it to your DMNSession.
** This way, once the control is enabled, it checks the elements being [registered|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-c...] on the diagram/canvas. When the element being added is a DecisionService, you can obtain the Shape and ShapeView instances and register the new CP handler for the shape view instance. Once the lienzo handler do the callback call, on this new canvas control class you can then execute the commands in order to move the shape up / down
** once the control is disabled, you can remove any listener or whatever state added to the shape view instance.
* About (b) - Resizing the DecisionService
** Well probably there is some (maksed) bug on the resize stuff on the core as well.. :/ sorry, let's to see if we can fix/improve this :)
** The idea is that the size value is always given by the "bean". So let's consider your DecisionService needs a width and height values - you should create both stunner properties for width and height as usually (annotations, forms, etc) and also specify the _PropertyMetaType.WIDTH/HEIGHT_ via annotations.
** The ShapeView implementation must implement or either _HasSize_/_HasRadiius_, or use a custom _ShapeViewHandler_ in order to update the right attributes given some size
** Once the bean has both properties and they're available from Stunner domain handlers (_PropertyMetaType.WIDTH/HEIGHT_):
*** When updating the value from the properties panel (or any other component), it updates the values on the bean side, so it will update the width and height properties for the DecisionService bean. At thsi point, once a property has been updated, it should also refresh the shape on the canvas, so it uses the new size from the bean values.
*** When resizing from the canvas, it actually uses a canvas control - the _ResizeControl_. The idea is the same as commented on above point (a) - register some handlers on the lienzo size when the element/shape is being added into the canvas, and listen for the callbacks in order to execute the right stunner commands
*** This way the idea is that both properties panel or resizing from the canvas will update the bean values, and the (related) shape/s will be "refreshed" in order to use the new "size" given from the (updated) bean
Well TBH not sure if I answered what you was expecting .... but at least could help a bit. Anyway please ping me or reach me out if you think we should do some call for this, np for me!! I'm now always starting so late hehe :).....seriously, np, just lemme know if you need me, I'll be on PTO for a couple of weeks this xmas so let's try to have this clear during this week, if you think so
Thanks!!
> [DMN Designer] Decision Service splitter should be movable
> ----------------------------------------------------------
>
> Key: DROOLS-3406
> URL: https://issues.jboss.org/browse/DROOLS-3406
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> The _splitter_ within a Decision Service is static.
> It needs to be movable (vertically) maintaining it's alignment with the Decision Service bounds. At this point we need to either decide to add _result_ decision(s) and _encapsulated_ decisions to the Decision Service by Command (depending on where the node is dropped) or update the Marshaller to determine the type of decision based on its vertical positioning and location of the _splitter_.
> h2. Acceptance test
> Decision state is updated according to _splitter_ movement. Example if area of result decision expanded so some decision belongs there now, this decision should have state _rusult decision_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3406) [DMN Designer] Decision Service splitter should be movable
by Roger Martínez (Jira)
[ https://issues.jboss.org/browse/DROOLS-3406?page=com.atlassian.jira.plugi... ]
Roger Martínez commented on DROOLS-3406:
----------------------------------------
Hey [~manstis]
Well probably I'm still not familiar with this things you're doing and the issues behind, as we never did something like this before on to of Stunner shapes... So good to see you are feeling brave hehe :) I'll help as much as possible.
Soo some comments:
* TBH I don't understand how the actual resize stuff works for a Line, I mean by using _view.addHandler(ViewEventType.RESIZE, new ResizeHandler()...)_ . Are really the resize CPs appearing? on top of the line? and what's being resized? Can you please attach some screenshot or video?? it would help to have an idea...
* About (a) - Add a CP to the line and fire some commands
** I see two parts here - the lienzo and stunner sides
** On lienzo size it's necessary to implement this new CP and its behavior in some way - maybe implementing the IControlHandle interface as others? not really sure if makes sense, but once given the ability, for your shape, to show/hide the CP, it should also provide some callback to let stunner know the CP has been "updated". As usually you can do this in different ways... options could be using an interface (like we do with the IContainmentAcceptor etc) or using the event bus by creating your own eventhandlers.
** On Stunner side I would implement a new "CavnasControl" and register it to your DMNSession.
** This way, once the control is enabled, it checks the elements being [registered|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-c...] on the diagram/canvas. When the element being added is a DecisionService, you can obtain the Shape and ShapeView instances and register the new CP handler for the shape view instance. Once the lienzo handler do the callback call, on this new canvas control class you can then execute the commands in order to move the shape up / down
** once the control is disabled, you can remove any listener or whatever state added to the shape view instance.
* About (b) - Resizing the DecisionService
** Well probably there is some (maksed) bug on the resize stuff on the core as well.. :/ sorry, let's to see if we can fix/improve this :)
** The idea is that the size value is always given by the "bean". So let's consider your DecisionService needs a width and height values - you should create both stunner properties for width and height as usually (annotations, forms, etc) and also specify the _PropertyMetaType.WIDTH/HEIGHT_ via annotations.
** The ShapeView implementation must implement or either _HasSize_/_HasRadiius_, or use a custom _ShapeViewHandler_ in order to update the right attributes given some size
** Once the bean has both properties and they're available from Stunner domain handlers (_PropertyMetaType.WIDTH/HEIGHT_):
*** When updating the value from the properties panel (or any other component), it updates the values on the bean side, so it will update the width and height properties for the DecisionService bean. At thsi point, once a property has been updated, it should also refresh the shape on the canvas, so it uses the new size from the bean values.
*** When resizing from the canvas, it actually uses a canvas control - the _ResizeControl_. The idea is the same as commented on above point (a) - register some handlers on the lienzo size when the element/shape is being added into the canvas, and listen for the callbacks in order to execute the right stunner commands
*** This way the idea is that both properties panel or resizing from the canvas will update the bean values, and the (related) shape/s will be "refreshed" in order to use the new "size" given from the (updated) bean
Well TBH not sure if I answered what you was expecting .... but at least could help a bit. Anyway please ping me or reach me out if you think we should do some call for this, np for me!! I'm now always starting so late hehe :).....seriously, np, just lemme know if you need me, I'll be on PTO for a couple of weeks this xmas so let's try to have this clear during this week, if you think so
Thanks!!
> [DMN Designer] Decision Service splitter should be movable
> ----------------------------------------------------------
>
> Key: DROOLS-3406
> URL: https://issues.jboss.org/browse/DROOLS-3406
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> The _splitter_ within a Decision Service is static.
> It needs to be movable (vertically) maintaining it's alignment with the Decision Service bounds. At this point we need to either decide to add _result_ decision(s) and _encapsulated_ decisions to the Decision Service by Command (depending on where the node is dropped) or update the Marshaller to determine the type of decision based on its vertical positioning and location of the _splitter_.
> h2. Acceptance test
> Decision state is updated according to _splitter_ movement. Example if area of result decision expanded so some decision belongs there now, this decision should have state _rusult decision_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11471) Add expressions to enable statistics
by Frank Langelage (Jira)
[ https://issues.jboss.org/browse/WFLY-11471?page=com.atlassian.jira.plugin... ]
Frank Langelage commented on WFLY-11471:
----------------------------------------
At least according to the schemas ejb3, infinispan and the webservices module have statistics:
*+ejb3+*
<statistics enabled="${wildfly.ejb3.statistics-enabled:${wildfly.statistics-enabled:false}}"/>
*+infinispan+*
< <cache-container name="server" default-cache="default" module="org.wildfly.clustering.server" statistics-enabled="${wildfly.infinispan.statistics-enabled:${wildfly.statistics-enabled:false}}">
< <local-cache name="default" statistics-enabled="${wildfly.infinispan.statistics-enabled:${wildfly.statistics-enabled:false}}">
---
> <cache-container name="server" default-cache="default" module="org.wildfly.clustering.server">
> <local-cache name="default">
< <cache-container name="web" default-cache="passivation" module="org.wildfly.clustering.web.infinispan" statistics-enabled="${wildfly.infinispan.statistics-enabled:${wildfly.statistics-enabled:false}}">
< <local-cache name="passivation" statistics-enabled="${wildfly.infinispan.statistics-enabled:${wildfly.statistics-enabled:false}}">
---
> <cache-container name="web" default-cache="passivation" module="org.wildfly.clustering.web.infinispan">
> <local-cache name="passivation">
< <cache-container name="ejb" aliases="sfsb" default-cache="passivation" module="org.wildfly.clustering.ejb.infinispan" statistics-enabled="${wildfly.infinispan.statistics-enabled:${wildfly.statistics-enabled:false}}">
< <local-cache name="passivation" statistics-enabled="${wildfly.infinispan.statistics-enabled:${wildfly.statistics-enabled:false}}">
---
> <cache-container name="ejb" aliases="sfsb" default-cache="passivation" module="org.wildfly.clustering.ejb.infinispan">
> <local-cache name="passivation">
< <cache-container name="hibernate" module="org.infinispan.hibernate-cache" statistics-enabled="${wildfly.infinispan.statistics-enabled:${wildfly.statistics-enabled:false}}">
< <local-cache name="entity" statistics-enabled="${wildfly.infinispan.statistics-enabled:${wildfly.statistics-enabled:false}}">
---
> <cache-container name="hibernate" module="org.infinispan.hibernate-cache">
> <local-cache name="entity">
< <local-cache name="local-query" statistics-enabled="${wildfly.infinispan.statistics-enabled:${wildfly.statistics-enabled:false}}">
---
> <local-cache name="local-query">
< <local-cache name="timestamps" statistics-enabled="${wildfly.infinispan.statistics-enabled:${wildfly.statistics-enabled:false}}"/>
---
> <local-cache name="timestamps"/>
*+webservices+*
< <subsystem xmlns="urn:jboss:domain:webservices:2.0" statistics-enabled="${wildfly.webservices.statistics-enabled:${wildfly.statistics-enabled:false}}">
---
> <subsystem xmlns="urn:jboss:domain:webservices:2.0">
> Add expressions to enable statistics
> ------------------------------------
>
> Key: WFLY-11471
> URL: https://issues.jboss.org/browse/WFLY-11471
> Project: WildFly
> Issue Type: Enhancement
> Components: JCA, JMS, MP Metrics, Transactions, Web (Undertow)
> Affects Versions: 15.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Major
> Fix For: 16.0.0.Beta1
>
>
> With the microprofile-metrics-smallrye extension, we can expose WildFly metrics to monitoring tools such as Promotheus.
> However, some of these metrics can have performance/memory impact and are not computed by default. They are control by attributes named `statistics-enabled` on the WildFly resources those runtime provides these metrics.
> If an user wants to collect such metrics, he has to set these `statistics-enabled` attributes to `true` for all resources.
> In order to improve user experience, our shipped standalone configuration could use expressions so that the user would have to set a single system property to enable these metrics.
> The format would be:
> {code}
> statistics-enabled=${wildfly.statistics-enabled:${wildfly.<xxx>.statistics-enabled:false}}
> {code}
> where <xxx> are names of the resources that exposes the metrics: undertow, transactions, datasources, messaging-activemq
> The nested expressions allows to have a global system property to enable *all* statistics: (wildfly.statistics-enabled) and specific system properties to enable/disable only some metrics (e.g. wildfly.transactions.statistics-enabled).
> Use case:
> * start the standalone profile as usual
> * ./bin/standalone.sh
> * => all statistics-enabled attributes are resolved to false
> * start the standalone profile with all statistics:
> * ./bin/standalone.sh -Dwildfly.statistics-enabled=true
> * => all statistics-enabled attributes are resolved to true
> * start the standalone profile with only undertow statistics:
> * ./bin/standalone.sh -Dwildfly.undertow.statistics-enabled=true
> * => all statistics-enabled attributes are resolved to true
> * start the standalone profile with only undertow statistics:
> * ./bin/standalone.sh -Dwildfly.undertow.statistics-enabled=true
> * => only undertow statistics are enabled
> * start the standalone profile with all but undertow statistics:
> * ./bin/standalone.sh -Dwildfly.undertow.statistics-enabled=false -Dwildfly.statistics-enabled=true
> * => All but undertow statistics are enabled
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months