VFS: how to configure synapse to use input file name for the output file name
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
VFS: how to configure synapse to use input file name for the output file name
by Niek Palm
::
Rate this Message:
I am trying to confiugre synapse to pick up files for the file system
(vfs) send them to a web services an write the response to the file syste. I succees this basic scenario. Now I want to write the webservice response to a file that has the same file name as its origin. The problem is that I cannot not access the FILE NAME when the webservice is invoked. So I can I transfer a property to other mediators (e.g. form inSequence to outSequence). Here is my configuration: <proxy name="FileProxy" transports="vfs"> <parameter name="transport.vfs.FileURI">file:///opt/synapse/inbox </parameter> <parameter name="transport.vfs.ContentType">application/xml</parameter> <parameter name="transport.vfs.FileNamePattern">.*\.xml</parameter> <parameter name="transport.PollInterval">1</parameter> <parameter name="transport.vfs.MoveAfterProcess">file:///opt/synapse/processed </parameter> <parameter name="transport.vfs.MoveAfterFailure">file:///opt/synapse/failed </parameter> <parameter name="transport.vfs.ActionAfterProcess">DELETE</parameter> <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter> <parameter name="transport.vfs.MoveTimestampFormat">yyMMddHHmmss</parameter> <target> <inSequence> <log level="custom"> <property name="filename" expression="get-property('transport', 'FILE_NAME')" /><property name="transport.vfs.ReplyFileName" </log> <send> <endpoint key="soapService"></endpoint> </send> </inSequence> <outSequence> <property name="transport.vfs.ReplyFileName" expression="fn:concat(get-property('SYSTEM_DATE', 'yyMMddHHmmss') , '-', get-property('????', '??? ref to FILE???'), '.xml')" scope="transport" /> <send> <endpoint> <address uri="vfs:file:///opt/synapse/outbox" /> </endpoint> </send> </outSequence> </target> </proxy> Best Regard, Niek Palm ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2 |
|
|
Re: VFS: how to configure synapse to use input file name for the output file name
by Ruwan Linton
::
Rate this Message:
Hi Niek,
All the properties of the in path of the message will be there for the out path as well. So you can directly use the property name "filename" to retrieve the file name at the outSequence. <property name="transport.vfs.ReplyFileName" expression="fn:concat(get-property('SYSTEM_DATE', 'yyMMddHHmmss'), '-', get-property('filename'), '.xml')" scope="transport" /> Hope this helps... Thanks, Ruwan 2009/7/22 Niek Palm <niek.palm@...> > I am trying to confiugre synapse to pick up files for the file system > (vfs) send them to a web services an write the response to the file > syste. I succees this basic scenario. Now I want to write the webservice > response to a file that has the same file name as its origin. The > problem is that I cannot not access the FILE NAME when the webservice is > invoked. So I can I transfer a property to other mediators (e.g. form > inSequence to outSequence). > > Here is my configuration: > > > <proxy name="FileProxy" transports="vfs"> > <parameter name="transport.vfs.FileURI">file:///opt/synapse/inbox > </parameter> > <parameter name="transport.vfs.ContentType">application/xml</parameter> > <parameter name="transport.vfs.FileNamePattern">.*\.xml</parameter> > <parameter name="transport.PollInterval">1</parameter> > <parameter > name="transport.vfs.MoveAfterProcess">file:///opt/synapse/processed > </parameter> > <parameter > name="transport.vfs.MoveAfterFailure">file:///opt/synapse/failed > </parameter> > <parameter name="transport.vfs.ActionAfterProcess">DELETE</parameter> > <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter> > <parameter > name="transport.vfs.MoveTimestampFormat">yyMMddHHmmss</parameter> > > <target> > <inSequence> > <log level="custom"> > <property name="filename" expression="get-property('transport', > 'FILE_NAME')" /><property name="transport.vfs.ReplyFileName" > </log> > > <send> > <endpoint key="soapService"></endpoint> > </send> > > </inSequence> > > <outSequence> > > <property name="transport.vfs.ReplyFileName" > expression="fn:concat(get-property('SYSTEM_DATE', > 'yyMMddHHmmss') , > '-', > get-property('????', '??? ref to FILE???'), > '.xml')" > scope="transport" /> > <send> > <endpoint> > <address uri="vfs:file:///opt/synapse/outbox" /> > </endpoint> > </send> > </outSequence> > </target> > </proxy> > > Best Regard, Niek Palm > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ruwan@...; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com |
|
|
Re: VFS: how to configure synapse to use input file name for the output file name
by Asankha C. Perera
::
Rate this Message:
Hi Niek
Forwarding the reply from Ruwan directly to you, since your original email went into moderation.. so I am assuming you are not subscribed to have received Ruwan's reply. Please ensure that you subscribe to the list as per information mentioned in http://synapse.apache.org/mail-lists.html cheers asankha > Hi Niek, > > All the properties of the in path of the message will be there for the out > path as well. So you can directly use the property name "filename" to > retrieve the file name at the outSequence. > > <property name="transport.vfs.ReplyFileName" > expression="fn:concat(get-property('SYSTEM_DATE', 'yyMMddHHmmss'), '-', > get-property('filename'), '.xml')" scope="transport" /> > Hope this helps... > > Thanks, > Ruwan > > > 2009/7/22 Niek Palm <niek.palm@...> > > >> I am trying to confiugre synapse to pick up files for the file system >> (vfs) send them to a web services an write the response to the file >> syste. I succees this basic scenario. Now I want to write the webservice >> response to a file that has the same file name as its origin. The >> problem is that I cannot not access the FILE NAME when the webservice is >> invoked. So I can I transfer a property to other mediators (e.g. form >> inSequence to outSequence). >> >> Here is my configuration: >> >> >> <proxy name="FileProxy" transports="vfs"> >> <parameter name="transport.vfs.FileURI">file:///opt/synapse/inbox >> </parameter> >> <parameter name="transport.vfs.ContentType">application/xml</parameter> >> <parameter name="transport.vfs.FileNamePattern">.*\.xml</parameter> >> <parameter name="transport.PollInterval">1</parameter> >> <parameter >> name="transport.vfs.MoveAfterProcess">file:///opt/synapse/processed >> </parameter> >> <parameter >> name="transport.vfs.MoveAfterFailure">file:///opt/synapse/failed >> </parameter> >> <parameter name="transport.vfs.ActionAfterProcess">DELETE</parameter> >> <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter> >> <parameter >> name="transport.vfs.MoveTimestampFormat">yyMMddHHmmss</parameter> >> >> <target> >> <inSequence> >> <log level="custom"> >> <property name="filename" expression="get-property('transport', >> 'FILE_NAME')" /><property name="transport.vfs.ReplyFileName" >> </log> >> >> <send> >> <endpoint key="soapService"></endpoint> >> </send> >> >> </inSequence> >> >> <outSequence> >> >> <property name="transport.vfs.ReplyFileName" >> expression="fn:concat(get-property('SYSTEM_DATE', >> 'yyMMddHHmmss') , >> '-', >> get-property('????', '??? ref to FILE???'), >> '.xml')" >> scope="transport" /> >> <send> >> <endpoint> >> <address uri="vfs:file:///opt/synapse/outbox" /> >> </endpoint> >> </send> >> </outSequence> >> </target> >> </proxy> >> >> Best Regard, Niek Palm >> -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com |
|
|
Re: VFS: how to configure synapse to use input file name for the output file name
by Niek Palm
::
Rate this Message:
Hi Asankha,
Thank you for you hint, unfortunately this one of the things I have tried and it is not working. The get-property('filename') returns an empty or null as result. The synapse log gives the following error: INFO TimeoutHandler This engine will expire all callbacks after : 86400 seconds, irrespective of the timeout action, after the specified or optional timeout 2009-07-22 09:53:35,389 [127.0.1.1-niek-laptop] [HttpClientWorker-1] WARN SynapseConfigUtils IO Error reading from URL : /<dirs>/./repository/FileNamejava.io.FileNotFoundException: /<dirs>/./repository/FileName (No such file or directory) It seem getting the property results in some IO action.... I am not sure if I correct but to me it seems I have to deal with in / out to the file system and another in / out from web service to fs. Maybe you have a working example? Best Regards, Niek Palm > > cheers > asankha > > Hi Niek, > > > > All the properties of the in path of the message will be there for the out > > path as well. So you can directly use the property name "filename" to > > retrieve the file name at the outSequence. > > > > <property name="transport.vfs.ReplyFileName" > > expression="fn:concat(get-property('SYSTEM_DATE', 'yyMMddHHmmss'), '-', > > get-property('filename'), '.xml')" scope="transport" /> > > Hope this helps... > > > > Thanks, > > Ruwan > > > > > > 2009/7/22 Niek Palm <niek.palm@...> > > > > > >> I am trying to confiugre synapse to pick up files for the file system > >> (vfs) send them to a web services an write the response to the file > >> syste. I succees this basic scenario. Now I want to write the webservice > >> response to a file that has the same file name as its origin. The > >> problem is that I cannot not access the FILE NAME when the webservice is > >> invoked. So I can I transfer a property to other mediators (e.g. form > >> inSequence to outSequence). > >> > >> Here is my configuration: > >> > >> > >> <proxy name="FileProxy" transports="vfs"> > >> <parameter name="transport.vfs.FileURI">file:///opt/synapse/inbox > >> </parameter> > >> <parameter name="transport.vfs.ContentType">application/xml</parameter> > >> <parameter name="transport.vfs.FileNamePattern">.*\.xml</parameter> > >> <parameter name="transport.PollInterval">1</parameter> > >> <parameter > >> name="transport.vfs.MoveAfterProcess">file:///opt/synapse/processed > >> </parameter> > >> <parameter > >> name="transport.vfs.MoveAfterFailure">file:///opt/synapse/failed > >> </parameter> > >> <parameter name="transport.vfs.ActionAfterProcess">DELETE</parameter> > >> <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter> > >> <parameter > >> name="transport.vfs.MoveTimestampFormat">yyMMddHHmmss</parameter> > >> > >> <target> > >> <inSequence> > >> <log level="custom"> > >> <property name="filename" expression="get-property('transport', > >> 'FILE_NAME')" /><property name="transport.vfs.ReplyFileName" > >> </log> > >> > >> <send> > >> <endpoint key="soapService"></endpoint> > >> </send> > >> > >> </inSequence> > >> > >> <outSequence> > >> > >> <property name="transport.vfs.ReplyFileName" > >> expression="fn:concat(get-property('SYSTEM_DATE', > >> 'yyMMddHHmmss') , > >> '-', > >> get-property('????', '??? ref to FILE???'), > >> '.xml')" > >> scope="transport" /> > >> <send> > >> <endpoint> > >> <address uri="vfs:file:///opt/synapse/outbox" /> > >> </endpoint> > >> </send> > >> </outSequence> > >> </target> > >> </proxy> > >> > >> Best Regard, Niek Palm > >> > ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2 |
|
|
Re: VFS: how to configure synapse to use input file name for the output file name
by Asankha C. Perera
::
Rate this Message:
Hi Niek
Well if your pasted configuration seems wrong in XML too :) ? .. anyway trick is to set a property 'filename' in the inSequence, and set it to the FILE_NAME property from the transport on reading. The response is then saved in the outSequence using the 'filename' thus saved. Here is a working config created from sample 254 (http://synapse.apache.org/Synapse_Samples.html#Sample254) cheers asankha > ... >>>> <log level="custom"> >>>> <property name="filename" expression="get-property('transport', >>>> 'FILE_NAME')" /><property name="transport.vfs.ReplyFileName" >>>> </log> >>>> ... -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com <!-- ~ Licensed to the Apache Software Foundation (ASF) under one ~ or more contributor license agreements. See the NOTICE file ~ distributed with this work for additional information ~ regarding copyright ownership. The ASF licenses this file ~ to you under the Apache License, Version 2.0 (the ~ "License"); you may not use this file except in compliance ~ with the License. You may obtain a copy of the License at ~ ~ http://www.apache.org/licenses/LICENSE-2.0 ~ ~ Unless required by applicable law or agreed to in writing, ~ software distributed under the License is distributed on an ~ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~ KIND, either express or implied. See the License for the ~ specific language governing permissions and limitations ~ under the License. --> <!-- Using the file system as transport medium using VFS transport listener and sender --> <definitions xmlns="http://ws.apache.org/ns/synapse"> <proxy name="StockQuoteProxy" transports="vfs"> <parameter name="transport.vfs.FileURI">file:///tmp/in</parameter> <!--CHANGE--> <parameter name="transport.vfs.ContentType">text/xml</parameter> <parameter name="transport.vfs.FileNamePattern">.*\.xml</parameter> <parameter name="transport.PollInterval">15</parameter> <parameter name="transport.vfs.MoveAfterProcess">file:///tmp/out</parameter> <!--CHANGE--> <parameter name="transport.vfs.MoveAfterFailure">file:///tmp/out</parameter> <!--CHANGE--> <parameter name="transport.vfs.ActionAfterProcess">MOVE</parameter> <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter> <target> <inSequence> <property name="filename" expression="get-property('transport','FILE_NAME')"/> <log level="full"> <property name="file name" expression="get-property('filename')"/> </log> </inSequence> <endpoint> <address uri="http://localhost:9000/services/SimpleStockQuoteService"/> </endpoint> <outSequence> <property action="set" name="OUT_ONLY" value="true"/> <property name="transport.vfs.ReplyFileName" expression="get-property('filename')" scope="transport"/> <send> <endpoint> <address uri="vfs:file:///tmp"/> <!--CHANGE--> </endpoint> </send> </outSequence> </target> </proxy> </definitions> |
|
|
Re: VFS: how to configure synapse to use input file name for the output file name
by Niek Palm
::
Rate this Message:
Hi Asankha,
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. I have also tried other scopes then transport (which is the default). The XML in the previous mail could be invalid since I removed non relevant data. <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')" /> </log> <send> <endpoint key="soapService"></endpoint> </send> </inSequence> 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. <outSequence> <log level="custom"> <property name="-filename-" expression="get-property('transport', 'filename')" /> </log> <property name="transport.vfs.ReplyFileName" expression="get-property('filename', 'transport')" /> <send> <endpoint> <address uri="vfs:file:///opt." /> </endpoint> </send> </outSequence> But noe I don't see the file name in de logging, I see: 2009-07-22 10:52:19,704 [127.0.1.1-niek-laptop] [HttpClientWorker-1] INFO LogMediator -filename- = null So it seems the properties are not shared between mediators (inSequence / outSequence). I hope you have another hint. Regards, Niek On Wed, 2009-07-22 at 13:57 +0530, Asankha C. Perera wrote: Hi Niek Well if your pasted configuration seems wrong in XML too :) ? .. anyway trick is to set a property 'filename' in the inSequence, and set it to the FILE_NAME property from the transport on reading. The response is then saved in the outSequence using the 'filename' thus saved. Here is a working config created from sample 254 (http://synapse.apache.org/Synapse_Samples.html#Sample254) cheers asankha > ... >>>> <log level="custom"> >>>> <property name="filename" expression="get-property('transport', >>>> 'FILE_NAME')" /><property name="transport.vfs.ReplyFileName" >>>> </log> >>>> ... ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2 |
|
|
Re: VFS: how to configure synapse to use input file name for the output file name
by Asankha C. Perera
::
Rate this Message:
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 -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com |
|
|
Re: VFS: how to configure synapse to use input file name for the output file name
by Niek Palm
::
Rate this Message:
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 > ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2 |
| Free embeddable forum powered by Nabble | Forum Help |
