Grouping items in rules - customer data structures like pojo

[rlkoshak (Rich Koshak)]

@alp_habian

Actually the code in the rule is duplicated for each valve

Not ,

I recommend reviewing

• Design Pattern: Working with Groups in Rules
• Design Pattern: Associated Items
• Design Pattern: DRY, How Not to Repeat Yourself in Rules DSL
• Design Pattern: Encoding and Accessing Values in Rules

There is no need to have separate rules. There is probably no need for the lambda. And there is likely no need for the nested loops.

Another approach is to put the static values in a .map file and access them by a key using the transform Action similar to documented in Design Pattern: Human Readable Names in Messages.