[GitHub] [camel] jacekszymanski opened a new pull request, #9830: CAMEL-19257: fix the bug in camel-jslt

["jacekszymanski (via GitHub)" <gi...@apache.org>]

jacekszymanski opened a new pull request, #9830:
URL: https://github.com/apache/camel/pull/9830

   # Description
   
   Deep serialize only safe data types
   
   Safe datatypes, i.e. primitives, records, Serializables (including primitive wrappers, Strings etc.) and Collections/Maps thereof.
   
   Unsafe datatypes are serialized by their toString().
   
   This is to fix the bug in camel-jslt, where the Servlet Response object was serialized along with the rest of the Exchange headers, which resulted in a premature call to getWriter() and subsequent exception when the Exchange had been completed and the answer was about to be sent to the client.
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (note that Camel 3 uses `camel-3.x`, whereas Camel 4 uses the `main` branch)
   
   # Tracking
   - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it).
   
   <!--
   # *Note*: trivial changes like, typos, minor documentation fixes and other small items do not require a JIRA issue. In this case your pull request should address just this issue, without pulling in other changes.
   -->
   
   # Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful subject line and body.
   
   <!--  
   If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue.
   -->
   
   - [x] I formatted the code using `mvn -Pformat,fastinstall install && mvn -Psourcecheck`
   
   <!-- 
   You can run the aforementioned command in your module so that the build auto-formats your code and the source check verifies that is complies with our coding style. This will also be verified as part of the checks and your PR may be rejected if the checkstyle does not pass.
   
   You can learn more about the contribution guidelines at https://github.com/apache/camel/blob/main/CONTRIBUTING.md
   -->
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel] davsclaus merged pull request #9830: CAMEL-19257: fix the bug in camel-jslt

["davsclaus (via GitHub)" <gi...@apache.org>]

davsclaus merged PR #9830:
URL: https://github.com/apache/camel/pull/9830


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel] github-actions[bot] commented on pull request #9830: CAMEL-19257: fix the bug in camel-jslt

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on PR #9830:
URL: https://github.com/apache/camel/pull/9830#issuecomment-1500523701

   :star2: Thank you for your contribution to the Apache Camel project! :star2: 
   
   :warning: Please note that the changes on this PR may be **tested automatically**. 
   
   If necessary Apache Camel Committers may access logs and test results in the job summaries!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org