Maybe expose it as a trait instead.
On 06/23/2011 11:27 AM, Lukas Krejci wrote:
Would it work if we had a readonly property in the resource
configuration that
would be computed to always contain the absolute path of the document root?
How would resource config updates behave if a request to change the document
root changed yet another property? Would we have duplicate history entries or
is the update logic "smart enough" to just ignore that more has been changed
than was requested for?
On Thursday, June 23, 2011 17:18:43 John Mazzitelli wrote:
> On 06/23/2011 11:10 AM, Lukas Krejci wrote:
>> 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).
> I was JUST adding that, but hit a snag. Reading the xml comments on the
> "DocumentRoot" setting, it says, "If the directory-path is not
absolute
> then it is assumed to be relative to the ServerRoot."
>
> Problem is, if that is a relative path, the bundle stuff has no way of
> knowing where it is relative to (we have no way of saying, "if the
> resource config setting is relative, then it is relative to THIS setting
> over HERE).
> _______________________________________________
> rhq-devel mailing list
> rhq-devel(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/rhq-devel
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/rhq-devel
--
Ian Springer
Principal Software Developer
JBoss Operations Network
Red Hat
ian.springer(a)redhat.com