Hi, Another usefull behaviour I think that we should provide is the ability set some property for vfs inbound, so that when the file is moved/copied the original name will be appended by some sequence number or a time stamp. This will be usefull in case if the third party application is generating the same file name each time it is deposited to the in folder and it will help to track all files being processed without overwriting the previous files.
Eranga. Eranga Perera Senior Lead Solutions Engineer WSO2, Inc. Mobile : +94 72 778 4250 [email protected] On Dec 12, 2015 4:52 PM, "Kalyani Yogeswaranathan" <[email protected]> wrote: > Hi Kirishanthy, > > These resources may help you to get some knowledge about VFS Transport[1] > and File inbound[2]. > > 1. https://docs.wso2.com/display/ESB490/VFS+Transport > 2. https://docs.wso2.com/display/ESB490/File+Inbound+Protocol > 3. > > https://github.com/wso2/carbon-mediation/tree/master/components/inbound-endpoints > > Thank you. > > On Fri, Dec 11, 2015 at 11:49 AM, Jagath Sisirakumara Ariyarathne < > [email protected]> wrote: > >> Hi, >> >> To get the input for polling interval/cron configuration, how about using >> a toggle button like in Scheduled Tasks. >> >> [image: Inline image 1] >> >> In this case, we can set interval as default selection. Based on the >> selection, you can use required implementation. >> >> Thanks. >> >> On Fri, Dec 11, 2015 at 10:56 AM, Kirishanthy Tharmalingam < >> [email protected]> wrote: >> >>> Hi all , >>> >>> Now I'm working on following improvement in the VFS inbound and ESB >>> polling inbound. >>> >>> 1. For VFS inbound we only have the option to delete or move file >>> after processed or after error. Need to give the options copy and leave >>> as >>> it is. >>> 2. Current ESB polling inbound only support interval. But we need to >>> have the ability to schedule it using cron expressions. >>> >>> In first case leave as it is the good option because we can used the >>> same file again and again. >>> In the copy option we copy the same file again and again, so If the file >>> is already exist in the destination directory delete the file and copy the >>> file again. >>> use case of copy option is we can update the content of the file(because >>> it is exist in the source directory), then the next polling we can copy the >>> updated file to the destination directory.(because delete the existing file >>> in the destination directory and copy the updated file). Is there any >>> other use case? Please correct if am I wrong. >>> >>> In the second case,I'm using the separate UI field for getting value >>> for interval and cron , If the cron value is available then polling is >>> working with cron time period , if the cron is not available then the >>> polling is working with the interval. >>> Is there a different way to implement this feature? >>> >>> -- >>> Thanks & Regards, >>> Kirishanthy >>> Associate Software Engineer >>> Mobile : +94 778333939 >>> [email protected] >>> >> >> >> >> -- >> Jagath Ariyarathne >> Technical Lead >> WSO2 Inc. http://wso2.com/ >> Email: [email protected] >> Mob : +94 77 386 7048 >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > *Kalyani Yogeswaranathan* > > *Associate software engineer* > *WSO2 Inc.* > > *Mobile: 0776390284* > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
