[JBoss JIRA] (DROOLS-5387) Rule Names are converted GDST <-> XLS
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5387?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5387:
--------------------------------
Affects Version/s: 7.39.0.Final
> Rule Names are converted GDST <-> XLS
> -------------------------------------
>
> Key: DROOLS-5387
> URL: https://issues.redhat.com/browse/DROOLS-5387
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor, XLS Decision Table Editor
> Affects Versions: 7.39.0.Final
> Reporter: Jozef Marko
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> After DROOLS-5333 we should ensure custom rule names are correctly converted in both ways GDST->XLS and XLS->GDST.
> Currently even if in GDST we declared custom rule names in the converted XLS are used some autogonerated values as [tablename_rowindex].
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5333) Allow to customize rule names in guided decision table editor
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5333?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5333:
--------------------------------
Description:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected (/)
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox (/)
- Chrome (/)
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans) (/)
- Create scesim file to check execution is not affected
- GDST to XLS conversion
- Tooltip for added check box - (x)
was:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected (/)
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox (/)
- Chrome (/)
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans) (/)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
- Help in the changed wizard page
> Allow to customize rule names in guided decision table editor
> -------------------------------------------------------------
>
> Key: DROOLS-5333
> URL: https://issues.redhat.com/browse/DROOLS-5333
> Project: Drools
> Issue Type: Feature Request
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: rulename-column.webm
>
>
> Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
> h3. Check to be done during manual review
> - Guided Rule Templates are not affected (/)
> - Guided Rules are not affected (/)
> - bxms-qe-tests internal are updated
> - Firefox (/)
> - Chrome (/)
> - Create new table, Put value, Save and reopen, Remove value, Save and reopen
> - Open existing table (Pricing loans) (/)
> - Create scesim file to check execution is not affected
> - GDST to XLS conversion
> - Tooltip for added check box - (x)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5333) Allow to customize rule names in guided decision table editor
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5333?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5333:
--------------------------------
Description:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected (/)
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox (/)
- Chrome (/)
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans) (/)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
- Help in the changed wizard page
was:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected (/)
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox (/)
- Chrome (/)
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
- Help in the changed wizard page
> Allow to customize rule names in guided decision table editor
> -------------------------------------------------------------
>
> Key: DROOLS-5333
> URL: https://issues.redhat.com/browse/DROOLS-5333
> Project: Drools
> Issue Type: Feature Request
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: rulename-column.webm
>
>
> Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
> h3. Check to be done during manual review
> - Guided Rule Templates are not affected (/)
> - Guided Rules are not affected (/)
> - bxms-qe-tests internal are updated
> - Firefox (/)
> - Chrome (/)
> - Create new table, Put value, Save and reopen, Remove value, Save and reopen
> - Open existing table (Pricing loans) (/)
> - Create scesim file to check execution is not affetced
> - GDST to XLS conversion
> - Help in the changed wizard page
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5333) Allow to customize rule names in guided decision table editor
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5333?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5333:
--------------------------------
Description:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected (/)
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox (/)
- Chrome (/)
- Create new table, Put value, Save and reopen, Remove value, Save and reopen (/)
- Open existing table (Pricing loans) (/)
- Create scesim file to check execution is not affected
- GDST to XLS conversion
- Tooltip for added check box - (x)
was:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected (/)
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox (/)
- Chrome (/)
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans) (/)
- Create scesim file to check execution is not affected
- GDST to XLS conversion
- Tooltip for added check box - (x)
> Allow to customize rule names in guided decision table editor
> -------------------------------------------------------------
>
> Key: DROOLS-5333
> URL: https://issues.redhat.com/browse/DROOLS-5333
> Project: Drools
> Issue Type: Feature Request
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: rulename-column.webm
>
>
> Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
> h3. Check to be done during manual review
> - Guided Rule Templates are not affected (/)
> - Guided Rules are not affected (/)
> - bxms-qe-tests internal are updated
> - Firefox (/)
> - Chrome (/)
> - Create new table, Put value, Save and reopen, Remove value, Save and reopen (/)
> - Open existing table (Pricing loans) (/)
> - Create scesim file to check execution is not affected
> - GDST to XLS conversion
> - Tooltip for added check box - (x)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5333) Allow to customize rule names in guided decision table editor
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5333?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5333:
--------------------------------
Description:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected (/)
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox (/)
- Chrome (/)
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
- Help in the changed wizard page
was:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected (/)
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
- Help in the changed wizard page
> Allow to customize rule names in guided decision table editor
> -------------------------------------------------------------
>
> Key: DROOLS-5333
> URL: https://issues.redhat.com/browse/DROOLS-5333
> Project: Drools
> Issue Type: Feature Request
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: rulename-column.webm
>
>
> Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
> h3. Check to be done during manual review
> - Guided Rule Templates are not affected (/)
> - Guided Rules are not affected (/)
> - bxms-qe-tests internal are updated
> - Firefox (/)
> - Chrome (/)
> - Create new table, Put value, Save and reopen, Remove value, Save and reopen
> - Open existing table (Pricing loans)
> - Create scesim file to check execution is not affetced
> - GDST to XLS conversion
> - Help in the changed wizard page
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5333) Allow to customize rule names in guided decision table editor
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5333?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5333:
--------------------------------
Description:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected (/)
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
- Help in the changed wizard page
was:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
- Help in the changed wizard page
> Allow to customize rule names in guided decision table editor
> -------------------------------------------------------------
>
> Key: DROOLS-5333
> URL: https://issues.redhat.com/browse/DROOLS-5333
> Project: Drools
> Issue Type: Feature Request
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: rulename-column.webm
>
>
> Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
> h3. Check to be done during manual review
> - Guided Rule Templates are not affected (/)
> - Guided Rules are not affected (/)
> - bxms-qe-tests internal are updated
> - Firefox
> - Chrome
> - Create new table, Put value, Save and reopen, Remove value, Save and reopen
> - Open existing table (Pricing loans)
> - Create scesim file to check execution is not affetced
> - GDST to XLS conversion
> - Help in the changed wizard page
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5333) Allow to customize rule names in guided decision table editor
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5333?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5333:
--------------------------------
Description:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected
- Guided Rules are not affected (/)
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
- Help in the changed wizard page
was:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected
- Guided Rules are not affected
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
- Help in the changed wizard page
> Allow to customize rule names in guided decision table editor
> -------------------------------------------------------------
>
> Key: DROOLS-5333
> URL: https://issues.redhat.com/browse/DROOLS-5333
> Project: Drools
> Issue Type: Feature Request
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: rulename-column.webm
>
>
> Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
> h3. Check to be done during manual review
> - Guided Rule Templates are not affected
> - Guided Rules are not affected (/)
> - bxms-qe-tests internal are updated
> - Firefox
> - Chrome
> - Create new table, Put value, Save and reopen, Remove value, Save and reopen
> - Open existing table (Pricing loans)
> - Create scesim file to check execution is not affetced
> - GDST to XLS conversion
> - Help in the changed wizard page
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5386) Accumulate with static method with pettern bind variable
by Toshiya Kobayashi (Jira)
Toshiya Kobayashi created DROOLS-5386:
-----------------------------------------
Summary: Accumulate with static method with pettern bind variable
Key: DROOLS-5386
URL: https://issues.redhat.com/browse/DROOLS-5386
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.38.0.Final
Reporter: Toshiya Kobayashi
Assignee: Toshiya Kobayashi
This rule fails with PATTERN_DSL
{noformat}
rule R when
accumulate (
$p : Person(), $result : sum( MyUtil.add($p.getAge(), 10) ) )
then
insert($result);
end
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-11999) Wildfly creates to many instances of all web service classes
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFLY-11999?page=com.atlassian.jira.plugi... ]
Parul Sharma edited comment on WFLY-11999 at 5/28/20 11:41 PM:
---------------------------------------------------------------
[~jim.ma] [~s.frings74] Can you please let me know what is the purpose of using @ApplicationScoped and @webservice both?
The reason is *@Application* is responsible for initializing CDI/weld that's why multiple instances are creating on the server start. One instance is creating for web services and another for CDI/Weld. Yes, after calling SoapService it should create only one instance but on server start, the startup method has been executing two times because as I explain above Test application is initializing for both CDI and web services.
You didn't face this issue in apache because it doesn't have CDI/weld.
Thanks
was (Author: parsharma):
[~jim.ma] [~s.frings74] Can you please let me know what is the purpose of using @ApplicationScoped and @webservice both?
*@Application* is responsible for initializing CDI/weld that's why multiple instances are creating when we start the server. One is creating for web services and another for CDI/Weld. You didn't face this issue in apache (multiple instances) because it doesn't have CDI/weld.
Yes, after calling SoapService it should create only one instance. Currently, it is creating two instances.
> Wildfly creates to many instances of all web service classes
> ------------------------------------------------------------
>
> Key: WFLY-11999
> URL: https://issues.redhat.com/browse/WFLY-11999
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.0.0.Final, 16.0.0.Final, 19.0.0.Final
> Environment: Ubuntu 18.10 64bit, Open JDK 8 or Open JDK 11
> Reporter: Stefan Frings
> Assignee: Parul Sharma
> Priority: Minor
> Attachments: Test-1.0-SNAPSHOT.war, Test.zip, standalone.xml
>
>
> 1) My @Webservice classes are all constructed multiple times (3x - 4x) but I expected only one instance.
> 2) Only the second instance receives a call to the observer method for initialization. I expect that this method is called in each instance.
> The issue can be reproduced with the attached minimum project on Wildfly 8 with JDK 8 as well as Wildfly 16 with JDK 11.
> Complete source code of the whole application:
> {code}
> package com.mvneco.test;
> import javax.enterprise.context.ApplicationScoped;
> import javax.enterprise.context.Initialized;
> import javax.enterprise.event.Observes;
> import javax.jws.WebMethod;
> import javax.jws.WebService;
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
> @ApplicationScoped
> @WebService
> public class SoapService
> {
> private Log log = LogFactory.getLog(SoapService.class);
> public SoapService()
> {
> log.debug("Init SoapService 1");
> }
> @WebMethod(exclude = true)
> public void init(@Observes @Initialized(ApplicationScoped.class) Object init)
> {
> log.debug("Init SoapService 2");
> }
> @WebMethod
> public String test(String payload)
> {
> log.debug("Start test(). payload="+payload);
> return "OK";
> }
> }
> {code}
> Extract from Log messages that show the issue (the complete log is in the attached ZIP):
> {code}
> 2019-04-17 13:12:21,399 DEBUG [com.mvneco.test.SoapService] (MSC service thread 1-2) Init SoapService 1
> 2019-04-17 13:12:23,068 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 1
> 2019-04-17 13:12:23,070 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 2
> 2019-04-17 13:12:23,475 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started in 10514ms - Started 510 of 699 services (337 services are lazy, passive or on-demand)
> 2019-04-17 13:12:28,920 INFO [org.apache.cxf.services.SoapService.REQ_IN] (default task-1) REQ_IN
> Address: http://localhost:8080/Test-1.0-SNAPSHOT/SoapService
> ...
> 2019-04-17 13:12:28,932 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1
> 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1
> 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Start test(). payload=?
> 2019-04-17 13:12:28,969 INFO [org.apache.cxf.services.SoapService.RESP_OUT] (default task-1) RESP_OUT
> Content-Type: text/xml
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-11999) Wildfly creates to many instances of all web service classes
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFLY-11999?page=com.atlassian.jira.plugi... ]
Parul Sharma edited comment on WFLY-11999 at 5/28/20 11:34 PM:
---------------------------------------------------------------
[~jim.ma] [~s.frings74] Can you please let me know what is the purpose of using @ApplicationScoped and @webservice both?
*@Application* is responsible for initializing CDI/weld that's why multiple instances are creating when we start the server. One is creating for web services and another for CDI/Weld. You didn't face this issue in apache (multiple instances) because it doesn't have CDI/weld.
Yes, after calling SoapService it should create only one instance. Currently, it is creating two instances.
was (Author: parsharma):
[~jim.ma] [~s.frings74] Can you please let me know what is the purpose of using @ApplicationScoped and @webservice both?
*@Application* is responsible for initializing CDI/weld that's why multiple instances are creating.
One is creating for web services and another for CDI/Weld. You didn't face this issue in (multiple instances) apache because it doesn't have CDI/weld.
> Wildfly creates to many instances of all web service classes
> ------------------------------------------------------------
>
> Key: WFLY-11999
> URL: https://issues.redhat.com/browse/WFLY-11999
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.0.0.Final, 16.0.0.Final, 19.0.0.Final
> Environment: Ubuntu 18.10 64bit, Open JDK 8 or Open JDK 11
> Reporter: Stefan Frings
> Assignee: Parul Sharma
> Priority: Minor
> Attachments: Test-1.0-SNAPSHOT.war, Test.zip, standalone.xml
>
>
> 1) My @Webservice classes are all constructed multiple times (3x - 4x) but I expected only one instance.
> 2) Only the second instance receives a call to the observer method for initialization. I expect that this method is called in each instance.
> The issue can be reproduced with the attached minimum project on Wildfly 8 with JDK 8 as well as Wildfly 16 with JDK 11.
> Complete source code of the whole application:
> {code}
> package com.mvneco.test;
> import javax.enterprise.context.ApplicationScoped;
> import javax.enterprise.context.Initialized;
> import javax.enterprise.event.Observes;
> import javax.jws.WebMethod;
> import javax.jws.WebService;
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
> @ApplicationScoped
> @WebService
> public class SoapService
> {
> private Log log = LogFactory.getLog(SoapService.class);
> public SoapService()
> {
> log.debug("Init SoapService 1");
> }
> @WebMethod(exclude = true)
> public void init(@Observes @Initialized(ApplicationScoped.class) Object init)
> {
> log.debug("Init SoapService 2");
> }
> @WebMethod
> public String test(String payload)
> {
> log.debug("Start test(). payload="+payload);
> return "OK";
> }
> }
> {code}
> Extract from Log messages that show the issue (the complete log is in the attached ZIP):
> {code}
> 2019-04-17 13:12:21,399 DEBUG [com.mvneco.test.SoapService] (MSC service thread 1-2) Init SoapService 1
> 2019-04-17 13:12:23,068 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 1
> 2019-04-17 13:12:23,070 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 2
> 2019-04-17 13:12:23,475 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started in 10514ms - Started 510 of 699 services (337 services are lazy, passive or on-demand)
> 2019-04-17 13:12:28,920 INFO [org.apache.cxf.services.SoapService.REQ_IN] (default task-1) REQ_IN
> Address: http://localhost:8080/Test-1.0-SNAPSHOT/SoapService
> ...
> 2019-04-17 13:12:28,932 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1
> 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1
> 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Start test(). payload=?
> 2019-04-17 13:12:28,969 INFO [org.apache.cxf.services.SoapService.RESP_OUT] (default task-1) RESP_OUT
> Content-Type: text/xml
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month