camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6094) Cannot specify which converter to use when several can do the same conversion
Date Fri, 22 Feb 2013 15:18:18 GMT

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

Willem Jiang commented on CAMEL-6094:
-------------------------------------

I think we can add a option in camel to use the first one converter it found in the class
path.
But for the conflict of the camel-jetty and camel-http4 component converter, I think we can
resolve it in Camel 3.x to let the camel-http and camel-http4 to share the same common code
base.
                
> Cannot specify which converter to use when several can do the same conversion
> -----------------------------------------------------------------------------
>
>                 Key: CAMEL-6094
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6094
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http, camel-jetty
>            Reporter: Nicolas Lebreton
>
> I use both Camel-Jetty and Camel-http4 components in many routes. Each time a route is
started the following messages appear in logs : 
> 15:16:01,496 | WARN  | xtenderThread-32 | DefaultTypeConverter             | 68 - org.apache.camel.camel-core
- 2.6.0.fuse-01-09 | Overriding type converter from: StaticMethodTypeConverter: public static
java.io.InputStream org.apache.camel.component.http.HttpConverter.toInputStream(javax.servlet.http.HttpServletRequest,org.apache.camel.Exchange)
throws java.io.IOException to: StaticMethodTypeConverter: public static java.io.InputStream
org.apache.camel.component.http4.HttpConverter.toInputStream(javax.servlet.http.HttpServletRequest,org.apache.camel.Exchange)
throws java.io.IOException
> 15:16:01,497 | WARN  | xtenderThread-32 | DefaultTypeConverter             | 68 - org.apache.camel.camel-core
- 2.6.0.fuse-01-09 | Overriding type converter from: StaticMethodTypeConverter: public static
javax.servlet.http.HttpServletRequest org.apache.camel.component.http.HttpConverter.toServletRequest(org.apache.camel.Message)
to: StaticMethodTypeConverter: public static javax.servlet.http.HttpServletRequest org.apache.camel.component.http4.HttpConverter.toServletRequest(org.apache.camel.Message)
> 15:16:01,498 | WARN  | xtenderThread-32 | DefaultTypeConverter             | 68 - org.apache.camel.camel-core
- 2.6.0.fuse-01-09 | Overriding type converter from: StaticMethodTypeConverter: public static
javax.servlet.http.HttpServletResponse org.apache.camel.component.http.HttpConverter.toServletResponse(org.apache.camel.Message)
to: StaticMethodTypeConverter: public static javax.servlet.http.HttpServletResponse org.apache.camel.component.http4.HttpConverter.toServletResponse(org.apache.camel.Message)
> Even if these are warnings, even if the impact is clearly documented, my customers can
not understand why there are so many messages with keywords like IOExceptions and can think
this is linked to my product since they appear each time a route is started. This is why I
have chosen Major as a priority.
> I cannot uninstall neither camel-http4 nor camel-http (which is the most quoted solution
on forums).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message