October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-248) Avoid Route unavailability caused by load balancer recreation on CRD change

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-248?page=com.atlassian.jira.plugin.... ] Petr Kremensky updated WFWIP-248: --------------------------------- Summary: Avoid Route unavailability caused by load balancer recreation on CRD change (was: Avoid Route unavailability caused by load balancer recreation) > Avoid Route unavailability caused by load balancer recreation on CRD change > --------------------------------------------------------------------------- > > Key: WFWIP-248 > URL: https://issues.jboss.org/browse/WFWIP-248 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Tracked by https://github.com/wildfly/wildfly-operator/issues/117 > Reproduce: > {code:sh} > ### REPRODUCER TERMINAL > # deploy quickstart project > oc new-project wildfly-test > wildfly-operator]$ ./build/run-openshift.sh > oc apply -f deploy/crds/quickstart-cr.yaml > wildfly-operator]$ oc get pods > NAME READY STATUS RESTARTS AGE > quickstart-0 1/1 Running 0 34s > quickstart-1 1/1 Running 0 34s > wildfly-operator-7f555b86d5-jkctc 1/1 Running 0 99s > # verify the app is responsive > ROUTE=quickstart-route-wildfly-test.apps-crc.testing > curl $ROUTE > {"ip":"10.128.1.43"} > # watch pods > oc get pods -w & > # verify route readiness > ROUTE=quickstart-route-wildfly-test.apps-crc.testing > # I've seen some weird bash optimization using `while true` in past which I'd like to avoid here... > for i in {0..100000} ; do > echo '----------------------------------------' > date > curl -sI $ROUTE | grep HTTP > curl -s $ROUTE | head -n 1 > echo '' > oc describe service/quickstart-loadbalancer | grep Endpoints > sleep 0.5 > done > ### ADMIN TERMINAL - scale the application > oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":3}]' --type json > {code} > output: > {noformat} > ---------------------------------------- > Mon 14 Oct 2019 01:12:09 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > quickstart-2 0/1 Pending 0 0s > quickstart-2 0/1 Pending 0 0s > quickstart-2 0/1 Pending 0 0s > quickstart-2 0/1 Pending 0 0s > quickstart-2 0/1 ContainerCreating 0 0s > quickstart-2 0/1 ContainerCreating 0 0s > Error from server (NotFound): services "quickstart-loadbalancer" not found > ---------------------------------------- > Mon 14 Oct 2019 01:12:09 PM CEST > HTTP/1.0 503 Service Unavailable > <html> > Endpoints: 10.128.1.43:8080,10.128.1.44:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:10 PM CEST > HTTP/1.0 503 Service Unavailable > <html> > Endpoints: 10.128.1.43:8080,10.128.1.44:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:11 PM CEST > HTTP/1.0 503 Service Unavailable > <html> > Endpoints: 10.128.1.43:8080,10.128.1.44:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:12 PM CEST > HTTP/1.0 503 Service Unavailable > <html> > Endpoints: 10.128.1.43:8080,10.128.1.44:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:13 PM CEST > HTTP/1.0 503 Service Unavailable > <html> > Endpoints: 10.128.1.43:8080,10.128.1.44:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:13 PM CEST > HTTP/1.0 503 Service Unavailable > <html> > Endpoints: 10.128.1.43:8080,10.128.1.44:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:14 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:15 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:16 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080 > quickstart-2quickstart-2 0/10/1 ContainerCreatingContainerCreating 00 8s8s > ---------------------------------------- > Mon 14 Oct 2019 01:12:17 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080 > quickstart-2 1/1 Running 0 8s > quickstart-2 1/1 Running 0 8s > ---------------------------------------- > Mon 14 Oct 2019 01:12:17 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:18 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:19 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:20 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:24 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:24 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:25 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:26 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:27 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:28 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:28 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:29 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:30 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:31 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:32 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:32 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:33 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:34 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.44"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:35 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.43"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > ---------------------------------------- > Mon 14 Oct 2019 01:12:36 PM CEST > HTTP/1.1 200 OK > {"ip":"10.128.1.47"} > Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-248) Avoid Route unavailability caused by load balancer recreation

by Petr Kremensky (Jira)

