[jira] Created: (CAMEL-400) TypeConverter to support Charset for encoding with bytes

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (CAMEL-400) TypeConverter to support Charset for encoding with bytes

JIRA jira@apache.org
TypeConverter to support Charset for encoding with bytes
--------------------------------------------------------

                 Key: CAMEL-400
                 URL: https://issues.apache.org/activemq/browse/CAMEL-400
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-core
    Affects Versions: 1.3.0
            Reporter: Claus Ibsen


During some patches for came-mina (setting encoding option) I discovered that the camel type converters does not support a 2nd parameter such as a charset to be able to convert using bytes using a user set charset encoding.

Currently the JVM default encoding will most likely be used.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (CAMEL-400) TypeConverter to support Charset for encoding with bytes

JIRA jira@apache.org

     [ https://issues.apache.org/activemq/browse/CAMEL-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang reassigned CAMEL-400:
----------------------------------

    Assignee: Willem Jiang

> TypeConverter to support Charset for encoding with bytes
> --------------------------------------------------------
>
>                 Key: CAMEL-400
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-400
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Claus Ibsen
>            Assignee: Willem Jiang
>             Fix For: 1.5.0
>
>
> During some patches for came-mina (setting encoding option) I discovered that the camel type converters does not support a 2nd parameter such as a charset to be able to convert using bytes using a user set charset encoding.
> Currently the JVM default encoding will most likely be used.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-400) TypeConverter to support Charset for encoding with bytes

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45288#action_45288 ]

Claus Ibsen commented on CAMEL-400:
-----------------------------------

Remember to document it in the wiki

> TypeConverter to support Charset for encoding with bytes
> --------------------------------------------------------
>
>                 Key: CAMEL-400
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-400
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Claus Ibsen
>            Assignee: Willem Jiang
>             Fix For: 1.5.0
>
>
> During some patches for came-mina (setting encoding option) I discovered that the camel type converters does not support a 2nd parameter such as a charset to be able to convert using bytes using a user set charset encoding.
> Currently the JVM default encoding will most likely be used.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (CAMEL-400) TypeConverter to support Charset for encoding with bytes

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/activemq/browse/CAMEL-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CAMEL-400.
--------------------------------

    Resolution: Fixed

Updated  the wiki.


> TypeConverter to support Charset for encoding with bytes
> --------------------------------------------------------
>
>                 Key: CAMEL-400
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-400
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Claus Ibsen
>            Assignee: Willem Jiang
>             Fix For: 1.5.0
>
>
> During some patches for came-mina (setting encoding option) I discovered that the camel type converters does not support a 2nd parameter such as a charset to be able to convert using bytes using a user set charset encoding.
> Currently the JVM default encoding will most likely be used.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (CAMEL-400) TypeConverter to support Charset for encoding with bytes

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/activemq/browse/CAMEL-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen closed CAMEL-400.
-----------------------------


> TypeConverter to support Charset for encoding with bytes
> --------------------------------------------------------
>
>                 Key: CAMEL-400
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-400
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Claus Ibsen
>            Assignee: Willem Jiang
>             Fix For: 1.5.0
>
>
> During some patches for came-mina (setting encoding option) I discovered that the camel type converters does not support a 2nd parameter such as a charset to be able to convert using bytes using a user set charset encoding.
> Currently the JVM default encoding will most likely be used.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.