[JBoss JIRA] (DROOLS-1168) notify property change
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1168?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-1168:
-------------------------------------
Passing a random long there is clearly wrong. That long is a bitmask calculated on the basis of the modified attributes of the fact you're updating, so creating a fake bitmask is not the solution.
Said that I don't understand why you need that DroolsUtil.completeEntity() method instead of invoking the proper setters directly on $entity, in case your modifying more than a field the workaround that I suggested should still work as in:
{code}
String[] fields = new String[] {"codDiviCont", "cambioDiviCont"};
DroolsUtil.completeEntity($entity, fields, $t.get("cod_divi_contab").toString(), cambio);
$entity.setCodDiviCont($entity.getCodDiviCont());
$entity.setCambioDiviCont($entity.getCambioDiviCont());
update($entity);
{code}
If this doesn't work for you my only other suggestion is giving up using property reactivity for this use case.
> notify property change
> ----------------------
>
> Key: DROOLS-1168
> URL: https://issues.jboss.org/browse/DROOLS-1168
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 6.4.0.Final
> Environment: java 6, eclipse 4, windows 8.1
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: DroolsUtil.java, EntityBase.java, MtbLisvData.java, rules.drl
>
>
> in the then statement instead of modify use a custom function to change the field. This change does not notify the property even if the class is annotated with @PropertyReactive
> How can I manually notify the change?
> Use a stateless session
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (DROOLS-1182) KieServiesClient.completeConversation() won't unset all conversationIds
by Slavomir Krupa (JIRA)
Slavomir Krupa created DROOLS-1182:
--------------------------------------
Summary: KieServiesClient.completeConversation() won't unset all conversationIds
Key: DROOLS-1182
URL: https://issues.jboss.org/browse/DROOLS-1182
Project: Drools
Issue Type: Bug
Components: kie server
Affects Versions: 6.4.0.Final
Reporter: Slavomir Krupa
Assignee: Edson Tirelli
{noformat}
KieServiesClient.completeConversation()
{noformat}
will unset *conversationId* just from +KieServiesClient+ instance. It won't delete *conversationId* from other clients instances (ProcessServicesClient,UserTaskServicesClient...)
Kie server client stores *conversationId* as class attribute. It means that it is possible to have more *conversationIds* for one +KieServiesClient+ (one for every client implementing +AbstractKieServicesClientImpl+) and it is not possible to unset conversationId for most of the clients (just +KieServiesClient+ has *completeConversation* method).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (DROOLS-1168) notify property change
by Sante Stanisci (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1168?page=com.atlassian.jira.plugi... ]
Sante Stanisci commented on DROOLS-1168:
----------------------------------------
This is a workaround finded by me
rule "completeUntMisVen"
when
eval(checkRulesEnabled == 0)
$entity : MtbLisvData(untMisVen == null && codMart != null )
$untMis: java.lang.String() from SalesRules.completeUntMisLisv(conn, $entity)
then
//modify ( $entity ) { setUntMisVen($untMis) }
String[] fields = new String[]{"untMisVen"};
DroolsUtil.completeEntity($entity, fields, $untMis);
long l = 434576465786346l; //random long
LongBitMask ll = new LongBitMask(l);
update($entity, ll, $entity.getClass());
//update($entity)
end
It is a correct solution?
In this way bitmask is not 0 and next rule fire correctly
> notify property change
> ----------------------
>
> Key: DROOLS-1168
> URL: https://issues.jboss.org/browse/DROOLS-1168
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 6.4.0.Final
> Environment: java 6, eclipse 4, windows 8.1
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: DroolsUtil.java, EntityBase.java, MtbLisvData.java, rules.drl
>
>
> in the then statement instead of modify use a custom function to change the field. This change does not notify the property even if the class is annotated with @PropertyReactive
> How can I manually notify the change?
> Use a stateless session
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (DROOLS-1168) notify property change
by Sante Stanisci (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1168?page=com.atlassian.jira.plugi... ]
Sante Stanisci commented on DROOLS-1168:
----------------------------------------
I tryed I, but is a trivial solution, because DroolUtil can set multiple fields in multiple class that extends EntityBase in this example case
rule "completeCodDivisaContAndCambioDivisaCont"
when
eval(checkRulesEnabled == 0)
(JtbRLavt(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
JtbRLavr(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
GtbSpes(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
GtbTipiPaga(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
PartitaMag(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
CtbMovt(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
CtbMovr(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
CtbMovrCoan(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
CtbMovi(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
CtbParr(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
VtbArti(codDiviCont == null || cambioDiviCont == null, $entityFind : this) or
MtbSpes(codDiviCont == null || cambioDiviCont == null, $entityFind : this)
)
$entity : EntityBase() from $entityFind
$t: java.util.Map() from CommonRules.completeCodDivi(conn)
then
Double cambio = new Double($t.get("cambio").toString());
String[] fields = new String[]{"codDiviCont", "cambioDiviCont"};
DroolsUtil.completeEntity($entity, fields, $t.get("cod_divi_contab").toString(), cambio);
update($entity);
end
Drool natively modify not have this capability.
It's clear?
> notify property change
> ----------------------
>
> Key: DROOLS-1168
> URL: https://issues.jboss.org/browse/DROOLS-1168
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 6.4.0.Final
> Environment: java 6, eclipse 4, windows 8.1
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: DroolsUtil.java, EntityBase.java, MtbLisvData.java, rules.drl
>
>
> in the then statement instead of modify use a custom function to change the field. This change does not notify the property even if the class is annotated with @PropertyReactive
> How can I manually notify the change?
> Use a stateless session
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (DROOLS-1168) notify property change
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1168?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-1168:
-------------------------------------
Did you try what I suggested in my last comment? Something like
{code}
DroolsUtil.completeEntity($entity, fields, $untMis);
$entity.setUntMisVen($entity.getUntMisVen());
update($entity)
{code}
> notify property change
> ----------------------
>
> Key: DROOLS-1168
> URL: https://issues.jboss.org/browse/DROOLS-1168
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 6.4.0.Final
> Environment: java 6, eclipse 4, windows 8.1
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: DroolsUtil.java, EntityBase.java, MtbLisvData.java, rules.drl
>
>
> in the then statement instead of modify use a custom function to change the field. This change does not notify the property even if the class is annotated with @PropertyReactive
> How can I manually notify the change?
> Use a stateless session
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (DROOLS-1168) notify property change
by Sante Stanisci (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1168?page=com.atlassian.jira.plugi... ]
Sante Stanisci commented on DROOLS-1168:
----------------------------------------
ok, but what can be the workaround for the problem? How can I force the execution of update (final FactHandle handle, BitMask mask, Class <?> ModifiedClass). Since you are in the development you could give me some guidance?
Best Regards
> notify property change
> ----------------------
>
> Key: DROOLS-1168
> URL: https://issues.jboss.org/browse/DROOLS-1168
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 6.4.0.Final
> Environment: java 6, eclipse 4, windows 8.1
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: DroolsUtil.java, EntityBase.java, MtbLisvData.java, rules.drl
>
>
> in the then statement instead of modify use a custom function to change the field. This change does not notify the property even if the class is annotated with @PropertyReactive
> How can I manually notify the change?
> Use a stateless session
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JGRP-2066) Probe: sort attributes
by Bela Ban (JIRA)
Bela Ban created JGRP-2066:
------------------------------
Summary: Probe: sort attributes
Key: JGRP-2066
URL: https://issues.jboss.org/browse/JGRP-2066
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 3.6.10, 4.0
The output of probe is easier to read if all attributes are sorted by name
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6628) read-resource responds with incorrect address when going through host controller
by John Mazzitelli (JIRA)
John Mazzitelli created WFLY-6628:
-------------------------------------
Summary: read-resource responds with incorrect address when going through host controller
Key: WFLY-6628
URL: https://issues.jboss.org/browse/WFLY-6628
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 10.0.0.Final
Reporter: John Mazzitelli
Assignee: Alexey Loubyansky
I have a typical small domain setup: one master host controller (aka domain controller) and one slave host controller with "server-one" and "server-two" servers.
I need to discover things running in those two servers (server-one and server-two). As part of the discovery, I invoke read-resource operations via the management interface - for example, to discover all the datasources in server-one:
/host=slave/server=server-one/subsystem=datasources/data-source=*/:read-resource(include-runtime=true)
For each returned datasource, I need to know that datasource's full address. The problem is, I do not get the full address. Instead, the CLI returns the following partial address:
{
"outcome" => "success",
"result" => [{
"address" => [
("subsystem" => "datasources"),
("data-source" => "ExampleDS")
],
"outcome" => "success",
"result" => {
"allocation-retry" => undefined,
...and the rest of the properties for the ExampleDS datasource...
}
}
}]
}
The address should be the full address of:
"address" => [
("host" => "slave"),
("server" => "server-one"),
("subsystem" => "datasources"),
("data-source" => "ExampleDS")
],
NOTE! This problem occurs both when I connect to the domain controller and when I connect to the slave host controller - it doesn't matter, the CLI returns the same erroneous address if connected to either one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6627) Runtime handling for protocol-manager-factory is not implemented on "connection-factory"
by Chen Maoqian (JIRA)
[ https://issues.jboss.org/browse/WFLY-6627?page=com.atlassian.jira.plugin.... ]
Chen Maoqian updated WFLY-6627:
-------------------------------
Attachment: WFLY-6627.patch
The attachment is the patch to fix this issue,but this issue is blocked by ARTEMIS-519,so if we wan to fix this issue ,we must first update the ARTEMIS.
> Runtime handling for protocol-manager-factory is not implemented on "connection-factory"
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-6627
> URL: https://issues.jboss.org/browse/WFLY-6627
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Chen Maoqian
> Assignee: Chen Maoqian
> Attachments: WFLY-6627.patch
>
>
> When trying to update attribute _protocol-manager-factory_ of _/subsystem=messaging-activemq/server=default/connection-factory=RemoteConnectionFactory_ it raises the following exception
> {code:java}
> 17:36:06,807 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("undefine-attribute") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default"),
> ("connection-factory" => "RemoteConnectionFactory")
> ]): java.lang.UnsupportedOperationException: WFLYMSGAMQ0053: Runtime handling for protocol-manager-factory is not implemented
> at org.wildfly.extension.messaging.activemq.jms.ConnectionFactoryWriteAttributeHandler.applyOperationToActiveMQService(ConnectionFactoryWriteAttributeHandler.java:189)
> at org.wildfly.extension.messaging.activemq.jms.ConnectionFactoryWriteAttributeHandler.applyUpdateToRuntime(ConnectionFactoryWriteAttributeHandler.java:96)
> at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:104)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6627) Runtime handling for protocol-manager-factory is not implemented on "connection-factory"
by Chen Maoqian (JIRA)
[ https://issues.jboss.org/browse/WFLY-6627?page=com.atlassian.jira.plugin.... ]
Chen Maoqian moved JBEAP-4627 to WFLY-6627:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6627 (was: JBEAP-4627)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: ActiveMQ)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 10.0.0.Final
(was: 7.0.0.CR2)
> Runtime handling for protocol-manager-factory is not implemented on "connection-factory"
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-6627
> URL: https://issues.jboss.org/browse/WFLY-6627
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Chen Maoqian
> Assignee: Chen Maoqian
>
> When trying to update attribute _protocol-manager-factory_ of _/subsystem=messaging-activemq/server=default/connection-factory=RemoteConnectionFactory_ it raises the following exception
> {code:java}
> 17:36:06,807 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("undefine-attribute") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default"),
> ("connection-factory" => "RemoteConnectionFactory")
> ]): java.lang.UnsupportedOperationException: WFLYMSGAMQ0053: Runtime handling for protocol-manager-factory is not implemented
> at org.wildfly.extension.messaging.activemq.jms.ConnectionFactoryWriteAttributeHandler.applyOperationToActiveMQService(ConnectionFactoryWriteAttributeHandler.java:189)
> at org.wildfly.extension.messaging.activemq.jms.ConnectionFactoryWriteAttributeHandler.applyUpdateToRuntime(ConnectionFactoryWriteAttributeHandler.java:96)
> at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:104)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months