[jira] Created: (SM-1090) JBI 1.0 compatibility layer: Offline tool to transform JBI artifacts in OSGi bundles
JBI 1.0 compatibility layer: Offline tool to transform JBI artifacts in OSGi bundles Key: SM-1090 URL: https://issues.apache.org/activemq/browse/SM-1090 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Bruce Snyder Fix For: 4.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1091) Deployment bundle for JBI artifacts
Deployment bundle for JBI artifacts --- Key: SM-1091 URL: https://issues.apache.org/activemq/browse/SM-1091 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
ServiceMix 4.0 documentation
I was wondering if we should create a separate wiki space for ServiceMix 4.0 documentation. Also I need to take a look at how the camel book works: it generates a pdf from the wiki, so maybe we could do the same... -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Created: (SM-1093) NPE - FTP Sender Endpoint
NPE - FTP Sender Endpoint
-
Key: SM-1093
URL: https://issues.apache.org/activemq/browse/SM-1093
Project: ServiceMix
Issue Type: Bug
Components: servicemix-ftp
Affects Versions: 3.1.1
Environment: Windows XP / Servicemix 3.1.1
Reporter: Noseda Anne
FTP Sender Endpoint config :
ftp:sender service=cosu:FtpService
endpoint=FtpEndpoint
overwrite=true
uri=ftp://root:[EMAIL PROTECTED]/usr/ftp/cosu /
Error Log :
ERROR - FtpComponent - Error processing exchange InOnly[
id: ID:192.168.80.76-1156f58bd83-2:1
status: Active
role: provider
service: {http://www.etnic.be/janus/test/cosu}FtpService
endpoint: FtpEndpoint
in: ?xml version=1.0 encoding=UTF-8?ftpResult0123456789;1;MED
9876543210;1;ING
/ftpResult
]
java.lang.NullPointerException
at
org.apache.servicemix.ftp.FtpSenderEndpoint.processInOnly(FtpSenderEndpoint.java:176)
at
org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
jms flow in servicemix 3.x?
do JMS flow in servicemix 3.x can't implement distributed registry? -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28SM-1066%29-Distributed-registry-tf4489753s12049.html#a13070107 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
