[jboss-dev-forums] [Design of POJO Server] - Re: The DeploymentManager and ProfileService

[scott.stark@jboss.org]

"emuckenhuber" wrote : 
  | Therefore we could have one HDScanner thread per profile and DeploymentManager suspends the scanner,
  | when it's uploading contents.
  | 
  | Because i think in the end there will be quite a lot of immutable profiles (defined over xml), where you basically
  | don't have hot-deployment scanning.
  | And just the deploy/ directory and the clustering directories as hot-deployment profiles.
  | IMHO as soon, as you define deployments in a profile, it does not make sense to search for new content.
  | 

I'm not sure what your getting at with the last statement. We certainly will have hot deployment, and so a dynamic profile is needed. I would think that the distinction between dynamic/static should be explicit and the current code in the HDScanner that obtains the active profiles would get the dynamic profiles:


  |       // Get the active profiles
  |       Collection<ProfileKey> dynamicProfiles = profileService.getDynamicProfileKeys();
  |       if(activeProfiles == null || activeProfiles.isEmpty())
  |       {
  |          if( trace )
  |             log.trace("End deployment scan, no dynamic profiles");
  |          return;
  |       }
  | 

I would say the DeploymentManager disabled dynamic profile access using the ProfileService rather than knowing about an HDScanner.

However, the problem is that in general a scan will have started just before the DeploymentManager has disabled the dynamic profile access, so either the new upload has to wait for the current scan to complete (which there currently is no good way to do), or the upload has to deal with concurrency. 

Actually, since the upload needs to be targeted to a profile, if only dynamic profiles support adding content, one can know if there is an active query for the modified deployments and block the upload until its done. 

Let's sketch out all of the usecases of N dynamic profiles, any of which can be updated via direct access and the DeploymentManager to come up with a stable solution and base the spi from that.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205981#4205981

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205981