[JBoss JIRA] (WFLY-10131) [Artemis 2.x upgrade] Missing message JMS bridge with DUPS_OK quality of service
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-10131?page=com.atlassian.jira.plugin... ]
Miroslav Novak commented on WFLY-10131:
---------------------------------------
Setting this as resolve based on [~mtoth] comment above.
> [Artemis 2.x upgrade] Missing message JMS bridge with DUPS_OK quality of service
> --------------------------------------------------------------------------------
>
> Key: WFLY-10131
> URL: https://issues.jboss.org/browse/WFLY-10131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Labels: activemq, intermittent
>
> There is missing one message in scenario where JMS bridge (with DUPS_OK) resending messages from one server to another. Durint resending target server is killed and bridge does failover to backup.
> After failover in server logs there are lots of warns/errors:
> {code}
> 05:39:01,697 WARN [org.apache.activemq.artemis.jms.bridge] (Thread-144) AMQ342009: JMS Bridge N/A failed to send + acknowledge batch, closing JMS objects: javax.jms.JMSException: Duplicate message detected - me
> ssage will not be routed. Message information:LargeServerMessage[messageID=2147485500,durable=true,userID=d8ea8e0a-326b-11e8-b74b-fa163e64a220,priority=4, timestamp=Wed Mar 28 05:39:01 EDT 2018,expiration=0, dur
> able=true, address=jms.queue.OutQueue,size=410263,properties=TypedProperties[__AMQ_CID=bd95a355-326b-11e8-b74b-fa163e64a220,_AMQ_ROUTING_TYPE=1,AMQ_BRIDGE_MSG_ID_LIST=ID:c13a41dc-326b-11e8-949b-fa163e64a220,JMSX
> DeliveryCount=10,count=989,color=RED,counter=990,_AMQ_DUPL_ID=fde672e0-e858-4c50-a148-a0b7a4a223591522229901951,_AMQ_LARGE_SIZE=409615]]@1304406481
> at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:423) [artemis-core-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:319) [artemis-core-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.simpleCommit(ActiveMQSessionContext.java:381) [artemis-core-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.commit(ClientSessionImpl.java:862) [artemis-core-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.commit(ClientSessionImpl.java:835) [artemis-core-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.jms.client.ActiveMQSession.commit(ActiveMQSession.java:231) [artemis-jms-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.sendBatchNonTransacted(JMSBridgeImpl.java:1338) [artemis-jms-server-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.sendBatch(JMSBridgeImpl.java:1298) [artemis-jms-server-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.access$1700(JMSBridgeImpl.java:74) [artemis-jms-server-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl$SourceReceiver.run(JMSBridgeImpl.java:1694) [artemis-jms-server-2.5.0.jar:2.5.0]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_162]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_162]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_162]
> Caused by: ActiveMQDuplicateIdException[errorType=DUPLICATE_ID_REJECTED message=Duplicate message detected - message will not be routed. Message information:LargeServerMessage[messageID=2147485500,durable=true,u
> serID=d8ea8e0a-326b-11e8-b74b-fa163e64a220,priority=4, timestamp=Wed Mar 28 05:39:01 EDT 2018,expiration=0, durable=true, address=jms.queue.OutQueue,size=410263,properties=TypedProperties[__AMQ_CID=bd95a355-326b
> -11e8-b74b-fa163e64a220,_AMQ_ROUTING_TYPE=1,AMQ_BRIDGE_MSG_ID_LIST=ID:c13a41dc-326b-11e8-949b-fa163e64a220,JMSXDeliveryCount=10,count=989,color=RED,counter=990,_AMQ_DUPL_ID=fde672e0-e858-4c50-a148-a0b7a4a2235915
> 22229901951,_AMQ_LARGE_SIZE=409615]]@1304406481]
> ... 13 more
> 05:39:01,699 WARN [org.apache.activemq.artemis.core.server] (Thread-23 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@2076a02)) AMQ222149: Message Reference[3056]:RELIABLE:Co
> reMessage[messageID=3056,durable=true,userID=c1347573-326b-11e8-949b-fa163e64a220,priority=4, timestamp=Wed Mar 28 05:38:21 EDT 2018,expiration=0, durable=true, address=jms.queue.InQueue,size=10673,properties=Ty
> pedProperties[__AMQ_CID=be528a5c-326b-11e8-949b-fa163e64a220,_AMQ_ROUTING_TYPE=1,count=980,counter=981,_AMQ_DUPL_ID=13adf1ec-581f-42e4-835b-0e6e33a4e1191522229901913,color=GREEN]]@511432790 has reached maximum d
> elivery attempts, sending it to Dead Letter Address jms.queue.DLQ from jms.queue.InQueue
> 05:39:01,700 WARN [org.apache.activemq.artemis.core.server] (Thread-23 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@2076a02)) AMQ222149: Message Reference[3058]:RELIABLE:CoreMessage[messageID=3058,durable=true,userID=c1349c84-326b-11e8-949b-fa163e64a220,priority=4, timestamp=Wed Mar 28 05:38:21 EDT 2018,expiration=0, durable=true, address=jms.queue.InQueue,size=20914,properties=TypedProperties[__AMQ_CID=be528a5c-326b-11e8-949b-fa163e64a220,_AMQ_ROUTING_TYPE=1,count=981,counter=982,_AMQ_DUPL_ID=6feb66cd-8616-4dff-8775-3f85a4b9bdbb1522229901914,color=RED]]@1150646585 has reached maximum delivery attempts, sending it to Dead Letter Address jms.queue.DLQ from jms.queue.InQueue
> ....
> 05:39:01,706 WARN [org.apache.activemq.artemis.core.server] (Thread-23 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@2076a02)) AMQ222149: Message Reference[3082]:RELIABLE:CoreMessage[messageID=3082,durable=true,userID=c13d4f1d-326b-11e8-949b-fa163e64a220,priority=4, timestamp=Wed Mar 28 05:38:21 EDT 2018,expiration=0, durable=true, address=jms.queue.InQueue,size=10673,properties=TypedProperties[__AMQ_CID=be528a5c-326b-11e8-949b-fa163e64a220,_AMQ_ROUTING_TYPE=1,count=990,counter=991,_AMQ_DUPL_ID=f802f4b7-e0a1-4dee-acc7-0b11963bec401522229901971,color=GREEN]]@2708478 has reached maximum delivery attempts, sending it to Dead Letter Address jms.queue.DLQ from jms.queue.InQueue
> {code}
> So the missing message ended up in DLQ as it could not be delivered to target queue. It looks like that _AMQ_DUPL_ID might trigger dup message detection in target queueu however such message did not get there.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10131) [Artemis 2.x upgrade] Missing message JMS bridge with DUPS_OK quality of service
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-10131?page=com.atlassian.jira.plugin... ]
Miroslav Novak resolved WFLY-10131.
-----------------------------------
Resolution: Done
> [Artemis 2.x upgrade] Missing message JMS bridge with DUPS_OK quality of service
> --------------------------------------------------------------------------------
>
> Key: WFLY-10131
> URL: https://issues.jboss.org/browse/WFLY-10131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Labels: activemq, intermittent
>
> There is missing one message in scenario where JMS bridge (with DUPS_OK) resending messages from one server to another. Durint resending target server is killed and bridge does failover to backup.
> After failover in server logs there are lots of warns/errors:
> {code}
> 05:39:01,697 WARN [org.apache.activemq.artemis.jms.bridge] (Thread-144) AMQ342009: JMS Bridge N/A failed to send + acknowledge batch, closing JMS objects: javax.jms.JMSException: Duplicate message detected - me
> ssage will not be routed. Message information:LargeServerMessage[messageID=2147485500,durable=true,userID=d8ea8e0a-326b-11e8-b74b-fa163e64a220,priority=4, timestamp=Wed Mar 28 05:39:01 EDT 2018,expiration=0, dur
> able=true, address=jms.queue.OutQueue,size=410263,properties=TypedProperties[__AMQ_CID=bd95a355-326b-11e8-b74b-fa163e64a220,_AMQ_ROUTING_TYPE=1,AMQ_BRIDGE_MSG_ID_LIST=ID:c13a41dc-326b-11e8-949b-fa163e64a220,JMSX
> DeliveryCount=10,count=989,color=RED,counter=990,_AMQ_DUPL_ID=fde672e0-e858-4c50-a148-a0b7a4a223591522229901951,_AMQ_LARGE_SIZE=409615]]@1304406481
> at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:423) [artemis-core-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:319) [artemis-core-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.simpleCommit(ActiveMQSessionContext.java:381) [artemis-core-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.commit(ClientSessionImpl.java:862) [artemis-core-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.commit(ClientSessionImpl.java:835) [artemis-core-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.jms.client.ActiveMQSession.commit(ActiveMQSession.java:231) [artemis-jms-client-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.sendBatchNonTransacted(JMSBridgeImpl.java:1338) [artemis-jms-server-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.sendBatch(JMSBridgeImpl.java:1298) [artemis-jms-server-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.access$1700(JMSBridgeImpl.java:74) [artemis-jms-server-2.5.0.jar:2.5.0]
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl$SourceReceiver.run(JMSBridgeImpl.java:1694) [artemis-jms-server-2.5.0.jar:2.5.0]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_162]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_162]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_162]
> Caused by: ActiveMQDuplicateIdException[errorType=DUPLICATE_ID_REJECTED message=Duplicate message detected - message will not be routed. Message information:LargeServerMessage[messageID=2147485500,durable=true,u
> serID=d8ea8e0a-326b-11e8-b74b-fa163e64a220,priority=4, timestamp=Wed Mar 28 05:39:01 EDT 2018,expiration=0, durable=true, address=jms.queue.OutQueue,size=410263,properties=TypedProperties[__AMQ_CID=bd95a355-326b
> -11e8-b74b-fa163e64a220,_AMQ_ROUTING_TYPE=1,AMQ_BRIDGE_MSG_ID_LIST=ID:c13a41dc-326b-11e8-949b-fa163e64a220,JMSXDeliveryCount=10,count=989,color=RED,counter=990,_AMQ_DUPL_ID=fde672e0-e858-4c50-a148-a0b7a4a2235915
> 22229901951,_AMQ_LARGE_SIZE=409615]]@1304406481]
> ... 13 more
> 05:39:01,699 WARN [org.apache.activemq.artemis.core.server] (Thread-23 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@2076a02)) AMQ222149: Message Reference[3056]:RELIABLE:Co
> reMessage[messageID=3056,durable=true,userID=c1347573-326b-11e8-949b-fa163e64a220,priority=4, timestamp=Wed Mar 28 05:38:21 EDT 2018,expiration=0, durable=true, address=jms.queue.InQueue,size=10673,properties=Ty
> pedProperties[__AMQ_CID=be528a5c-326b-11e8-949b-fa163e64a220,_AMQ_ROUTING_TYPE=1,count=980,counter=981,_AMQ_DUPL_ID=13adf1ec-581f-42e4-835b-0e6e33a4e1191522229901913,color=GREEN]]@511432790 has reached maximum d
> elivery attempts, sending it to Dead Letter Address jms.queue.DLQ from jms.queue.InQueue
> 05:39:01,700 WARN [org.apache.activemq.artemis.core.server] (Thread-23 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@2076a02)) AMQ222149: Message Reference[3058]:RELIABLE:CoreMessage[messageID=3058,durable=true,userID=c1349c84-326b-11e8-949b-fa163e64a220,priority=4, timestamp=Wed Mar 28 05:38:21 EDT 2018,expiration=0, durable=true, address=jms.queue.InQueue,size=20914,properties=TypedProperties[__AMQ_CID=be528a5c-326b-11e8-949b-fa163e64a220,_AMQ_ROUTING_TYPE=1,count=981,counter=982,_AMQ_DUPL_ID=6feb66cd-8616-4dff-8775-3f85a4b9bdbb1522229901914,color=RED]]@1150646585 has reached maximum delivery attempts, sending it to Dead Letter Address jms.queue.DLQ from jms.queue.InQueue
> ....
> 05:39:01,706 WARN [org.apache.activemq.artemis.core.server] (Thread-23 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@2076a02)) AMQ222149: Message Reference[3082]:RELIABLE:CoreMessage[messageID=3082,durable=true,userID=c13d4f1d-326b-11e8-949b-fa163e64a220,priority=4, timestamp=Wed Mar 28 05:38:21 EDT 2018,expiration=0, durable=true, address=jms.queue.InQueue,size=10673,properties=TypedProperties[__AMQ_CID=be528a5c-326b-11e8-949b-fa163e64a220,_AMQ_ROUTING_TYPE=1,count=990,counter=991,_AMQ_DUPL_ID=f802f4b7-e0a1-4dee-acc7-0b11963bec401522229901971,color=GREEN]]@2708478 has reached maximum delivery attempts, sending it to Dead Letter Address jms.queue.DLQ from jms.queue.InQueue
> {code}
> So the missing message ended up in DLQ as it could not be delivered to target queue. It looks like that _AMQ_DUPL_ID might trigger dup message detection in target queueu however such message did not get there.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1632) Fix compiler warnings
by Philippe Marschall (JIRA)
Philippe Marschall created ELY-1632:
---------------------------------------
Summary: Fix compiler warnings
Key: ELY-1632
URL: https://issues.jboss.org/browse/ELY-1632
Project: WildFly Elytron
Issue Type: Enhancement
Reporter: Philippe Marschall
Assignee: Darran Lofthouse
The project contains some compiler warnings that are easy to fix.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-98) MP Health is not available in domain mode
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created WFWIP-98:
--------------------------------------
Summary: MP Health is not available in domain mode
Key: WFWIP-98
URL: https://issues.jboss.org/browse/WFWIP-98
Project: WildFly WIP
Issue Type: Bug
Components: MP Health
Reporter: Rostislav Svoboda
Assignee: Jeff Mesnil
Priority: Critical
MP Health is not available in domain mode.
Analysis is not saying that domain is out of scope, EAP7 RFE is not explicit about this either.
We may resolve this just by making it explicit, that MP health is just fo standalone for now.
For domain we should at least have a plan what to do and how
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1631) Compilation error for tests on IBM JDK: sun.security.ec does not exist
by Ondrej Kotek (JIRA)
Ondrej Kotek created ELY-1631:
---------------------------------
Summary: Compilation error for tests on IBM JDK: sun.security.ec does not exist
Key: ELY-1631
URL: https://issues.jboss.org/browse/ELY-1631
Project: WildFly Elytron
Issue Type: Bug
Components: Testsuite
Affects Versions: 1.5.1.Final
Environment: + java -version
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 8.0.5.17 - pxi3280sr5fp17-20180627_01(SR5 FP17))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux x86-32-Bit 20180626_390413 (JIT enabled, AOT enabled)
OpenJ9 - 5cdc604
OMR - a24bc01
IBM - 21870d6)
JCL - 20180619_01 based on Oracle jdk8u171-b11
+ mvn -version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
Maven home: /qa/tools/opt/maven3-latest
Java version: 1.8.0_171, vendor: IBM Corporation
Java home: /qa/tools/opt/ibm-java-i386-sdk-8.0-5.17/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-696.el6.i686", arch: "x86", family: "unix"
Reporter: Ondrej Kotek
Priority: Critical
{{mvn test}} results in compilation error:
{noformat}
[ERROR] /home/hudson/hudson_workspace/workspace/eap-7.x-wildfly-elytron-unit-tests-rhel/944a5964/wildfly-elytron/src/test/java/org/wildfly/security/x500/cert/acme/AcmeClientSpiTest.java:[66,23] package sun.security.ec does not exist
{noformat}
Blocks testing on IBM JDK, setting to Critical.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-97) MP Health is not available in standalone HA profiles
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created WFWIP-97:
--------------------------------------
Summary: MP Health is not available in standalone HA profiles
Key: WFWIP-97
URL: https://issues.jboss.org/browse/WFWIP-97
Project: WildFly WIP
Issue Type: Bug
Components: MP Config
Reporter: Rostislav Svoboda
Assignee: Jeff Mesnil
Priority: Blocker
MP Health is not available in standalone HA profiles
MP health is defined in
* standalone/configuration//standalone-full.xml
* standalone/configuration//standalone.xml
MP health is NOT defined in
* standalone/configuration//standalone-full-ha.xml
* standalone/configuration//standalone-ha.xml
Using build based on https://github.com/wildfly/wildfly/pull/11503
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2867) [Guided Rule] You have to reopen rule to load dependent enums
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2867?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2867:
--------------------------------
Description:
Imagine you have data object like
{code:java}
package com.myspace.new_one_project;
public class Person implements java.io.Serializable {
static final long serialVersionUID = 1L;
private java.lang.String name;
private java.lang.String name2;
public Person() {
}
public java.lang.String getName() {
return this.name;
}
public void setName(java.lang.String name) {
this.name = name;
}
public java.lang.String getName2() {
return this.name2;
}
public void setName2(java.lang.String name2) {
this.name2 = name2;
}
public Person(java.lang.String name, java.lang.String name2) {
this.name = name;
this.name2 = name2;
}
}
{code}
and enumeration
{code}
'Person.name' : ['a','b']
'Person.name2[name=a]' : ['c', 'd']
{code}
Then create constraint like
!Screenshot from 2018-08-08 15-13-14.png|thumbnail!
Then update it like:
!Screenshot from 2018-08-08 15-14-00.png|thumbnail!
Then update it like:
!Screenshot from 2018-08-08 15-14-50.png|thumbnail!
Notice the constraint for name2 field doesn't offer enums 'c' and 'd'. If you save and reopen the rule 'c' and 'd' will be offered. They should be offered without reopening the rule.
h3. Acceptance Test
[EnumerationDepenedentGuidedRuleTest|https://github.com/jboss-integration/...]
was:
Imagine you have data object like
{code:java}
package com.myspace.new_one_project;
public class Person implements java.io.Serializable {
static final long serialVersionUID = 1L;
private java.lang.String name;
private java.lang.String name2;
public Person() {
}
public java.lang.String getName() {
return this.name;
}
public void setName(java.lang.String name) {
this.name = name;
}
public java.lang.String getName2() {
return this.name2;
}
public void setName2(java.lang.String name2) {
this.name2 = name2;
}
public Person(java.lang.String name, java.lang.String name2) {
this.name = name;
this.name2 = name2;
}
}
{code}
and enumeration
{code}
'Person.name' : ['a','b']
'Person.name2[name=a]' : ['c', 'd']
{code}
Then create constraint like
!Screenshot from 2018-08-08 15-13-14.png|thumbnail!
Then update it like:
!Screenshot from 2018-08-08 15-14-00.png|thumbnail!
Then update it like:
!Screenshot from 2018-08-08 15-14-50.png|thumbnail!
Notice the constraint for name2 field doesn't offer enums 'c' and 'd'. If you save and reopen the rule 'c' and 'd' will be offered. They should be offered without reopening the rule.
> [Guided Rule] You have to reopen rule to load dependent enums
> -------------------------------------------------------------
>
> Key: DROOLS-2867
> URL: https://issues.jboss.org/browse/DROOLS-2867
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor, Guided Rule Editor
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Toni Rikkola
> Labels: drools-tools, regression
> Attachments: Screenshot from 2018-08-08 15-13-14.png, Screenshot from 2018-08-08 15-14-00.png, Screenshot from 2018-08-08 15-14-50.png
>
>
> Imagine you have data object like
> {code:java}
> package com.myspace.new_one_project;
> public class Person implements java.io.Serializable {
> static final long serialVersionUID = 1L;
> private java.lang.String name;
> private java.lang.String name2;
> public Person() {
> }
> public java.lang.String getName() {
> return this.name;
> }
> public void setName(java.lang.String name) {
> this.name = name;
> }
> public java.lang.String getName2() {
> return this.name2;
> }
> public void setName2(java.lang.String name2) {
> this.name2 = name2;
> }
> public Person(java.lang.String name, java.lang.String name2) {
> this.name = name;
> this.name2 = name2;
> }
> }
> {code}
> and enumeration
> {code}
> 'Person.name' : ['a','b']
> 'Person.name2[name=a]' : ['c', 'd']
> {code}
> Then create constraint like
> !Screenshot from 2018-08-08 15-13-14.png|thumbnail!
> Then update it like:
> !Screenshot from 2018-08-08 15-14-00.png|thumbnail!
> Then update it like:
> !Screenshot from 2018-08-08 15-14-50.png|thumbnail!
> Notice the constraint for name2 field doesn't offer enums 'c' and 'd'. If you save and reopen the rule 'c' and 'd' will be offered. They should be offered without reopening the rule.
> h3. Acceptance Test
> [EnumerationDepenedentGuidedRuleTest|https://github.com/jboss-integration/...]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months