Usually it is best to move such configuration out of your war file.
i.e. use a datasource for your database connection, etc.
You don't want to have to build 3 wars for different environments:
test, usertest and production.
Martijn
On Wed, May 20, 2009 at 9:01 PM, Dane Laverty
Awesome, that's exactly what I was looking for. Thanks!
On Wed, May 20, 2009 at 9:59 AM, Clint Popetz cl...@42lines.net wrote:
I recommend using ${} variables in web.xml and resource filtering, as
you mentioned, but the way to avoid changing them all the time in
pom.xml is to have different
Check out the way I did it in my wicket-advanced example application:
http://svn.carmanconsulting.com/public/wicket-advanced/trunk
I did a combination of maven profiles and Spring's
PropertyPlaceholderConfigurer. If you're not using Spring, it won't
help, but if you are, it might be interesting
Clint - I've run into one (hopefully minor) hitch with the process. The
filtering works, but only after I've used Maven to deploy the project. When
I'm developing, however, I just run the project on the Jetty server that
comes with the Quickstart. Of course, that means that the ${} variables are
On Wed, May 20, 2009 at 2:35 PM, Dane Laverty danelave...@gmail.com wrote:
Clint - I've run into one (hopefully minor) hitch with the process. The
filtering works, but only after I've used Maven to deploy the project. When
I'm developing, however, I just run the project on the Jetty server that
The way I solve that locally (and it may not be a best practice, but
it works, eh?) is to use m2eclipse, so that mvn filtering happens
incrementally as I change things in eclipse. I also set up maven to
copy my src/main/webapp directory into target/test-classes, i.e.:
testResources
Set a system property in your server config or startup script that
tells wicket it's running in deployment mode.
-Dwicket.configuration=deployment is all there's to it.
Martijn
On Wed, May 20, 2009 at 6:40 PM, Dane Laverty danelave...@gmail.com wrote:
I've got my project set up to deploy with
I've got my project set up to deploy with Maven's Tomcat plugin now. My next
step is getting the web.xml to use the correct Wicket configuration
(development/deployment) value. Is there a way to run two separate web.xml
files for the application, and then somehow have Maven pick up the correct
one
I recommend using ${} variables in web.xml and resource filtering, as
you mentioned, but the way to avoid changing them all the time in
pom.xml is to have different maven profiles that set them differently
in your pom. It is true that you'll have to do things like
-PtomcatDeployment when running
Thanks for piping in, Martijn. I should have clarified, my deployment and
development environments use different databases. I'm storing the database
connection information inside of the web.xml also, so I need to be able to
switch those as well as the Wicket configuration depending on the
10 matches
Mail list logo
