Hello again.
Thanks a lot for your feedback and the links to the commits. Indeed,
following your way, we've checked the source code from Red-Hat and the
camel-core 2.17.0.redhat-630516 we use has a different code, that is
not a backport of the Apache's commit, but leads to the same issue.
The cod
Thank you for checking this with Camel 3.x!
I created a ticket for it: https://issues.apache.org/jira/browse/CAMEL-18685
This behavior of the Charset is configurable and can be adjusted to report
(the default), ignore or replace the unmappable character.
Kind regards
On Thu, Nov 3, 2022 at 4:57
Hi,
For Red Hat Fuse, please check https://issues.redhat.com/browse/ENTESB-15441
and https://access.redhat.com/solutions/5649371. I think this could explain
this issue.
On Fri, Nov 4, 2022 at 12:07 AM Zheng Feng wrote:
> I just checked the commits history. And it seems related to this change
>
I just checked the commits history. And it seems related to this change [1]
which switched to using Files.newBufferedWriter since camel-2.20.0. So your
example is failing with camel > 2.20.0
For Red Hat Fuse, it might backport this commit to their products and your
customer should check it with the
@Otavia I run the test and this also happens on Camel 3.19.0 (JDK11). The
result:
Caused by: java.nio.charset.UnmappableCharacterException: Input length = 1
I am not expert on charsets, but when a character is not available /
unmappable I would expect that it is replaced by for example a '?'.
Obv
Hello again.
Perhaps you're right about RedHat Fuse. I can ask our customer to open a case...
For other environments where we use pure Karaf+Camel I'm afraid we
have to find the solution elsewhere...
I don't understand the origin of this issue. In my understanding
charsets and streams operations
Well, since you are using Fuse 6.3 and I think it is supported by Red Hat.
So it would be better to open a case to get more support from them.
On Thu, Nov 3, 2022 at 7:49 PM Ephemeris Lappis
wrote:
> Hello.
>
> I'm afraid we can't switch to a newer version. Our customer production
> system is Fu
Hello.
I'm afraid we can't switch to a newer version. Our customer production
system is Fuse 6.3 with its validated Camel version.
And other systems are using the versions I've previously listed.
For the future we can plan to use the latest Camel versions, but today
it's almost impossible...
No
Hi,
I wouldn't know about the reason for this behavior, but my suggestion is to
try with a newer version of Camel. Camel version 2.x is not maintained
anymore.
Please, can you try with a newer version of Camel? Something like 3.18.3
... and let us know if this is still a problem?
Kind regards
O
Hello.
The issue happens on different versions of Camel with different configurations :
- 2.25.4 / karaf 4.3.6 / jdk 1.8
- 2.25.4 / karaf 4.4.1 / jdk 18
- 2.17.0 / fuse 6.3 / jdk 1.8
The last one is the production environment where the issue is critical...
What's strange, is that the same little
Hello,
What version of Camel are you using?
Kind regards
On Wed, Nov 2, 2022 at 3:22 PM Ephemeris Lappis
wrote:
> Hello again.
>
> Sorry to answer my own question...
>
> I've read again the file component documentation looking for any
> solution to fix ou issue, and I've seen that this is exac
Hello again.
Sorry to answer my own question...
I've read again the file component documentation looking for any
solution to fix ou issue, and I've seen that this is exactly the
example that it's given for using charset :
The charset option allows for configuring an encoding of the files on
both
12 matches
Mail list logo
