Last but not least - the deploymentManager is one of the remaining parts which are making
the cleanup of the profileservice-spi a bit harder.
Especially the basic locking which is done when copying a file into a hot-deployment
So maybe we want to remove the enableModifiedDeploymentChecks from the Profile spi:
| public interface Profile
| * Enable/disable the getModifiedDeployments results. This can be
| * used to disable the getModifiedDeployments results during
| * periods such as bootstrap where changes should be delayed.
| * @see #getModifiedDeployments
| * @param flag - the enable/disable flag
| void enableModifiedDeploymentChecks(boolean flag);
And just have a HDScanner.suspendProfile(ProfileKey key) and
to avoid that the folder is hot-deployment checked when the DeploymentManager is copying a
Not sure if that makes more sense, but i think the enableModifiedDeploymentChecks in the
Profile spi maybe should not be there.
View the original post :
Reply to the post :