Hi Asankha

I am using synapse version 1.2. probably that is the problem. I will
checkout the SNAPSHOT version later today. Leaving the scope in the
get-property function will result in an error:

2009-07-22 12:39:28,178 [-] [vfs-Worker-7]  WARN SynapseConfigUtils IO
Error reading from URL : <dir to
synapse>/./repository/filenamejava.io.FileNotFoundException: <dir to
synapse>/./repository/filename (No such file or directory)

Regard Niek

On Wed, 2009-07-22 at 15:00 +0530, Asankha C. Perera wrote:
> Hi Niek
> > Thank you again for the quick response. I have also tried this but thr
> > problem seems that properties set in the inSequence are not available
> > in the outSequence
> This cant be! I just tested this before I shared the configuration...
> Which version of Synapse are you using? I tried with a snapshot from
> probably a few weeks back..
> > <inSequence>
> > <property action='set' name="filename"
> > expression="fn:concat(get-property('SYSTEM_DATE', 'yyMMddHHmmss') ,
> > '-', get-property('transport', 'FILE_NAME'), '.xml')"
> > scope='transport' />
> > <log level="custom">
> > <property name="show-name"
> > expression="get-property('transport','filename')" />
> ## Don't do this.. if you want to check if the 'filename' property was
> set correctly as required to be read in the outSequence, just use
> get-property('filename') and drop the transport scope this time..
> > So first I compose the name and assign it to the property filename.
> > Next I write the variable to the log. Now I am sure the variable is
> > set correctly.
> Well .. the code is right to set it.. but your reading was faulty..
> > <outSequence>
> > <log level="custom">
> > <property name="-filename-" expression="get-property('transport',
> > 'filename')" />
> > </log>
> This is wrong.. you can share properties only in the default scope - and
> thus you will not have the transport scope available during inSequence
> in your outSequence
> > <property name="transport.vfs.ReplyFileName"
> > expression="get-property('filename', 'transport')" />
> Make sure to mark this message as OUT_ONLY too as shown in my example
> 
> Cheers
> asankha
> 
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to