You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2008/03/15 10:47:32 UTC
[jira] Closed: (CAMEL-381) camel-mina UDP protocol should have
encoding configuration
[ https://issues.apache.org/activemq/browse/CAMEL-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen closed CAMEL-381.
-----------------------------
Fix Version/s: 1.3.0
Resolution: Fixed
Added documentation to the wiki component page.
See unit tests for samples how to use the encoding parameter.
> camel-mina UDP protocol should have encoding configuration
> ----------------------------------------------------------
>
> Key: CAMEL-381
> URL: https://issues.apache.org/activemq/browse/CAMEL-381
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-mina
> Affects Versions: 1.3.0
> Reporter: Claus Ibsen
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 1.3.0
>
> Attachments: camel_381_patch_part1.txt, camel_381_patch_part2.txt
>
>
> If sending string messages using a MinaProducer then the encoding configuration is not possible to configure.
> Currently it is fixed as:
> {code}
> encoder = Charset.defaultCharset().newEncoder();
> {code}
> It should be possible to configure this so we can have all those exotic kind of encodings to work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.