[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2156?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2156:
--------------------------------
Description:
To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
h3. Manual Acceptance Test
Define multiple decision nodes, each holding different expression type as root entry
- Check the heading is updated by clicking in navigation dock (/)
- Check the heading is updated by navigating manually by using back to (/)
- Check the heading is updated in the expression type is changed (/)
- Check the heading is not affected when decision node is renamed
was:
To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
h3. Manual Acceptance Test
Define multiple decision nodes, each holding different expression type as root entry
- Check the heading is updated by clicking in navigation dock (/)
- Check the heading is updated by navigating manually by using back to (/)
- Check the heading is updated in the expression type is changed
- Check the heading is not affected when decision node is renamed
> DMN decision table names should be presented as titles in editor screen.
> ------------------------------------------------------------------------
>
> Key: DROOLS-2156
> URL: https://issues.jboss.org/browse/DROOLS-2156
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Labels: UX
>
> To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
> h3. Manual Acceptance Test
> Define multiple decision nodes, each holding different expression type as root entry
> - Check the heading is updated by clicking in navigation dock (/)
> - Check the heading is updated by navigating manually by using back to (/)
> - Check the heading is updated in the expression type is changed (/)
> - Check the heading is not affected when decision node is renamed
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2156?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2156:
--------------------------------
Description:
To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
h3. Manual Acceptance Test
Define multiple decision nodes, each holding different expression type as root entry
- Check the heading is updated by clicking in navigation dock (/)
- Check the heading is updated by navigating manually by using back to
- Check the heading is updated in the expression type is changed
- Check the heading is not affected when decision node is renamed
was:
To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
h3. Manual Acceptance Test
Define multiple decision nodes, each holding different expression type as root entry
- Check the heading is updated by clicking in navigation dock
- Check the heading is updated by navigating manually by using back to
- Check the heading is updated in the expression type is changed
- Check the heading is not affected when decision node is renamed
> DMN decision table names should be presented as titles in editor screen.
> ------------------------------------------------------------------------
>
> Key: DROOLS-2156
> URL: https://issues.jboss.org/browse/DROOLS-2156
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Labels: UX
>
> To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
> h3. Manual Acceptance Test
> Define multiple decision nodes, each holding different expression type as root entry
> - Check the heading is updated by clicking in navigation dock (/)
> - Check the heading is updated by navigating manually by using back to
> - Check the heading is updated in the expression type is changed
> - Check the heading is not affected when decision node is renamed
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2156?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2156:
--------------------------------
Description:
To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
h3. Manual Acceptance Test
Define multiple decision nodes, each holding different expression type as root entry
- Check the heading is updated by clicking in navigation dock (/)
- Check the heading is updated by navigating manually by using back to (/)
- Check the heading is updated in the expression type is changed
- Check the heading is not affected when decision node is renamed
was:
To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
h3. Manual Acceptance Test
Define multiple decision nodes, each holding different expression type as root entry
- Check the heading is updated by clicking in navigation dock (/)
- Check the heading is updated by navigating manually by using back to
- Check the heading is updated in the expression type is changed
- Check the heading is not affected when decision node is renamed
> DMN decision table names should be presented as titles in editor screen.
> ------------------------------------------------------------------------
>
> Key: DROOLS-2156
> URL: https://issues.jboss.org/browse/DROOLS-2156
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Labels: UX
>
> To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
> h3. Manual Acceptance Test
> Define multiple decision nodes, each holding different expression type as root entry
> - Check the heading is updated by clicking in navigation dock (/)
> - Check the heading is updated by navigating manually by using back to (/)
> - Check the heading is updated in the expression type is changed
> - Check the heading is not affected when decision node is renamed
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2156?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2156:
--------------------------------
Description:
To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
h3. Manual Acceptance Test
Define multiple decision nodes, each holding different expression type as root entry
- Check the heading is updated by clicking in navigation dock
- Check the heading is updated by navigating manually by using back to
- Check the heading is updated in the expression type is changed
- Check the heading is not affected when decision node is renamed
was:To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
> DMN decision table names should be presented as titles in editor screen.
> ------------------------------------------------------------------------
>
> Key: DROOLS-2156
> URL: https://issues.jboss.org/browse/DROOLS-2156
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Labels: UX
>
> To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title.
> h3. Manual Acceptance Test
> Define multiple decision nodes, each holding different expression type as root entry
> - Check the heading is updated by clicking in navigation dock
> - Check the heading is updated by navigating manually by using back to
> - Check the heading is updated in the expression type is changed
> - Check the heading is not affected when decision node is renamed
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-294) Investigate ElasticSearch memory requirements on B24 cluster
by Filip Brychta (JIRA)
[ https://issues.jboss.org/browse/SWSQE-294?page=com.atlassian.jira.plugin.... ]
Filip Brychta commented on SWSQE-294:
-------------------------------------
Looking at Image: openshift3/logging-elasticsearch it's configured following way:
CPU: 1 core requested
Memory: 8 GiB to 8 GiB
> Investigate ElasticSearch memory requirements on B24 cluster
> ------------------------------------------------------------
>
> Key: SWSQE-294
> URL: https://issues.jboss.org/browse/SWSQE-294
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
> Attachments: es1.log
>
>
> On minishift and the CNCF CI OpenShift cluster, we install ElasticSearch using the commands:
> curl https://raw.githubusercontent.com/RHsyseng/docker-rhel-elasticsearch/5.x/... --output es-cluster-deployment.yml
> oc create -f es-cluster-deployment.yml
> However, on B24 this fails. The first 2 elasticsearch pods will start up, but then elasticsearch-2 gets into the following failure loop like:
> elasticsearch-2 1/1 Running 3 1m
> elasticsearch-2 0/1 OOMKilled 3 1m
> elasticsearch-2 0/1 CrashLoopBackOff 3 2m
> If I increase memory in the es-cluster-deployment.yml to 1Gi it will at least start, but I've found I really need to increase it to 2Gi to do anything non trivial.
> We may need to track down the people who originally created this template for help on this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-294) Investigate ElasticSearch memory requirements on B24 cluster
by Filip Brychta (JIRA)
[ https://issues.jboss.org/browse/SWSQE-294?page=com.atlassian.jira.plugin.... ]
Filip Brychta commented on SWSQE-294:
-------------------------------------
The same issue is visible after default installation of downstream istio 0.8.0. Elastic search has only 512MB and is failing. When increased to 4GB it's working fine. From metrics it's visible that it's consuming 3070MB after default installation so 512MB is definitely not enough. We need a jira to update istio installer to increase memory for elastic search pod.
> Investigate ElasticSearch memory requirements on B24 cluster
> ------------------------------------------------------------
>
> Key: SWSQE-294
> URL: https://issues.jboss.org/browse/SWSQE-294
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
> Attachments: es1.log
>
>
> On minishift and the CNCF CI OpenShift cluster, we install ElasticSearch using the commands:
> curl https://raw.githubusercontent.com/RHsyseng/docker-rhel-elasticsearch/5.x/... --output es-cluster-deployment.yml
> oc create -f es-cluster-deployment.yml
> However, on B24 this fails. The first 2 elasticsearch pods will start up, but then elasticsearch-2 gets into the following failure loop like:
> elasticsearch-2 1/1 Running 3 1m
> elasticsearch-2 0/1 OOMKilled 3 1m
> elasticsearch-2 0/1 CrashLoopBackOff 3 2m
> If I increase memory in the es-cluster-deployment.yml to 1Gi it will at least start, but I've found I really need to increase it to 2Gi to do anything non trivial.
> We may need to track down the people who originally created this template for help on this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10613) Warning message when accessing endpoint in deployment with two Application subclasses with same @Path
by Katerina Odabasi (JIRA)
[ https://issues.jboss.org/browse/WFLY-10613?page=com.atlassian.jira.plugin... ]
Katerina Odabasi reassigned WFLY-10613:
---------------------------------------
Assignee: Katerina Odabasi (was: R Searls)
> Warning message when accessing endpoint in deployment with two Application subclasses with same @Path
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-10613
> URL: https://issues.jboss.org/browse/WFLY-10613
> Project: WildFly
> Issue Type: Enhancement
> Reporter: Katerina Odabasi
> Assignee: Katerina Odabasi
> Fix For: 14.0.0.CR1
>
> Attachments: RESTEASY-1445.zip
>
>
> Warning message could be logged, if deployment contains two Application subclass with same @ApplicationPath and same @Path annotation in their end-points.
> One deployment contains two application subclasses with the same @ApplicationPath:
> {code:java}
> @ApplicationPath("a")
> public class DuplicitePathDupliciteApplicationOne extends Application {
> @Override
> public Set<Class<?>> getClasses() {
> HashSet<Class<?>> set = new HashSet<Class<?>>();
> set.add(DuplicitePathDupliciteResourceOne.class);
> return set;
> }
> }
> @ApplicationPath("a")
> public class DuplicitePathDupliciteApplicationTwo extends Application {
> @Override
> public Set<Class<?>> getClasses() {
> HashSet<Class<?>> set = new HashSet<Class<?>>();
> set.add(DuplicitePathDupliciteResourceTwo.class);
> return set;
> }
> }
> {code}
> And each has resource with the same @Path:
> {code:java}
> @Path("/b")
> public class DuplicitePathDupliciteResourceOne {
> public static final String DUPLICITE_RESPONSE = "response4";
> @Path("/c")
> @GET
> @Produces(MediaType.TEXT_PLAIN)
> public String duplicite() {
> return DUPLICITE_RESPONSE;
> }
> }
> @Path("/b")
> public class DuplicitePathDupliciteResourceTwo {
> public static final String DUPLICITE_RESPONSE = "response5";
> @Path("/c")
> @GET
> @Produces(MediaType.TEXT_PLAIN)
> public String dupliciteOne() {
> return DUPLICITE_RESPONSE;
> }
> }
> {code}
> With the request:
> {code:java}
> Response response = client.target("http://localhost:8080/DuplicitePathTest/a/b/c").request().get();
> {code}
> Warning in the server log should be logged as two different resources matches the request.
> See the test in the upstream testsuite - org.jboss.resteasy.test.response.DuplicitePathTest.testDuplicationTwoAppTwoResourceSameMethodPath() (excluded from running with testsuite by default)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2640) [DMN Designer] First function language definitions
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2640?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2640:
--------------------------------
Description:
This was spotted during review of DROOLS-2454 however not sure if it is related. The problem occurs if you declare the function language for the first time.
h3. Manual Acceptance Test
Change function definition multiple times:
- function as top level expression (/)
- context as top level expression, function inside (/)
was:
This was spotted during review of DROOLS-2454 however not sure if it is related. The problem occurs if you declare the function language for the first time.
h3. Manual Acceptance Test
Change function definition multiple times:
- function as top level expression
- context as top level expression, function inside
> [DMN Designer] First function language definitions
> --------------------------------------------------
>
> Key: DROOLS-2640
> URL: https://issues.jboss.org/browse/DROOLS-2640
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Attachments: Screenshot from 2018-06-18 09-54-07.png, Screenshot from 2018-06-18 09-54-15.png
>
>
> This was spotted during review of DROOLS-2454 however not sure if it is related. The problem occurs if you declare the function language for the first time.
> h3. Manual Acceptance Test
> Change function definition multiple times:
> - function as top level expression (/)
> - context as top level expression, function inside (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2640) [DMN Designer] First function language definitions
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2640?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2640:
--------------------------------
Description:
This was spotted during review of DROOLS-2454 however not sure if it is related. The problem occurs if you declare the function language for the first time.
h3. Manual Acceptance Test
Change function definition multiple times:
- function as top level expression
- context as top level expression, function inside
was:This was spotted during review of DROOLS-2454 however not sure if it is related. The problem occurs if you declare the function language for the first time.
> [DMN Designer] First function language definitions
> --------------------------------------------------
>
> Key: DROOLS-2640
> URL: https://issues.jboss.org/browse/DROOLS-2640
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Attachments: Screenshot from 2018-06-18 09-54-07.png, Screenshot from 2018-06-18 09-54-15.png
>
>
> This was spotted during review of DROOLS-2454 however not sure if it is related. The problem occurs if you declare the function language for the first time.
> h3. Manual Acceptance Test
> Change function definition multiple times:
> - function as top level expression
> - context as top level expression, function inside
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-3666) Provide Elytron alternative to RoleMappingLoginModule
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3666?page=com.atlassian.jira.plugi... ]
Martin Choma commented on WFCORE-3666:
--------------------------------------
[~dlofthouse] [~brian.stansberry] We need here to describe Map in model. So OBJECT fits this purpopse just fine. But is it possible to describe Map in model in more "static" way. I mean to have explicitely named key and value attributes, e.g "from" and "to"? So we can describe their meaning directly in model and leverage code completition in CLI?
> Provide Elytron alternative to RoleMappingLoginModule
> -----------------------------------------------------
>
> Key: WFCORE-3666
> URL: https://issues.jboss.org/browse/WFCORE-3666
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 4.0.0.Final
> Reporter: Martin Choma
> Assignee: Martin Mazanek
>
> In picketbox there is RoleMappingLoginModule [1], which takes role as returned from authorization process and maps to different role. I thought something similar should be configurable with some of Elytron role-mappers. But looking into model/code, it is not obvious to me which of them can be used. I know custom role mapper can be still used, but I wonder if we really do not provide this common funcionality out of the box with Elytron.
> Another workaround is to use direct roles from realm (e.g. LDAP ) in target (e.g. web.xml). But seems users tend to map IDM Roles to applicaiton roles.
> [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years