When I build GeoServer with -Pweb2 to create a geoserver.war and deploy it, I get the following dire warnings:
********************************************************************
*** WARNING: Wicket is running in DEVELOPMENT mode. ***
*** ^^^^^^^^^^^ ***
*** Do NOT deploy to your live server(s) without changing this. ***
*** See Application#getConfigurationType() for more information. ***
********************************************************************
What is the correct way to build a GeoServer WAR so that, on deployment, it is in Wicket PRODUCTION mode?
Kind regards,
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Ben Caradoc-Davies ha scritto:
When I build GeoServer with -Pweb2 to create a geoserver.war and deploy it, I get the following dire warnings:
********************************************************************
*** WARNING: Wicket is running in DEVELOPMENT mode. ***
*** ^^^^^^^^^^^ ***
*** Do NOT deploy to your live server(s) without changing this. ***
*** See Application#getConfigurationType() for more information. ***
********************************************************************
What is the correct way to build a GeoServer WAR so that, on deployment, it is in Wicket PRODUCTION mode?
Change the applicationContext.xml file in the web2/app module.
I still haven't figured out a better way (thought for official releases
it's not that bad, you have to make some other changes to files
in the tags anyways)
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Ben Caradoc-Davies ha scritto:
What is the correct way to build a GeoServer WAR so that, on deployment, it is in Wicket PRODUCTION mode?
Change the applicationContext.xml file in the web2/app module.
I think you mean web2/core.
I still haven't figured out a better way (thought for official releases
it's not that bad, you have to make some other changes to files
in the tags anyways)
Is this a job for Maven resource filtering? That way, we could just enable a profile to get deployment bundles with Wicket in deployment mode.
I have never used Maven filtering: I am willing to try, but I'd rather learn how to do it the right way from someone who knows what they are doing, rather than hack something together.
The task is perhaps complicated by each applicationContext.xml being in the src tree, not resources. Will this cause filtering to mangle the java source, or include it inappropriately? Again, if we have someone who knows Maven filtering, I'd like to see how it should be done.
Kind regards,
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia