Improve some icons based on Apache Camel EIP icons

[aheil]

At https://camel.apache.org/eip.html you find some variants on the typical EIP pattern icons which could be an improvement to the original icons introduced by GH. The EIP-PlantUML icons could be checked for these improvements.

[Potherca]

To make this task more concrete, I've made a list of all the images from the linked page, and an overview of all sprites already in EIP-PlantUML

These are the 44 icons that need to be checked against those already in EIP-PlantUML:

• [ ] Aggregator
  
• [ ] ChannelAdapter
  
• [ ] Channel
  
• [ ] CompetingConsumers
  
• [ ] ContentBasedRouter
  
• [ ] ContentFilter
  
• [ ] ControlBus
  
• [ ] CorrelationIdentifier
  
• [ ] DataEnricher
  
• [ ] DeadLetterChannel
  
• [ ] Detour
  
• [ ] DistributionAggregate
  
• [ ] DurableSubscription
  
• [ ] DynamicRouter
  
• [ ] EventDrivenConsumer
  
• [ ] EventMessage
  
• [ ] GuaranteedMessaging
  
• [ ] MessageBroker
  
• [ ] MessageBus
  
• [ ] MessageDispatcher
  
• [ ] MessageEndpoint
  
• [ ] MessageExpiration
  
• [ ] MessageFilter
  
• [ ] Message
  
• [ ] MessageSelector
  
• [ ] MessageTranslator
  
• [ ] MessagingAdapter
  
• [ ] MessagingBridge
  
• [ ] MessagingGateway
  
• [ ] Normalizer
  
• [ ] PipesAndFilters
  
• [ ] PointToPoint
  
• [ ] PollingConsumer
  
• [ ] ProcessManager
  
• [ ] PublishSubscribe
  
• [ ] RecipientList
  
• [ ] RequestReply
  
• [ ] Resequencer
  
• [ ] ReturnAddress
  
• [ ] RoutingTable
  
• [ ] Splitter
  
• [ ] StoreInLibrary
  
• [ ] TransactionalClient
  
• [ ] WireTap
  

Full source from page

