I think Apache could maybe do this as well.
The location would be the value of the DocumentRoot, which is a property in
the resource configuration of Virtual Host resources.
So each virtual host resource could have the ability to deploy to the
DocumentRoot it defines (this property is not required though so we should
handle failures gracefully here).
On Thursday, June 23, 2011 17:00:28 John Mazzitelli wrote:
I need to finish up the bundle-to-non-platforms feature - the last
thing
is to modify plugin descriptors so resources can be targets for bundles.
What resource types can or should support bundle deployments and where
should those bundle deployments be placed?
For example, in the JBoss AS 4 plugin, I added the ability to put
bundles in two places, the "Install Directory" (denoted by the plugin
configuration holding the home directory path) and the "Profile
Directory" (another plugin configuration property holding the
configuration set path).
What other plugins do we want to provide this kind of thing?
For one, I'm thinking the JBossAS 5 plugin should have the same thing as
the JBossAS 4 plugin.
NOTE: we can target bundles to paths that are stored in a resource's
plugin configuration, resource configuration or a metric trait value. So
if a resource stores a path in some resource config or trait, we can use
that too.
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/rhq-devel