[jira] Commented: (CAMEL-1309) StringSource is not serializable
[
https://issues.apache.org/activemq/browse/CAMEL-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49097#action_49097
]
Claus Ibsen commented on CAMEL-1309:
Guillaumn can you elaborate?
StringSource extends Externalizable that implements Serializable
public class org.apache.camel.converter.jaxp.StringSource extends StreamSource
implements Externalizable
In StreamCacheConverter there is a SourceCache that extends StringSource and
its missing a no-args constructor.
Could that cause trouble?
{code}
/*
* {...@link StreamCache} implementation for {...@link Source}s
*/
private class SourceCache extends StringSource implements StreamCache {
private static final long serialVersionUID = 4147248494104812945L;
public SourceCache(String text) {
super(text);
}
public void reset() {
// do nothing here
}
}
{code}
StringSource is not serializable
Key: CAMEL-1309
URL: https://issues.apache.org/activemq/browse/CAMEL-1309
Project: Apache Camel
Issue Type: Bug
Components: camel-core
Reporter: Guillaume Nodet
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1310) DelegateProcessor should support async message handling
DelegateProcessor should support async message handling --- Key: CAMEL-1310 URL: https://issues.apache.org/activemq/browse/CAMEL-1310 Project: Apache Camel Issue Type: Improvement Components: camel-core Affects Versions: 1.5.0 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: 1.5.1, 2.0.0 We should improve the default DelegateProcessor to support async Message handling as well. Right now, adding a Tracer, Delayer, StreamCaching, ... to a Route breaks the ability to use asynchronous processing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1309) StringSource is not serializable
[ https://issues.apache.org/activemq/browse/CAMEL-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-1309: --- Fix Version/s: 2.0.0 1.5.1 StringSource is not serializable Key: CAMEL-1309 URL: https://issues.apache.org/activemq/browse/CAMEL-1309 Project: Apache Camel Issue Type: Bug Components: camel-core Reporter: Guillaume Nodet Assignee: Claus Ibsen Fix For: 1.5.1, 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1271) Can only interact with servicemix-http if logging is at DEBUG
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49099#action_49099 ] Gert Vanthienen commented on CAMEL-1271: Fixed for trunk in http://svn.eu.apache.org/viewvc?view=revrevision=740251 and backported to branch in http://svn.eu.apache.org/viewvc?view=revrevision=740263 Darren, could you give it another go with a local build of both Camel and servicemix-camel? Can only interact with servicemix-http if logging is at DEBUG - Key: CAMEL-1271 URL: https://issues.apache.org/activemq/browse/CAMEL-1271 Project: Apache Camel Issue Type: Bug Components: camel-jbi Affects Versions: 1.5.0 Reporter: Darren Davison Assignee: Gert Vanthienen Fix For: 1.5.1, 2.0.0 Given the following camel DSL: from(activemq:queue.testJms.in) .to(jbi:service:urn:oms:testHttp?mep=in-out) .to(activemq:queue.testJms.out); and the following xbean.xml for the smx (3.3) SU: http:endpoint service=oms:testHttp endpoint=testHttp role=provider locationURI=http://localhost:8080/testP1; /http:endpoint then Camel operates correctly (or at least as desired) only if DEBUG logging is enabled in the org.apache.servicemix.http package. This seems to be because a DOMSource is returned (which Camel can convert). If the log level is reduced (say to WARN) then a StreamSource object is returned instead which Camel appears unable to convert. This results in stack traces such as: ERROR - DeadLetterChannel - Failed delivery for exchangeId: ID-davisond-laptop/53380-1232099798317/0-0. On delivery attempt: 0 caught: org.apache.camel.RuntimeCamelException: javax.xml.transform.TransformerException: java.io.IOException: Attempted read on closed stream. org.apache.camel.RuntimeCamelException: javax.xml.transform.TransformerException: java.io.IOException: Attempted read on closed stream. at org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:441) at org.apache.camel.impl.converter.InstanceMethodTypeConverter.convertTo(InstanceMethodTypeCo +nverter.java:57) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1309) StringSource is not serializable
[ https://issues.apache.org/activemq/browse/CAMEL-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49102#action_49102 ] Claus Ibsen commented on CAMEL-1309: Trunk: 740295 1.x: 740297 StringSource is not serializable Key: CAMEL-1309 URL: https://issues.apache.org/activemq/browse/CAMEL-1309 Project: Apache Camel Issue Type: Bug Components: camel-core Reporter: Guillaume Nodet Assignee: Claus Ibsen Fix For: 1.5.1, 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1309) StringSource is not serializable
[ https://issues.apache.org/activemq/browse/CAMEL-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1309. Resolution: Fixed StringSource is not serializable Key: CAMEL-1309 URL: https://issues.apache.org/activemq/browse/CAMEL-1309 Project: Apache Camel Issue Type: Bug Components: camel-core Reporter: Guillaume Nodet Assignee: Claus Ibsen Fix For: 1.5.1, 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1271) Can only interact with servicemix-http if logging is at DEBUG
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49103#action_49103 ] Claus Ibsen commented on CAMEL-1271: Thanks to get we got the camel-jaxb fixed Can only interact with servicemix-http if logging is at DEBUG - Key: CAMEL-1271 URL: https://issues.apache.org/activemq/browse/CAMEL-1271 Project: Apache Camel Issue Type: Bug Components: camel-jbi Affects Versions: 1.5.0 Reporter: Darren Davison Assignee: Gert Vanthienen Fix For: 1.5.1, 2.0.0 Given the following camel DSL: from(activemq:queue.testJms.in) .to(jbi:service:urn:oms:testHttp?mep=in-out) .to(activemq:queue.testJms.out); and the following xbean.xml for the smx (3.3) SU: http:endpoint service=oms:testHttp endpoint=testHttp role=provider locationURI=http://localhost:8080/testP1; /http:endpoint then Camel operates correctly (or at least as desired) only if DEBUG logging is enabled in the org.apache.servicemix.http package. This seems to be because a DOMSource is returned (which Camel can convert). If the log level is reduced (say to WARN) then a StreamSource object is returned instead which Camel appears unable to convert. This results in stack traces such as: ERROR - DeadLetterChannel - Failed delivery for exchangeId: ID-davisond-laptop/53380-1232099798317/0-0. On delivery attempt: 0 caught: org.apache.camel.RuntimeCamelException: javax.xml.transform.TransformerException: java.io.IOException: Attempted read on closed stream. org.apache.camel.RuntimeCamelException: javax.xml.transform.TransformerException: java.io.IOException: Attempted read on closed stream. at org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:441) at org.apache.camel.impl.converter.InstanceMethodTypeConverter.convertTo(InstanceMethodTypeCo +nverter.java:57) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1311) when dependencies are missing, can we report to the user exactly what kinds of jars are typically required?
when dependencies are missing, can we report to the user exactly what kinds of jars are typically required? --- Key: CAMEL-1311 URL: https://issues.apache.org/activemq/browse/CAMEL-1311 Project: Apache Camel Issue Type: Improvement Reporter: James Strachan Fix For: 2.0.0 See this tweet ... http://twitter.com/casron/statuses/1172707316 not exactly sure how we can do it though :) I wonder if when we know there is a class missing, we can deduce some groupId + artifact Id that is typically missing, then we can report on the jars (and the dependencies) missing for that group ID and artifact ID? e.g. if we know that (say) XStream jar is missing, can we report the camel-xstream dependencies that are missing? This typically occurs when we use the apache-camel uber-jar and then the converters can't be registered due to the dependencies not being there. So how about adding (say) camel-xstream knows that jars it requires and has some kinda way (through Maven / OSGi tooling) to auto-generate a list of missing jars? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1311) when dependencies are missing, can we report to the user exactly what kinds of jars are typically required?
[ https://issues.apache.org/activemq/browse/CAMEL-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49109#action_49109 ] Carson McDonald commented on CAMEL-1311: So I think the real issue here is that some of the optional parts log exceptions trying to find dependencies but don't fail. Looking at the logs can become confusing because of these exceptions since they aren't really meaningful. It could work just to hide those exceptions since you are already logging the fact that the part won't work without more dependencies. This led me to think that if I was told that I'm including x.jar that won't work because I don't have the dependencies needed I would just go and remove x.jar. I don't want the dependency list for x.jar, I just want to know that it needs to be removed unless I add the dependencies it needs to function. when dependencies are missing, can we report to the user exactly what kinds of jars are typically required? --- Key: CAMEL-1311 URL: https://issues.apache.org/activemq/browse/CAMEL-1311 Project: Apache Camel Issue Type: Improvement Reporter: James Strachan Fix For: 2.0.0 See this tweet ... http://twitter.com/casron/statuses/1172707316 not exactly sure how we can do it though :) I wonder if when we know there is a class missing, we can deduce some groupId + artifact Id that is typically missing, then we can report on the jars (and the dependencies) missing for that group ID and artifact ID? e.g. if we know that (say) XStream jar is missing, can we report the camel-xstream dependencies that are missing? This typically occurs when we use the apache-camel uber-jar and then the converters can't be registered due to the dependencies not being there. So how about adding (say) camel-xstream knows that jars it requires and has some kinda way (through Maven / OSGi tooling) to auto-generate a list of missing jars? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1312) Restlet component should allow response content type and return code to be set
Restlet component should allow response content type and return code to be set -- Key: CAMEL-1312 URL: https://issues.apache.org/activemq/browse/CAMEL-1312 Project: Apache Camel Issue Type: Bug Components: camel-restlet Reporter: William Tam Assignee: William Tam Fix For: 1.5.1, 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1314) camel-example-reportincident - should work with Tomcat
camel-example-reportincident - should work with Tomcat -- Key: CAMEL-1314 URL: https://issues.apache.org/activemq/browse/CAMEL-1314 Project: Apache Camel Issue Type: Task Components: examples Affects Versions: 2.0.0 Reporter: Claus Ibsen Priority: Minor Fix For: 2.0.0 An end user reported that this example might not work out of the box in Tomcat. Needed to import some cxf imports in the cxf-config.xml file. Just created this ticket to remember to look into it -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
We need to update the maven deploying script of CAMEL
Hi , I just noticed currently deployed CAMEL 2.0-SNAPSHOT is the old version of Camel (before the svn directory changed), so we need to update the deploying script to right svn repository of CAMEL. Thanks, Willem
Re: Need example demonstrating camel-mail support of endpoint sending multipart/alternative message
On Tue, Feb 3, 2009 at 9:19 PM, MarkBi mabis...@cs.indiana.edu wrote: Need an example demonstrating camel-mail support of endpoint sending a multipart/alternative message (plain text body and equivalent html body). ./src/test/java/org/apache/camel/component/mail/MimeMessageConsumeTest.java is an example using javamail transport to send a multipart/alternative but not the camel-mail endpoint. If an example is not readily available, does camel-mail support this or is it a known limitation due to single body exchange? If it is a limitation then is it possible to send 2nd part as attachment (but without filename, disposition, etc...) and with the appropriate alternative content types. Many thanks! Hi I dont think we have such an example. Many of the wiki documentation is usually based on real unit tests. And you have looked what we got. We love contributions, so if you feel like it then please give it a stab at it to add this feature/example that you need. http://camel.apache.org/contributing.html -- View this message in context: http://www.nabble.com/Need-example-demonstrating-camel-mail-support-of-endpoint-sending-multipart-alternative-message-tp21818001s22882p21818001.html Sent from the Camel - Development mailing list archive at Nabble.com. -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/
