I looked at my pom.xml and I'm not creating a new JVM for each test. I wanted to reuse the same application context for all of my tests instead of reloading it before every test.
Here's that...
Type: Posts; User: elusivemel; Keyword(s):
I looked at my pom.xml and I'm not creating a new JVM for each test. I wanted to reuse the same application context for all of my tests instead of reloading it before every test.
Here's that...
Hmmm...
First, I tried Arthur's suggestion and added created log4j.properties file in 'src/test/resources'. I even moved all of my Spring test *-context.xml files to that directory. Maven runs...
Thanks for the response, momania.
Since I'm using Maven2, I added a new folder src/main/resources to the project, then added the folder to the list of testResources:
<testResources>...
Perhaps I'm a bit slow, but I'll ask the question anyway.
I've managed to configure my application to use Log4J when it is deployed to Tomcat by making the following changes to my web.xml:
...
I've checked my jms-context.xml thoroughly and don't see anything out of place, so I'm going to assume that the problem is related to Spring not finding a proper handler for namespace...
This could be a silly thing, but I haven't been able to make any sense of it after quite some time, so here goes.
Here's my JMS context file, nothing fancy:
<?xml version="1.0"...
This is a strange question, but I'll ask it anyway.
I have a mainframe application that is posting data to my Spring-MVC Java application. I'm using ServletRequestDataBinder to bind request...
I moved this post to the Web forum where it belongs. Sorry about that.