Petr Kremensky created WFWIP-248: ------------------------------------ Summary: Avoid Route unavailability caused by load balancer recreation Key: WFWIP-248 URL: https://issues.jboss.org/browse/WFWIP-248 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Petr Kremensky Assignee: Jeff Mesnil Tracked by https://github.com/wildfly/wildfly-operator/issues/117 Reproduce: {code:sh} ### REPRODUCER TERMINAL # deploy quickstart project oc new-project wildfly-test wildfly-operator]$ ./build/run-openshift.sh oc apply -f deploy/crds/quickstart-cr.yaml wildfly-operator]$ oc get pods NAME READY STATUS RESTARTS AGE quickstart-0 1/1 Running 0 34s quickstart-1 1/1 Running 0 34s wildfly-operator-7f555b86d5-jkctc 1/1 Running 0 99s # verify the app is responsive ROUTE=quickstart-route-wildfly-test.apps-crc.testing curl $ROUTE {"ip":"10.128.1.43"} # watch pods oc get pods -w & # verify route readiness ROUTE=quickstart-route-wildfly-test.apps-crc.testing # I've seen some weird bash optimization using `while true` in past which I'd like to avoid here... for i in {0..100000} ; do echo '----------------------------------------' date curl -sI $ROUTE | grep HTTP curl -s $ROUTE | head -n 1 echo '' oc describe service/quickstart-loadbalancer | grep Endpoints sleep 0.5 done ### ADMIN TERMINAL - scale the application oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":3}]' --type json {code} output: {noformat} ---------------------------------------- Mon 14 Oct 2019 01:12:09 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} quickstart-2 0/1 Pending 0 0s quickstart-2 0/1 Pending 0 0s quickstart-2 0/1 Pending 0 0s quickstart-2 0/1 Pending 0 0s quickstart-2 0/1 ContainerCreating 0 0s quickstart-2 0/1 ContainerCreating 0 0s Error from server (NotFound): services "quickstart-loadbalancer" not found ---------------------------------------- Mon 14 Oct 2019 01:12:09 PM CEST HTTP/1.0 503 Service Unavailable <html> Endpoints: 10.128.1.43:8080,10.128.1.44:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:10 PM CEST HTTP/1.0 503 Service Unavailable <html> Endpoints: 10.128.1.43:8080,10.128.1.44:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:11 PM CEST HTTP/1.0 503 Service Unavailable <html> Endpoints: 10.128.1.43:8080,10.128.1.44:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:12 PM CEST HTTP/1.0 503 Service Unavailable <html> Endpoints: 10.128.1.43:8080,10.128.1.44:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:13 PM CEST HTTP/1.0 503 Service Unavailable <html> Endpoints: 10.128.1.43:8080,10.128.1.44:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:13 PM CEST HTTP/1.0 503 Service Unavailable <html> Endpoints: 10.128.1.43:8080,10.128.1.44:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:14 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:15 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:16 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080 quickstart-2quickstart-2 0/10/1 ContainerCreatingContainerCreating 00 8s8s ---------------------------------------- Mon 14 Oct 2019 01:12:17 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080 quickstart-2 1/1 Running 0 8s quickstart-2 1/1 Running 0 8s ---------------------------------------- Mon 14 Oct 2019 01:12:17 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:18 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:19 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:20 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:24 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:24 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:25 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:26 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:27 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:28 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:28 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:29 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:30 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:31 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:32 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:32 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:33 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:34 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.44"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:35 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.43"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 ---------------------------------------- Mon 14 Oct 2019 01:12:36 PM CEST HTTP/1.1 200 OK {"ip":"10.128.1.47"} Endpoints: 10.128.1.43:8080,10.128.1.44:8080,10.128.1.47:8080 {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4609) remove save method from editors that depend on upload widget

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4609?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4609: -------------------------------- Labels: drools-tools (was: ) > remove save method from editors that depend on upload widget > ------------------------------------------------------------ > > Key: DROOLS-4609 > URL: https://issues.jboss.org/browse/DROOLS-4609 > Project: Drools > Issue Type: Task > Components: XLS Decision Table Editor, XLS Score Card Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > The save method is never used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4250) Improve data source type resolving in OOPath

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4250?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4250: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 41-43 (from Okt 7) (was: 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34) > Improve data source type resolving in OOPath > -------------------------------------------- > > Key: DROOLS-4250 > URL: https://issues.jboss.org/browse/DROOLS-4250 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > > Raise better errors when parsing OOPath and refactor some type-handling -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4633) Optimize self-join patterns forall statement

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4633?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4633. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/03c2f67dee21b4a6d38c484b4e7f68a... > Optimize self-join patterns forall statement > -------------------------------------------- > > Key: DROOLS-4633 > URL: https://issues.jboss.org/browse/DROOLS-4633 > Project: Drools > Issue Type: Enhancement > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > At the moment a forall statement with a self join like > {code} > forall( $t : Type( constraints1 ) Type( this == $t, constraints2 ) ) > {code} > is implemented with 2 not nodes and a join. It would be much faster to rewrite it as > {code} > not( Type( constraints1, !constraints2 ) ) > {code} > and then evaluate it with one single not node. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4629) DMN heuristic for invocation name

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-4629?page=com.atlassian.jira.plugi... ] Matteo Mortari reopened DROOLS-4629: ------------------------------------ Needed extended scope, as new PR. > DMN heuristic for invocation name > --------------------------------- > > Key: DROOLS-4629 > URL: https://issues.jboss.org/browse/DROOLS-4629 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > Ref https://issues.jboss.org/browse/RHDM-980?focusedCommentId=13796841&page=c... > h2. Acceptance test > - Invoke function from different node > - Invoke function from the same node > - Invoke By Invocation expression > - Invoke by Literal Expression -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3923) (C)DI detection should be more reliable/standard for codegen

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3923?page=com.atlassian.jira.plugi... ] Edoardo Vacchi closed DROOLS-3923. ---------------------------------- Resolution: Out of Date superseded by KOGITO-370 > (C)DI detection should be more reliable/standard for codegen > ------------------------------------------------------------ > > Key: DROOLS-3923 > URL: https://issues.jboss.org/browse/DROOLS-3923 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > we are currently doing {{ try { Class.forName("...ApplicationScoped") } }} which is > (1) pretty hackish (2) won't work in Maven because maven's ClassPath is not the same of the target application > We should rather use a config param or any better way to detect if we're going to use DI. Currently we have added a config param + "auto detect" using the technique above (in maven only the config param works) but auto-detect should be better. > Besides ApplicationScoped only work for CDI, while JSR-330 @Inject is independent from CDI so using ApplicationScoped as a signal is too limited. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3923) (C)DI detection should be more reliable/standard for codegen

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3923?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3923: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 41-43 (from Okt 7) (was: 2019 Week 23-25, 2019 Week 26-28) > (C)DI detection should be more reliable/standard for codegen > ------------------------------------------------------------ > > Key: DROOLS-3923 > URL: https://issues.jboss.org/browse/DROOLS-3923 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > we are currently doing {{ try { Class.forName("...ApplicationScoped") } }} which is > (1) pretty hackish (2) won't work in Maven because maven's ClassPath is not the same of the target application > We should rather use a config param or any better way to detect if we're going to use DI. Currently we have added a config param + "auto detect" using the technique above (in maven only the config param works) but auto-detect should be better. > Besides ApplicationScoped only work for CDI, while JSR-330 @Inject is independent from CDI so using ApplicationScoped as a signal is too limited. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3374) Add primitive to suspend rule firing

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3374?page=com.atlassian.jira.plugi... ] Edoardo Vacchi closed DROOLS-3374. ---------------------------------- Resolution: Out of Date the fix has been rendered useless by rule units which won't use agenda groups anymore to implement partitioned rule-base/working-memory. > Add primitive to suspend rule firing > ------------------------------------- > > Key: DROOLS-3374 > URL: https://issues.jboss.org/browse/DROOLS-3374 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > subsumes DROOLS-3282 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3374) Add primitive to suspend rule firing

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3374?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3374: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7) > Add primitive to suspend rule firing > ------------------------------------- > > Key: DROOLS-3374 > URL: https://issues.jboss.org/browse/DROOLS-3374 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > subsumes DROOLS-3282 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 2019