Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can just use any persistence component to save your dead letter messages (<a href="http://camel.apache.org/hibernate.html" rel="nofollow">Hibernate</a>, <a href="http://camel.apache.org/jpa.html" rel="nofollow">JPA</a>, <a href="http://camel.apache.org/jdbc.html" rel="nofollow">JDBC</a>, <a href="http://camel.apache.org/db4o.html" rel="nofollow">DB4O</a>, etc.). In case of majority of persistence components you will not save the message itself, but selected (meta)data from it (the notable exception from that is the case of using DB4O component).</p> <p>For example if you're sending Hibernates entities in messages, you can use <a href="http://camel.apache.org/hibernate.html" rel="nofollow">Hibernate component</a>:</p> <pre><code>from("seda:deadMessageStore"). setBody().groovy("new DeadMessageLog(request.headers, request.body) "). to("hibernate:com.foo.DeadMessageLog"); errorHandler(deadLetterChannel("seda:deadMessageStore")); </code></pre> <p>If you cannot predict what kind of classes will you send to the dead letter queue, consider using <a href="http://camel.apache.org/db4o.html" rel="nofollow">DB4O component</a>. DB4O is extremely flexible in that matter since it allows you to store any Java object in the your queue (without explicit mapping, like in the case of the Hibernate or JPA). </p> <pre><code>// store any Java object without transformations errorHandler(deadLetterChannel("db4o:java.lang.Object")) </code></pre> <p>Also creating embedded DB40 container is very simple:</p> <pre><code>ObjectContainer db = Db4oEmbedded.openFile(Db4oEmbedded.newConfiguration(), DB4OFILENAME); </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload