When I try to use the following camel component inside a Camel route, I
receive the following two errors :
- The element type "File" must be terminated by the matching end-tag
"</File>". This is strange because my XML file ended with a tag </File> (see
below),
- ERROR - FileComponent - Failed to process file:
c:\temp\test\.camel\ordersXML.csv. Reason: javax.jbi.me
ssaging.MessagingException: Could not find route for exchange: InOnly[
Is this error related to the previous or has not relation ?
Regards,
Charles
INFO - Message send to the endpoint - Exchange[FileMessage:
c:\temp\test\ordersXML.csv]
WARN - FileComponent - Target service
({urn:org:apache:servicemix:camel-swift}swiftDSLRouter) and endp
oint (camelReceiver) specified, but no matching endpoint found. Only the
service will be used for routing.
WARN - DefaultBroker - ServiceName
({urn:org:apache:servicemix:camel-swift}swiftDSLRouter) specified f
or routing, but can't find it registered
WARN - DefaultBroker - ServiceName
({urn:org:apache:servicemix:camel-swift}swiftDSLRouter) specified f
or routing, but can't find it registered
[Fatal Error] :3:79: The element type "File" must be terminated by the
matching end-tag "</File>".
ERROR - FileComponent - Failed to process file:
c:\temp\test\.camel\ordersXML.csv. Reason: javax.jbi.me
ssaging.MessagingException: Could not find route for exchange: InOnly[
id: ID:172.16.10.128-1194c770021-8:0
status: Active
role: provider
service: {urn:org:apache:servicemix:camel-swift}swiftDSLRouter
in: Unable to display: org.xml.sax.SAXParseException: The element type
"File" must be terminated by the matching end-t
ag "</File>".
] for service: {urn:org:apache:servicemix:camel-swift}swiftDSLRouter and
interface: null
javax.jbi.messaging.MessagingException: Could not find route for exchange:
InOnly[
id: ID:172.16.10.128-1194c770021-8:0
status: Active
role: provider
service: {urn:org:apache:servicemix:camel-swift}swiftDSLRouter
in: Unable to display: org.xml.sax.SAXParseException: The element type
"File" must be terminated by the matching end-t
ag "</File>".
] for service: {urn:org:apache:servicemix:camel-swift}swiftDSLRouter and
interface: null
at
org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(DefaultBroker.java:297)
at
org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket(SecuredBroker.java:81)
at
org.apache.servicemix.jbi.container.JBIContainer.sendExchange(JBIContainer.java:830)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:395)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.sendSync(DeliveryChannelImpl.java:470)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.sendSync(DeliveryChannelImpl.java:442)
at
org.apache.servicemix.common.EndpointDeliveryChannel.sendSync(EndpointDeliveryChannel.java:96)
at
org.apache.servicemix.common.endpoints.SimpleEndpoint.sendSync(SimpleEndpoint.java:71)
at
org.apache.servicemix.file.FilePollerEndpoint.processFile(FilePollerEndpoint.java:282)
at
org.apache.servicemix.file.FilePollerEndpoint.processFileAndDelete(FilePollerEndpoint.java:253)
at
org.apache.servicemix.file.FilePollerEndpoint$1.run(FilePollerEndpoint.java:231)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Remarks :
- Version of servicemix : 3.3-SNAPSHOT
- Version of Camel : 1.3-SNAPSHOT
- XML file :
<File name="orders.csv" location="C:\Temp\test\orders.csv">
<Line number="1">1,bank1,10,20,sale</Line>
</File>
- Camelroute defined in my java class:
from("file:///c:/temp/test")
.to("log:Message send to the endpoint");
- Camelcontext declared in a ServiceMix SU
- <camelContext id="camel3" useJmx="false" mbeanServer="mbeanServer"
xmlns="http://activemq.apache.org/camel/schema/spring";>
<package>com.xpectis.routing</package>
</camelContext>
RomKal wrote:
>
> 2008/4/14, cmoulliard <[EMAIL PROTECTED]>:
>>
>> Nobody answer to this question : Does it make sense to mix endpoints of
>> Camel
>> with JBI ?
>
> It definitely makes sense. Especially in certain situations like using
> TCP/IP connectivity through Camel just because SMX (If we are talking
> about SMX) doesn't have TCP/IP JBI component.
>
> BTW As far as I know SMX 4.x does it - it exposes Camel
> endpoints/flows to the bus (if we ignore JBI compatibility layer).
>
> Roman
>
>
--
View this message in context:
http://www.nabble.com/Mix-camel-endpoint-with-jbi-endpoint-in-camel-routes---tp16627803s22882p16676062.html
Sent from the Camel - Users mailing list archive at Nabble.com.
