Search:

I see... so final advice: revert back to the original pom.xml and change slf4j version from 1.5.10 to 1.6.1 like this:
<org.slf4j-version>1.6.1</org.slf4j-version>
Actually I've tested it myself on...

that is funny, but did you even read my first comment? the advice to remove "commons-logging" exclusion? In pom.xml it is one line above the line "<!-- Exclude Commons Logging in favor of SLF4j -->"....

it looks like you did not remove slf4j dependency from pom.xml. Basically remove entire <!-- Logging --> section from pom.xml (everything between <!-- Logging --> and <!-- @Inject --> lines)

What exactly does not work? Are you getting any other exception?

The list of checked exceptions must be compatible with each target join point of the advice. So your join points have to throw APPErrorException and DBErrorException exceptions. What you can throw is...

I would try removing all "commons-logging" exclusions and also all slf4j dependencies. And I would even go further and removed log4j dependency. The result will be that commons-logging will be used...

I'm not sure about that. The doc says "FactoryBean that exposes an arbitrary target bean under a different name.". It exposes a bean that is already managed by a context (but under a different name).

why don't you use directly:
<bean id="foo" class="java.util.concurrent.Executors" factory-method="newCachedThreadPool" />

In the documentation you are referring to there's in section 3.2.3.2.2...

By default compiler plugin uses target and source set to version 1.5.

You can override this and include compiler plugin in your pom.xml:
<build>
<plugins>
<plugin>
...

Similar problem has been discussed already. Try looking over there to see how to combine XML and JavaConfig approach.

Hi,

there's a blog post covering the topic.

Just to quote the last paragraph to give an answer to your question:
"One important takeaway here is that it is the FactoryBean, not the factoried...

Although this question was asked a loong time ago, here is the answer. Don't use "annotatedPackages" but rather "packagesToScan". And the pattern to use is "directory" based (not package based), so...

Try using this:

<dependency>
<groupId>org.springframework.ws</groupId>
<artifactId>spring-ws</artifactId>
<version>1.5.10</version>
</dependency>

so it looks like you're using 2 instances of Apache Tomcat. First is located in C:/Program Files/Apache Software Foundation/Tomcat 6.0/ and second in C:/users/me/apache-tomcat-6.0.14/
Which one are...

Ok, I see. The deployment performs direct copy to webapps directory so no credentials are needed for that. Are you able to login to:
http://localhost:8080/manager/html
from the browser? (Or...

That's quite strange that you were able to deploy you app but not perform list action. Server returned HTTP response code: 401, unauthorized access.
Is you app really successfully deployed?