[jboss-dev-forums] [Design of POJO Server] - Re: Controlling deployments via a barrier bean
adrian@jboss.org
do-not-reply at jboss.com
Wed Jun 4 11:26:33 EDT 2008
"scott.stark at jboss.org" wrote : Its not completely true that:
| anonymous wrote :
| | 1) A scanner that populates the profile is a behavior of the basic profile service, but not of the full repository-based profile service. In the full version it's the DeploymentRepository impl itself that scans the filesystem for content.
| |
| in that you could still have an hasingleton scanner adding content to a profile regardless of what profile service implementation is in use. There should be a flag indicating that the deployment should not be a permanent part of the profile though. Is the APPLICATION_CLUSTERED phase going to be useful? Maybe this should be APPLICATION_TRANSIENT or some such to indicate a deployment that will not be remembered across restarts.
|
If that is the case then you also could say (regardless of clustering) that a hot
deployment scanner could be added to any profile service implementation.
Again this orthogonal.
It's then a hybrid profile service implementation. Where some sub-profiles
come from a versioned repository and others are unversioned in a directory.
Whichever way you look at it, its still a sub-profile of the profile in operation
and needs some "metadata" to say how/if/when it gets activated.
Ideally this should be a part of the management console where somebody can
say this sub-profile/deployment gets activated according to this policy,
where the policy is a part of the profile itself.
As I was trying to explain above, (but got side-tracked in implementation details :-)
for fine-grained it gets harder because the link to the policy might be
annotation on a pojo or a piece of metadata in jboss.xml, etc.
That's why I suggested a jboss-activation.xml to try to make it easier to manage.
The downside is it pushes the responsibility of this new metadata to the subsystems
to read it, since only they know what it means to activate their fine-grained component.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155727#4155727
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155727
More information about the jboss-dev-forums
mailing list