gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Files
fb2c026822245a23c21f58dd05ea78b09be0afcb
java-design-patterns/eip-wire-tap
History
Anurag Agarwal fb2c026822 Java 11 migrate remaining e (#1112) 
* Moves eip-aggregator to Java 11

* Moves eip-message-channel to Java 11

* Moves eip-publish-subscribe to Java 11

* Moves eip-splitter to Java 11

* Moves eip-wire-tap to Java 11

* Moves event-aggregator to Java 11

* Moves event-asynchronous to Java 11

* Moves event-driven-architecture to Java 11

* Moves event-queue to Java 11

* Moves event-sourcing to Java 11

* Moves execute-around to Java 11

* Moves extension-objects to Java 11
2019-12-09 19:03:30 +02:00
..
etc
#1113 Add uml-reverse-mapper plugin
2019-12-07 18:03:49 +02:00
src
Java 11 migrate remaining e (#1112)
2019-12-09 19:03:30 +02:00
pom.xml
Set version for next development iteration
2019-11-17 14:45:41 +02:00
README.md
#1113 Link uml-reverse-mapper created class diagrams to readme, where needed
2019-12-07 20:26:59 +02:00

README.md

layout, title, folder, permalink, categories, tags
layout title folder permalink categories tags
pattern EIP Wire Tap eip-wire-tap /patterns/eip-wire-tap/ Integration
Java
Difficulty-Intermittent
EIP

Intent

In most integration cases there is a need to monitor the messages flowing through the system. It is usually achieved by intercepting the message and redirecting it to a different location like console, filesystem or the database. It is important that such functionality should not modify the original message and influence the processing path.

Diagram

alt text

Applicability

Use the Wire Tap pattern when

  • You need to monitor messages flowing through the system
  • You need to redirect the same, unchanged message to two different endpoints/paths

Credits