"emuckenhuber" wrote : 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
folder.
| So maybe we want to remove the enableModifiedDeploymentChecks from the Profile spi:
|
The locking and enableModifiedDeploymentChecks were hacks to get the hot deployment
scanning from interfering with copying new deployment content. The repository itself could
either have this flag if its still needed, or just put the burden on the repository
implementation to handle concurrency better. The externalized locking and
enableModifiedDeploymentChecks were hacks to avoid concurrency problems I was seeing, so
first consider just removing them.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205969#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...