[jira] [Commented] (CAMEL-6094) Cannot specify which converter to use when several can do the same conversion
[ https://issues.apache.org/jira/browse/CAMEL-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14662993#comment-14662993 ] Claus Ibsen commented on CAMEL-6094: All those http components from Camel 2.16 now uses shared type converters in the camel-http-common module, so you should not see those duplicates anymore. 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: Improvement Components: camel-http, camel-jetty Reporter: Nicolas Lebreton Assignee: Claus Ibsen Fix For: 2.16.0 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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-6094) Cannot specify which converter to use when several can do the same conversion
[ https://issues.apache.org/jira/browse/CAMEL-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14663036#comment-14663036 ] Claus Ibsen commented on CAMEL-6094: There is also new options on type converter registry you can use to configure what to do: override, ignore or fail. and as well the logging level. 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: Improvement Components: camel-http, camel-jetty Reporter: Nicolas Lebreton Assignee: Claus Ibsen Fix For: 2.16.0 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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-6094) Cannot specify which converter to use when several can do the same conversion
[ https://issues.apache.org/jira/browse/CAMEL-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14003155#comment-14003155 ] Martin Lichtin commented on CAMEL-6094: --- Is there a workaround available to get rid of these warnings? They still appear with Camel 2.12.3. 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: Improvement Components: camel-http, camel-jetty Reporter: Nicolas Lebreton Fix For: Future 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 was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-6094) Cannot specify which converter to use when several can do the same conversion
[ https://issues.apache.org/jira/browse/CAMEL-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
