gzurowski commented on code in PR #1348:
URL: https://github.com/apache/camel-website/pull/1348#discussion_r2111350418


##########
content/blog/2025/05/camel412-whatsnew/index.md:
##########
@@ -0,0 +1,129 @@
+---
+title: "Apache Camel 4.12 What's New"
+date: 2025-05-28
+draft: false
+authors: [ davsclaus,squakez ]
+categories: [ "Releases" ]
+preview: "Details of what we have done in the Camel 4.12 release."
+---
+
+Apache Camel 4.12 has just been [released](/blog/2025/05/RELEASE-4.12.0/).
+
+This release introduces a set of new features and noticeable improvements that 
we will cover in this blog post.
+
+## Camel Core
+
+The `camel-xml-io` XML DSL now has a generated XSD Schema that are 
independent, from the classic Camel Spring XSD.
+This allows tooling and end users to use this schema instead and ensure the 
schema matches exactly the capabilities
+of the `camel-ml-io` XML DSL.
+
+The schema is published online at: https://camel.apache.org/schema/xml-io
+
+## Camel Main - Management Port
+
+Camel Quarkus and Spring Boot runtimes allows a dedicated management port (to 
not reuse the regular HTTP service port).
+We have introduced the same feature for `camel-main` runtime.
+
+You can use a management server where to expose management endpoints (such as 
health, metrics, etc.).
+The new server will be available by default on port `9876`. This and other 
several configuration can be changed using
+`camel.management` application properties group. In order to avoid breaking 
compatibility, the previous services running
+on business port (default `8080`) will be still running on the old port AND on 
the new port for a few future releases.
+However, you're invited to move your configuration and adopt the new 
`camel.management` embedded server for management
+services as soon as possible.
+
+### Camel Observability Services - Management Port
+
+As we have made this feature available across all the runtimes, we're using a 
management port (`9876`) to expose the
+observability services. This is an enhancement for security purposes and to 
allow any tool to be able to use a
+management port where available without affecting the availability of the 
regular services exposed by the application.
+
+## Camel JBang
+
+Many smaller bug fixes and improvements to camel-jbang.
+
+The `export` command now has a `--verbose` option that shows exporting 
activity which makes trouble shooting much easier.
+
+Made the `camel get` and `camel ps` outputs a bit easier to understand by 
removing the remote counters. Use `--remote` to see these counters.
+
+The route dumper to YAML is now tooling friendly (such as Camel Karavan and 
Kaoto) so these tools can load the dumped YAML.
+
+The `camel cmd send` command now sends the message without the need for any 
existing running Camel integration.
+To use any existing integration then specify the integration name or PID.
+
+Improved the `camel edit` command to include Camel coding assistance (Camel 
LSP) so having a quick tool to quickly edit
+Camel routes (All DSL supported). 
+
+The `camel shell` now supports extra commands installed via plugins.
+
+The `camel run` now also supports `--port` for Spring Boot and Quarkus 
runtimes (main already supported),
+so you can run multiple instances without having port clashes.
+
+
+## Camel HTTP
+
+The `camel-http` can now easily do file upload as Multipart using 
`multipartUpload=true` option.

Review Comment:
   ```suggestion
   The `camel-http` can now easily handle file uploads as Multipart using 
`multipartUpload=true` option.
   ```



-- 
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-unsubscr...@camel.apache.org

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

Reply via email to