| | | | | --- | --- | --- | |  | [Message Channel][11] | How does one application communicate with another using messaging? | |  | [Message][12] | How can two applications be connected by a message channel exchange a piece of information? | |  | [Pipes and Filters][13] | How can we perform complex processing on a message while maintaining independence and flexibility? | |  | [Message Router][14] | How can you decouple individual processing steps so that messages can be passed to different filters depending on a set of conditions? | |  | [Message Translator][15] | How can systems using different data formats communicate with each other using messaging? | |  | [Message Endpoint][16] | How does an application connect to a messaging channel to send and receive messages? | |  | [Point to Point Channel][18] | How can the caller be sure that exactly one receiver will receive the document or perform the call? | |  | [Publish Subscribe Channel][19] | How can the sender broadcast an event to all interested receivers? | |  | [Dead Letter Channel][20] | What will the messaging system do with a message it cannot deliver? | |  | [Guaranteed Delivery][21] | How can the sender make sure that a message will be delivered, even if the messaging system fails? | |  | [Channel Adapter][22] | How can you connect an application to the messaging system so that it can send and receive messages? | |  | [Messaging Bridge][23] | How can multiple messaging systems be connected so that messages available on one are also available on the others?? | |  | [Message Bus][24] | What is an architecture that enables separate applications to work together, but in a de-coupled fashion such that applications can be easily added or removed without affecting the others? | |  | [Change Data Capture][25] | Data synchronization by capturing changes made to a database, and apply those changes to another system. | |  | [Event Message][27] | How can messaging be used to transmit events from one application to another? | |  | [Request Reply][28] | When an application sends a message, how can it get a response from the receiver? | |  | [Return Address][29] | How does a replier know where to send the reply? | |  | [Correlation Identifier][30] | How does a requestor that has received a reply know which request this is the reply for? | |  | [Message Expiration][31] | How can a sender indicate when a message should be considered stale and thus shouldn’t be processed? | |  | [Content Based Router][33] | How do we handle a situation where the implementation of a single logical function (e.g., inventory check) is spread across multiple physical systems? | |  | [Message Filter][34] | How can a component avoid receiving uninteresting messages? | |  | [Dynamic Router][35] | How can you avoid the dependency of the router on all possible destinations while maintaining its efficiency? | |  | [Recipient List][36] | How do we route a message to a list of (static or dynamically) specified recipients? | |  | [Splitter][37] | How can we process a message if it contains multiple elements, each of which may have to be processed in a different way? | |  | [Aggregator][38] | How do we combine the results of individual, but related messages so that they can be processed as a whole? | |  | [Resequencer][39] | How can we get a stream of related but out-of-sequence messages back into the correct order? | |  | [Composed Message Processor][40] | How can you maintain the overall message flow when processing a message consisting of multiple elements, each of which may require different processing? | |  | [Scatter-Gather][41] | How do you maintain the overall message flow when a message needs to be sent to multiple recipients, each of which may send a reply? | |  | [Routing Slip][42] | How do we route a message consecutively through a series of processing steps when the sequence of steps is not known at design-time and may vary for each message? | |  | [Process Manager][43] | How do we route a message through multiple processing steps when the required steps may not be known at design-time and may not be sequential? | |  | [Message Broker][44] | How can you decouple the destination of a message from the sender and maintain central control over the flow of messages? | |  | [Threads][45] | How can I decouple the continued routing of a message from the current thread? | |  | [Throttler][46] | How can I throttle messages to ensure that a specific endpoint does not get overloaded, or we don’t exceed an agreed SLA with some external service? | |  | [Sampling][47] | How can I sample one message out of many in a given period to avoid downstream route does not get overloaded? | |  | [Kamelet][48] | How can I call Kamelets (route templates). | |  | [Delayer][49] | How can I delay the sending of a message? | |  | [Load Balancer][50] | How can I balance load across a number of endpoints? | |  | [Circuit Breaker][51] | How can I stop to call an external service if the service is broken? | |  | [Stop][52] | How can I stop continue routing a message? | |  | [Service Call][53] | How can I call a remote service in a distributed system where the service is looked up from a service registry of some sorts? | |  | [Saga][54] | How can I define a series of related actions in a Camel route that should be either completed successfully (all of them) or not-executed/compensated? | |  | [Multicast][55] | How can I route a message to a number of endpoints at the same time? | |  | [Loop][56] | How can I repeat processing a message in a loop? | |  | [Content Enricher][58] | How do we communicate with another system if the message originator does not have all the required data items available? | |  | [Content Filter][59] | How do you simplify dealing with a large message, when you are interested only in a few data items? | |  | [Claim Check][60] | How can we reduce the data volume of message sent across the system without sacrificing information content? | |  | [Normalizer][61] | How do you process messages that are semantically equivalent, but arrive in a different format? | |  | [Sort][62] | How can I sort the body of a message? | |  | [Script][63] | How do I execute a script which may not change the message? | |  | [Validate][64] | How can I validate a message? | |  | [Messaging Mapper][66] | How do you move data between domain objects and the messaging infrastructure while keeping the two independent of each other? | |  | [Event Driven Consumer][67] | How can an application automatically consume messages as they become available? | |  | [Polling Consumer][68] | How can an application consume a message when the application is ready? | |  | [Competing Consumers][69] | How can a messaging client process multiple messages concurrently? | |  | [Message Dispatcher][70] | How can multiple consumers on a single channel coordinate their message processing? | |  | [Selective Consumer][71] | How can a message consumer select which messages it wishes to receive? | |  | [Durable Subscriber][72] | How can a subscriber avoid missing messages while it’s not listening for them? | |  | [Idempotent Consumer][73] | How can a message receiver deal with duplicate messages? | |  | [Resumable Consumer][74] | How can a message receiver resume from last known offset? | |  | [Transactional Client][75] | How can a client control its transactions with the messaging system? | |  | [Messaging Gateway][76] | How do you encapsulate access to the messaging system from the rest of the application? | |  | [Service Activator][77] | How can an application design a service to be invoked both via various messaging technologies and via non-messaging techniques? | |  | [ControlBus][79] | How can we effectively administer a messaging system that is distributed across multiple platforms and a wide geographic area? | |  | [Detour][80] | How can you route a message through intermediate steps to perform validation, testing or debugging functions? | |  | [Wire Tap][81] | How do you inspect messages that travel on a point-to-point channel? | |  | [Message History][82] | How can we effectively analyze and debug the flow of messages in a loosely coupled system? | |  | [Log][83] | How can I log processing a message? | |  | [Step][84] | Groups together a set of EIPs into a composite logical unit for metrics and monitoring. | [11]: https://camel.apache.org/components/next/eips/message-channel.html [12]: https://camel.apache.org/components/next/eips/message.html [13]: https://camel.apache.org/components/next/eips/pipeline-eip.html [14]: https://camel.apache.org/components/next/eips/message-router.html [15]: https://camel.apache.org/components/next/eips/message-translator.html [16]: https://camel.apache.org/components/next/eips/message-endpoint.html [17]: https://camel.apache.org/components/next/eips/#_messaging_channels [18]: https://camel.apache.org/components/next/eips/point-to-point-channel.html [19]: https://camel.apache.org/components/next/eips/publish-subscribe-channel.html [20]: https://camel.apache.org/components/next/eips/dead-letter-channel.html [21]: https://camel.apache.org/components/next/eips/guaranteed-delivery.html [22]: https://camel.apache.org/components/next/eips/channel-adapter.html [23]: https://camel.apache.org/components/next/eips/messaging-bridge.html [24]: https://camel.apache.org/components/next/eips/message-bus.html [25]: https://camel.apache.org/components/next/eips/change-data-capture.html [26]: https://camel.apache.org/components/next/eips/#_message_construction [27]: https://camel.apache.org/components/next/eips/event-message.html [28]: https://camel.apache.org/components/next/eips/requestReply-eip.html [29]: https://camel.apache.org/components/next/eips/return-address.html [30]: https://camel.apache.org/components/next/eips/correlation-identifier.html [31]: https://camel.apache.org/components/next/eips/message-expiration.html [32]: https://camel.apache.org/components/next/eips/#_message_routing [33]: https://camel.apache.org/components/next/eips/choice-eip.html [34]: https://camel.apache.org/components/next/eips/filter-eip.html [35]: https://camel.apache.org/components/next/eips/dynamicRouter-eip.html [36]: https://camel.apache.org/components/next/eips/recipientList-eip.html [37]: https://camel.apache.org/components/next/eips/split-eip.html [38]: https://camel.apache.org/components/next/eips/aggregate-eip.html [39]: https://camel.apache.org/components/next/eips/resequence-eip.html [40]: https://camel.apache.org/components/next/eips/composed-message-processor.html [41]: https://camel.apache.org/components/next/eips/scatter-gather.html [42]: https://camel.apache.org/components/next/eips/routingSlip-eip.html [43]: https://camel.apache.org/components/next/eips/process-manager.html [44]: https://camel.apache.org/components/next/eips/message-broker.html [45]: https://camel.apache.org/components/next/eips/threads-eip.html [46]: https://camel.apache.org/components/next/eips/throttle-eip.html [47]: https://camel.apache.org/components/next/eips/sample-eip.html [48]: https://camel.apache.org/components/next/eips/kamelet-eip.html [49]: https://camel.apache.org/components/next/eips/delay-eip.html [50]: https://camel.apache.org/components/next/eips/loadBalance-eip.html [51]: https://camel.apache.org/components/next/eips/circuitBreaker-eip.html [52]: https://camel.apache.org/components/next/eips/stop-eip.html [53]: https://camel.apache.org/components/next/eips/serviceCall-eip.html [54]: https://camel.apache.org/components/next/eips/saga-eip.html [55]: https://camel.apache.org/components/next/eips/multicast-eip.html [56]: https://camel.apache.org/components/next/eips/loop-eip.html [57]: https://camel.apache.org/components/next/eips/#_message_transformation [58]: https://camel.apache.org/components/next/eips/content-enricher.html [59]: https://camel.apache.org/components/next/eips/content-filter-eip.html [60]: https://camel.apache.org/components/next/eips/claimCheck-eip.html [61]: https://camel.apache.org/components/next/eips/normalizer.html [62]: https://camel.apache.org/components/next/eips/sort-eip.html [63]: https://camel.apache.org/components/next/eips/script-eip.html [64]: https://camel.apache.org/components/next/eips/validate-eip.html [65]: https://camel.apache.org/components/next/eips/#_messaging_endpoints [66]: https://camel.apache.org/components/next/eips/messaging-mapper.html [67]: https://camel.apache.org/components/next/eips/eventDrivenConsumer-eip.html [68]: https://camel.apache.org/components/next/eips/polling-consumer.html [69]: https://camel.apache.org/components/next/eips/competing-consumers.html [70]: https://camel.apache.org/components/next/eips/message-dispatcher.html [71]: https://camel.apache.org/components/next/eips/selective-consumer.html [72]: https://camel.apache.org/components/next/eips/durable-subscriber.html [73]: https://camel.apache.org/components/next/eips/idempotentConsumer-eip.html [74]: https://camel.apache.org/components/next/eips/resume-strategies.html [75]: https://camel.apache.org/components/next/eips/transactional-client.html [76]: https://camel.apache.org/components/next/eips/messaging-gateway.html [77]: https://camel.apache.org/components/next/eips/service-activator.html [78]: https://camel.apache.org/components/next/eips/#_system_management [79]: https://camel.apache.org/components/next/eips/../controlbus-component.html [80]: https://camel.apache.org/components/next/eips/intercept.html [81]: https://camel.apache.org/components/next/eips/wireTap-eip.html [82]: https://camel.apache.org/components/next/eips/message-history.html [83]: https://camel.apache.org/components/next/eips/log-eip.html [84]: https://camel.apache.org/components/next/eips/step-eip.html [85]: https://camel.apache.org/components/next/eips/#_eip_icons