[
https://issues.apache.org/jira/browse/CAMEL-26125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136536#comment-18136536
]
Claus Ibsen commented on CAMEL-26125:
-------------------------------------
PR: https://github.com/apache/camel/pull/28901
The insert operation now sets the node identifier with
exchange.getMessage().setBody(...), so the headers of the incoming message are
kept. Test added; upgrade guide entry added since the CamelJcr* headers now
stay on the message too.
_Claude Code on behalf of Claus Ibsen (davsclaus)_
> camel-jcr - the insert operation drops every incoming header
> ------------------------------------------------------------
>
> Key: CAMEL-26125
> URL: https://issues.apache.org/jira/browse/CAMEL-26125
> Project: Camel
> Issue Type: Bug
> Components: camel-jcr
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> Found while adding the catalog body types of smb, jt400 and jcr (CAMEL-24961,
> PR #28417).
> h4. 1. Insert drops every incoming header
> {{JcrProducer.process}} (main 2a465aa4814c, line 75) writes the id of the new
> node with {{exchange.getOut().setBody(...)}}, so the out message has no
> headers and every header of the incoming message is gone after the producer.
> Checked on 4.24.0-SNAPSHOT with an in-memory Jackrabbit.
> Proposed: use {{exchange.getMessage().setBody(...)}}.
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
