[jboss-dev-forums] [Design of POJO Server] - Re: Profile Service api

[bstansberry@jboss.com]

You guys write way faster than I do. :)

"scott.stark at jboss.org" wrote : Right, there is no notion of sub-profiles. How would the HASingletonDeploymentScanner be changed, deployment phases would be distinct sub-profiles that register with the ProfileService?

I don't see the contents of deploy-hasingleton as being a separate deployment phase; they are just APPLICATION, like everything in deploy.

What's special about them is their location in deploy-hasingleton marks them as belonging to a "hasingleton" subprofile. Registering them with the profile service as belonging to that subprofile could be a function of the scanner that's responsible for scanning that location. Or a function of the profile service impl; i.e. it has a configuration that understands that certain deployment URLs are associated with a particular subprofile. The latter has the advantage of allowing the regular repository HD scanner to scan both deploy and deploy-hasingleton.

Using the scanner in that way is just a convenience for those who can't/won't add some sort of configuration a la what Adrian described above.

The HASingletonDeploymentScanner's functionality them gets broken into 2 pieces:

1) The scanning/registration as part of subprofile function.

2) The activation function Adrian described at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136492&postdays=0&postorder=asc&start=10 .  HASingletonDeploymentActivator calls profileService.deployProfile("hasingleton") when it determines it is the master node.


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

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