You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2007/10/13 09:48:23 UTC
[jira] Created: (SM-1104) Type converters not working in ServiceMix
Type converters not working in ServiceMix
-----------------------------------------
Key: SM-1104
URL: https://issues.apache.org/activemq/browse/SM-1104
Project: ServiceMix
Issue Type: Bug
Components: servicemix-camel
Reporter: Gert Vanthienen
Fix For: 3.2
Currently, the Camel type converters do not work inside ServiceMix. Consider this example (replacing the eip:wire-tap in our tutorial using Camel)
{code}
from("jbi:service:urn:servicemix:tutorial:wiretap")
.convertBodyTo(DOMSource.class)
.to("jbi:endpoint:urn:servicemix:tutorial:jms:myQueue", "jbi:endpoint:urn:servicemix:tutorial:file:sender");
{code}
The snippet intends to convert the StreamSource, coming from the <file:poller/> to a DOMSource for sending it to both other endpoints, but conversion never happens. Haven't really looked into this, but it might be a classloading issue..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1104) Type converters not working in
ServiceMix
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40453 ]
James Strachan commented on SM-1104:
------------------------------------
I think this could be a gremlin in the servicemix-camel's JbiMessage implementation whcih wasn't keeping track of the setBody() value; have patched it...
> Type converters not working in ServiceMix
> -----------------------------------------
>
> Key: SM-1104
> URL: https://issues.apache.org/activemq/browse/SM-1104
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-camel
> Reporter: Gert Vanthienen
> Fix For: 3.2
>
>
> Currently, the Camel type converters do not work inside ServiceMix. Consider this example (replacing the eip:wire-tap in our tutorial using Camel)
> {code}
> from("jbi:service:urn:servicemix:tutorial:wiretap")
> .convertBodyTo(DOMSource.class)
> .to("jbi:endpoint:urn:servicemix:tutorial:jms:myQueue", "jbi:endpoint:urn:servicemix:tutorial:file:sender");
> {code}
> The snippet intends to convert the StreamSource, coming from the <file:poller/> to a DOMSource for sending it to both other endpoints, but conversion never happens. Haven't really looked into this, but it might be a classloading issue..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1104) Type converters not working in
ServiceMix
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved SM-1104.
---------------------------------
Resolution: Fixed
This commit (https://svn.apache.org/viewvc?view=rev&revision=587048) by James Strachan fixed the issue
> Type converters not working in ServiceMix
> -----------------------------------------
>
> Key: SM-1104
> URL: https://issues.apache.org/activemq/browse/SM-1104
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-camel
> Reporter: Gert Vanthienen
> Fix For: 3.2
>
>
> Currently, the Camel type converters do not work inside ServiceMix. Consider this example (replacing the eip:wire-tap in our tutorial using Camel)
> {code}
> from("jbi:service:urn:servicemix:tutorial:wiretap")
> .convertBodyTo(DOMSource.class)
> .to("jbi:endpoint:urn:servicemix:tutorial:jms:myQueue", "jbi:endpoint:urn:servicemix:tutorial:file:sender");
> {code}
> The snippet intends to convert the StreamSource, coming from the <file:poller/> to a DOMSource for sending it to both other endpoints, but conversion never happens. Haven't really looked into this, but it might be a classloading issue..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.