Chris,

Many thanks for your help on this much appreciated. It worked perfectly.

Vince

Chris Custine wrote:
> 
> Try setting "copyProperties=true" on all of your intermediate endpoints
> (XSLT and the web service call).  The DefaultFileMarshaler sets a property
> when it polls the original file and if that property exists when it
> reaches
> the file sender it will use that file name.  Don't set any of the
> prefix/suffix properties on the sender endpoint.  If any of the
> intermediate
> endpoints don't copy the properties over to the out message the file name
> is
> lost.
> 
> Chris
> --
> Chris Custine
> FUSESource :: http://fusesource.com
> My Blog :: http://blog.organicelement.com
> Apache ServiceMix :: http://servicemix.apache.org
> Apache Directory Server :: http://directory.apache.org
> 
> 
> On Wed, Mar 11, 2009 at 8:08 AM, vinceblogg
> <[email protected]>wrote:
> 
>>
>> All,
>>
>> Apologies if this is a numpty uestion but I've had a fair trawl now and
>> not
>> seen a documented example. I have the following setup:
>>
>> File Poller > XSLT > Web Service > XSLT > File Sender
>>
>> I'd like the output file to have the same name as the input file. Is
>> there
>> a
>> way to do this solely with configuration. I've seen a couple of posts
>> referring to the file marshaler but I could really use a worked example.
>> We've resorted to this route given we've had difficulties getting JMS
>> queues
>> to work with Adobe LiveCycle. The application needs to know which file
>> relates to which running process at the livecycle end.....which isn't a
>> problem with a correlation id on a queue, but is a problem in this
>> scenario.
>>
>> Thanks in advance if anyone can help
>>
>> Vince
>> --
>> View this message in context:
>> http://www.nabble.com/servicemix-file-tp22455886p22455886.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/servicemix-file-tp22455886p22461463.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to