[jboss-dev-forums] [Design of POJO Server] - Re: Sub-Profiles ProfileService changes

[bstansberry@jboss.com]

As I commented above, I think my HASingletonProfileManager class is the wrong approach. It's a temporary expedient.

It's wrong because something inside a Profile is adding content to the ProfileService at runtime.  That means the ProfileService isn't aware of the content unless there is a running AS underneath it that deployed the HASingletonProfileManager.

So, we're better than the AS 5.0.0 case where the ProfileService is only aware on content if there is a running AS underneath *and* it's the master. But still not where we should be.

To get where we should be I think we need something like the MC ControllerMode concept added to ProfileMetaData:

<profiles name="deploy-hasingleton">
  | 
  | 	<profile name="deploy-hasingleton-controller">
  | 		<source type="mutable">${jboss.server.base.url}deploy</source>
  | 		<deployment>cluster/deploy-hasingleton-jboss-beans.xml</deployment>
  | 	</profile>
  | 
  | 	<profile name="deploy-hasingleton-content" mode="MANUAL">
  | 		<source type="mutable">${jboss.server.base.url}deploy-hasingleton</source>
  | 	</profile>
  | 
  | </profiles>

In this case "MANUAL" means just register the profile but don't activate it; activation requires that something call ProfileService.activateProfile().

Probably different terms than the ControllerModes would be better since the semantics are not identical.

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

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