Hi All, The current way of monitoring artifacts changes in the Carbon-Deployment is to poll the File System for Last-Modified-Date[1].
java.nio.file package provides a WatchService which quite does the same job and has optimizations for the *native* support of the most of the File System implementations when it is available. As per the oracle docs[2] it is also recommended for a deployer task; It is also well suited for an application server that watches a directory, > perhaps waiting for .jsp or .jar files to drop, in order to deploy them. > > WDYT? [1] https://github.com/wso2/carbon-deployment/blob/master/components/org.wso2.carbon.deployment.engine/src/main/java/org/wso2/carbon/deployment/engine/internal/Utils.java#L38 [2] http://docs.oracle.com/javase/tutorial/essential/io/notification.html -- With Regards, *Rasika Perera* Software Engineer M: +94 71 680 9060 E: [email protected] LinkedIn: http://lk.linkedin.com/in/rasika90 WSO2 Inc. www.wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
