[JBoss JIRA] (DROOLS-897) Binding variable or condition
by Sante Stanisci (JIRA)
[ https://issues.jboss.org/browse/DROOLS-897?page=com.atlassian.jira.plugin... ]
Sante Stanisci commented on DROOLS-897:
---------------------------------------
Simply on method doConseguence() declare Y as directely super class of X, in other words
public void doConsequence(Drools drools, <? extends Y> $entity, java.util.Map $t, java.math.BigDecimal $cambio)
But I do not understand why in doConseguence() is used JtbRlavt and not any of the classes listed (JtbRLavr, GtbSpes, ....) in then statement.
> Binding variable or condition
> -----------------------------
>
> Key: DROOLS-897
> URL: https://issues.jboss.org/browse/DROOLS-897
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Environment: Windows 8
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Labels: dynamic, instanciation, variable
> Attachments: rule.drl, workaround.drl
>
>
> In this example I have more classes that extends EntityBase (my class). In my intention, i would assign to variable $entity one of this class that is inserted in Ksession fact.
> I insert fact of CtbMovrCoan class
> In when statement of the rule at row 16, variable $entity is correctely,
> but in then statement variable $entity becomes JtbRLavt class (first declared in then cond) and this behavior throw a ClassCastException, obviously.
> Can Help me?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFCORE-928) CLI is not terminated correctly with invalid address on HPUX
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-928?page=com.atlassian.jira.plugin... ]
Marek Kopecký moved JBEAP-914 to WFCORE-928:
--------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-928 (was: JBEAP-914)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: CLI
(was: CLI)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.0.Beta4
(was: 7.0.0.DR9)
> CLI is not terminated correctly with invalid address on HPUX
> ------------------------------------------------------------
>
> Key: WFCORE-928
> URL: https://issues.jboss.org/browse/WFCORE-928
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.0.0.Beta4
> Reporter: Marek Kopecký
> Assignee: Alexey Loubyansky
> Priority: Minor
>
> *Description of problem:*
> CLI is not terminated correctly with invalid address on HPUX.
> *How reproducible:*
> Always on HPUX
> *Steps to Reproduce:*
> # ./jboss-cli.sh -c --controller=nonsence
> *Actual results:*
> CLI is terminated after input on stdin.
> *Expected results:*
> CLI is terminated correctly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (DROOLS-897) Binding variable or condition
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-897?page=com.atlassian.jira.plugin... ]
Mario Fusco commented on DROOLS-897:
------------------------------------
Do you mean that we should have different consequence implementations and select the right one at runtime? Honestly this will have an awful performance impact only to cover an extremely limited use case that in my humble opinion has been generated by a badly designed domain model. Sorry, but for sure this is not going to happen.
> Binding variable or condition
> -----------------------------
>
> Key: DROOLS-897
> URL: https://issues.jboss.org/browse/DROOLS-897
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Environment: Windows 8
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Labels: dynamic, instanciation, variable
> Attachments: rule.drl, workaround.drl
>
>
> In this example I have more classes that extends EntityBase (my class). In my intention, i would assign to variable $entity one of this class that is inserted in Ksession fact.
> I insert fact of CtbMovrCoan class
> In when statement of the rule at row 16, variable $entity is correctely,
> but in then statement variable $entity becomes JtbRLavt class (first declared in then cond) and this behavior throw a ClassCastException, obviously.
> Can Help me?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (DROOLS-897) Binding variable or condition
by Sante Stanisci (JIRA)
[ https://issues.jboss.org/browse/DROOLS-897?page=com.atlassian.jira.plugin... ]
Sante Stanisci commented on DROOLS-897:
---------------------------------------
If only can declare entity with super class, X variable in doConseguence not raise classcastexception, right?
> Binding variable or condition
> -----------------------------
>
> Key: DROOLS-897
> URL: https://issues.jboss.org/browse/DROOLS-897
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Environment: Windows 8
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Labels: dynamic, instanciation, variable
> Attachments: rule.drl, workaround.drl
>
>
> In this example I have more classes that extends EntityBase (my class). In my intention, i would assign to variable $entity one of this class that is inserted in Ksession fact.
> I insert fact of CtbMovrCoan class
> In when statement of the rule at row 16, variable $entity is correctely,
> but in then statement variable $entity becomes JtbRLavt class (first declared in then cond) and this behavior throw a ClassCastException, obviously.
> Can Help me?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (DROOLS-897) Binding variable or condition
by Sante Stanisci (JIRA)
[ https://issues.jboss.org/browse/DROOLS-897?page=com.atlassian.jira.plugin... ]
Sante Stanisci commented on DROOLS-897:
---------------------------------------
Yes, is clear. There is a solution to bind consequence at runtime, in next release?
Or this is impossible for performance requirement?
> Binding variable or condition
> -----------------------------
>
> Key: DROOLS-897
> URL: https://issues.jboss.org/browse/DROOLS-897
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Environment: Windows 8
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Labels: dynamic, instanciation, variable
> Attachments: rule.drl, workaround.drl
>
>
> In this example I have more classes that extends EntityBase (my class). In my intention, i would assign to variable $entity one of this class that is inserted in Ksession fact.
> I insert fact of CtbMovrCoan class
> In when statement of the rule at row 16, variable $entity is correctely,
> but in then statement variable $entity becomes JtbRLavt class (first declared in then cond) and this behavior throw a ClassCastException, obviously.
> Can Help me?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (DROOLS-897) Binding variable or condition
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-897?page=com.atlassian.jira.plugin... ]
Mario Fusco commented on DROOLS-897:
------------------------------------
I'm telling you why this is happen. Because at COMPILE TIME drools generates that consequence method using JtbRLavt as type for $entity (the X in the signature of the previous comment). Then at RUNTIME you insert an instance of CtbMovrCoan, drools tries to invoke that consequence method passing that instance to it, but since it has JtbRLavt in its signature you get that ClassCastException.
Now my question is at COMPILE TIME what type should I use at place of X in order to make it work with all your classes? As you can see there's no right answer if your classes don't extend a common parent class having those methods. Is the problem more clear now?
> Binding variable or condition
> -----------------------------
>
> Key: DROOLS-897
> URL: https://issues.jboss.org/browse/DROOLS-897
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Environment: Windows 8
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Labels: dynamic, instanciation, variable
> Attachments: rule.drl, workaround.drl
>
>
> In this example I have more classes that extends EntityBase (my class). In my intention, i would assign to variable $entity one of this class that is inserted in Ksession fact.
> I insert fact of CtbMovrCoan class
> In when statement of the rule at row 16, variable $entity is correctely,
> but in then statement variable $entity becomes JtbRLavt class (first declared in then cond) and this behavior throw a ClassCastException, obviously.
> Can Help me?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (DROOLS-897) Binding variable or condition
by Sante Stanisci (JIRA)
[ https://issues.jboss.org/browse/DROOLS-897?page=com.atlassian.jira.plugin... ]
Sante Stanisci commented on DROOLS-897:
---------------------------------------
if I insert CtbMovrCoan instance in the knowledgebase X class should be CtbMovrCoan.class, but drools throw classcastexception CtbMovrCoan can not be in casted at JtbRLavt (my comment: first class in rule)
why does this happen?
I cannot tell the class / num line which is raised exception in drools.
> Binding variable or condition
> -----------------------------
>
> Key: DROOLS-897
> URL: https://issues.jboss.org/browse/DROOLS-897
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Environment: Windows 8
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Labels: dynamic, instanciation, variable
> Attachments: rule.drl, workaround.drl
>
>
> In this example I have more classes that extends EntityBase (my class). In my intention, i would assign to variable $entity one of this class that is inserted in Ksession fact.
> I insert fact of CtbMovrCoan class
> In when statement of the rule at row 16, variable $entity is correctely,
> but in then statement variable $entity becomes JtbRLavt class (first declared in then cond) and this behavior throw a ClassCastException, obviously.
> Can Help me?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFLY-4929) Hornetq failover doesn't work
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-4929?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil updated WFLY-4929:
------------------------------
Attachment: master.xml
slave.xml
WildFly 10.0.0.CR1-SNAPSHOT master and slave configuration using a shared-store
> Hornetq failover doesn't work
> -----------------------------
>
> Key: WFLY-4929
> URL: https://issues.jboss.org/browse/WFLY-4929
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 9.0.0.Final
> Environment: Fedora 22
> openjdk 8
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Attachments: master.log, master.xml, master.xml, slave.log, slave.xml, slave.xml
>
>
> I tried to set up backup server for JMS subsystem. I act upon this tutorial (shared store) https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Applicatio...
> When I killed the LIVE server, BACKUP server took the control as I expected. However the problem occurred when I started the LIVE server again. LIVE server stopped the BACKUP and then the BACKUP threw an exception. After that warnings started to occur in the log of BACKUP. When I killed the LIVE again, BACKUP didn't take the control again. See attachments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (WFLY-4929) Hornetq failover doesn't work
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-4929?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFLY-4929:
-----------------------------------
I've tested with WildFly 10.0.0.CR1-SNAPSHOT and HA failover (and failover) works as expected when using a shared store.
> Hornetq failover doesn't work
> -----------------------------
>
> Key: WFLY-4929
> URL: https://issues.jboss.org/browse/WFLY-4929
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 9.0.0.Final
> Environment: Fedora 22
> openjdk 8
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Attachments: master.log, master.xml, slave.log, slave.xml
>
>
> I tried to set up backup server for JMS subsystem. I act upon this tutorial (shared store) https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Applicatio...
> When I killed the LIVE server, BACKUP server took the control as I expected. However the problem occurred when I started the LIVE server again. LIVE server stopped the BACKUP and then the BACKUP threw an exception. After that warnings started to occur in the log of BACKUP. When I killed the LIVE again, BACKUP didn't take the control again. See attachments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months