This is the case... :-( -----Original Message----- From: Hiranya Jayathilaka [mailto:[email protected]] Sent: donderdag 28 juli 2011 16:15 To: [email protected] Subject: Re: The system cannot infer the transport exception
VFS sender should be enabled in the axis2.xml file used by the message processor. By default it uses the samples/axis2Client/client_repo/conf/axis2.xml file. Thanks, Hiranya On Thu, Jul 28, 2011 at 7:38 PM, De Vleeschauwer Nele < [email protected]> wrote: > The following line is enabled in my config file: > > <transportSender > class="org.apache.synapse.transport.vfs.VFSTransportSender" name="vfs"/> > > -----Original Message----- > From: Hiranya Jayathilaka [mailto:[email protected]] > Sent: donderdag 28 juli 2011 16:01 > To: [email protected] > Subject: Re: The system cannot infer the transport exception > > Check whether the VFS transport sender is enabled in the axis2.xml > > Thanks, > Hiranya > > On Thu, Jul 28, 2011 at 5:56 PM, De Vleeschauwer Nele < > [email protected]> wrote: > > > In our current apache synapse setup, we have configured the following: > > > > - a proxy service which receives an incoming message and stores it > > inside a message store: > > <?xml version="1.0" encoding="UTF-8"?> > > <proxy xmlns="http://ws.apache.org/ns/synapse"; name="testSequence" > > transports="http" startOnLoad="true" trace="disable"> > > <target> > > <inSequence> > > <sequence > > key="conf:/repository/synapse/default/sequences/store"/> > > <property name="FORCE_SC_ACCEPTED" value="true" > > scope="axis2"/> > > <property name="OUT_ONLY" value="true" scope="default"/> > > <property name="target.endpoint" > > value="fileshareEndpointNDV" scope="default"/> > > <log level="full"/> > > </inSequence> > > </target> > > </proxy> > > > > - store sequence: > > <?xml version="1.0" encoding="UTF-8"?> > > <sequence xmlns="http://ws.apache.org/ns/synapse"; name="store" > > trace="enable" statistics="enable"> > > <in> > > <log level="full"/> > > <store messageStore="MemoryMessageStore"/> > > </in> > > <description/> > > </sequence> > > > > We have also defined a message processor, which should pick up the > > messages from the store and deliver it to the endpoint (which was set > > via the target.endpoint property in the proxy service): > > <?xml version="1.0" encoding="UTF-8"?> > > <messageProcessor xmlns="http://ws.apache.org/ns/synapse"; > > > class="org.apache.synapse.message.processors.forward.ScheduledMessageFor > > wardingProcessor" name="ForwardMessageToEndpoint" > > messageStore="MemoryMessageStore"/> > > > > > > Each time when a new message arrives in the message store and the > > message processor functionality is invoked, we have the following > error: > > [2011-07-28 14:22:20,015] DEBUG - BlockingMessageSender Start Sending > > the Message > > [2011-07-28 14:22:20,015] DEBUG - Axis2SynapseEnvironment Creating > > Message Context > > [2011-07-28 14:22:20,015] INFO - MessageHelper Parent's Fault Stack : > > [] : Child's Fault Stack :[] > > [2011-07-28 14:22:20,015] DEBUG - BlockingMessageSender Invoking > service > > Url vfs:file:///D:/DATA/filedropping with > > Messageurn:uuid:3e955b31-55b5-4860-80e5-8bf91b7f9242 > > [2011-07-28 14:22:20,015] ERROR - ClientUtils The system cannot infer > > the transport information from the vfs:file:///D:/DATA/filedropping > URL. > > [2011-07-28 14:22:20,015] ERROR - BlockingMessageSender Error sending > > Message to url : vfs:file:///D:/DATA/filedropping > > org.apache.axis2.AxisFault: The system cannot infer the transport > > information from the vfs:file:///D:/DATA/filedropping URL. > > > > What is wrong here ? > > > > > > > > > > > > ----------------------------------------- > > Visit our website! http://www.nbb.be > > > > "DISCLAIMER: The content of this e-mail message should not be > > construed as binding on the part of the National Bank of Belgium > > (NBB) unless otherwise and previously stated. The opinions > > expressed in this message are solely those of the author and do not > > necessarily reflect NBB viewpoints, particularly when the content > > of this message, or part thereof, is private by nature or does not > > fall within the professional scope of its author." > > > > > -- > Hiranya Jayathilaka > Associate Technical Lead; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
