Mark Thomas wrote:
> Mark Thomas wrote:
>
>> Filip Hanik - Dev Lists wrote:
>>
>>> is no longer being picked up, at least not in my test.
>>> I think it's related to the deploy refactor that has been going on,
>>> possibly related to
>>> https://issues.apache.org/bugzilla/show_bug.cgi?id=47343
>>>
>> Possibly. I'll take a look.
>>
>
> AFAICT, className would never have been picked up in the global
> context.xml or from the host level context.xml.default. Those files are
> read in ContextConfig which itself is created from StandardContext. By
> the time the code gets to that point it is too late to change the
> Context implementation class.
>
> If this were to be implemented, HostConfig would need to parse any
> application context.xml file, any host context.xml.default file and the
> global context.xml file and make the right selection for className based
> on override and the presence, or not, of className in any of those files.
>
> Since no-one has asked for this, I'd prefer to add a note to the docs
> that className only has an effect if used in an application context.xml
> file.
>
let me noodle on a fix, I think it could be very simple.
> Mark
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
|