[jboss-dev-forums] [Design of POJO Server] - Re: Clustered DeploymentRepository for 5.1

[emuckenhuber]

ManagementView is handling all active profiles, so that should be fine.

But i'm not really sure about the DeploymentManager. I mean it should be possible to define to which profile you want to add your content. 
Although we might need to drop the loadProfile and releaseProfile, as this does not seem to be thread safe. 
It might make more sense to have just:


  |   deploymentMgr.distribute(String name, URL url, boolean copyContent);
  |   // and
  |   deploymentMgr.distribute(String name, URL url, ProfileKey key);
  | 

Whereas the 2nd way would imply copyContent == true. As transient deployments are handled by a own profile now.

So we might want to have load() where it creates a mapping between a deployment and the profile. So you can stop and remove all deployments easily. And for distribute and start we would need to cache the DeploymentID with it's profile. And those stuff will get cleaned when you do release(). 

There is a sort of defaultProfileKey notion - so when you do e.g. profileService.getActiveProfile(new ProfileKey(null)); it would return the profile associated with ProfileKey($jboss.server.name}).
So distribute(String name, URL url, copyContent = true) would add it to the injected default profile.

Whereas we might also want to differentiate between a normal Profile and a MutableProfile - where you can add and remove content.

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

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