[Yanel-dev] Make WAR files deployable without reconfiguration
Guillaume Déflache
guillaume.deflache at wyona.com
Tue May 25 10:46:18 CEST 2010
Michael Wechner schrieb:
> Michael Wechner wrote:
>> Hi
>>
>> Apart from the logging I have now implemented alternative methods to
>> load the realms configuration, whereas I have added some documentation to
>>
>> http://www.yanel.org/en/documentation/configuration/realms_xml.html
>
> I just noticed that one "minor" problem with this approach is that
> having more than one Yanel context within a Tomcat instance, all Yanel
> context will access the same realms.xml
Ooops, you're right! :/
Maybe we could use simply (mis)use the webapp display name (the
/web-app/display-name element in web.xml) to differentiate them?
> I guess not many people will run more than one Yanel context within the
> same Tomcat instance, but having downgrade and upgrade functionality it
> might be the case.
>
> I think it's important that we keep this mind and maybe reconsider the
> loading order.
Maybe we could add an option in local.build.properties to delete
yanel.xml and/or realms.xml from WAR so that for the case of deployment
we can try to load them 1st, and only when not present then fallback to
the other newly-introduced strategies?
More information about the Yanel-development
mailing list