search

azizlabib2015 / jmesa

Automatically exported from code.google.com/p/jmesa
0 stars 0 forks source link

After adding JMesa 3.0.4 gives error (SEVERE: Exception starting filter struts2 java.lang.NoSuchMethodError: com.opensymphony.xwork2.config.ConfigurationManager.addContainerProvider) on Apache Tomcat/6.0.35 #341

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

1> Create a WAR file with all software components except JMesa 3.0.4 using 
Maven. All softwares to be included in the attached pom.xml.
2> Deploying this in Tomcat/6.0.35 and verifying that the deployment is success.
3> Now adding relevant entry in pom.xml to include JMesa 3.0.4 from Central 
Repository,building the war file and deploying in Tomcat/6.0.35. This 
deployment fails with error :
19 Aug, 2012 9:57:50 AM 
org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter struts2
java.lang.NoSuchMethodError: 
com.opensymphony.xwork2.config.ConfigurationManager.addContainerProvider(Lcom/op
ensymphony/xwork2/config/ContainerProvider;)V
    at org.apache.struts2.dispatcher.Dispatcher.init_DefaultProperties(Dispatcher.java:310)

What is the expected output? What do you see instead?
> WAR file should get deployed in Tomcat 3.0.5.Existing application must run as 
it is unaware of JMesa been added.

What version of the product are you using? On what operating system?
> Jmesa 3.0.4 on Windows 7 Home Basic (6.1.7601 Service Pack 1 Build 
7601)

Please provide any additional information below.
> I am building a web application consisting of 
Spring 3.0.5, Struts 2.3.3, Spring Security 3.0.5, Display Tag 1.2, 
Struts2-Jquery plugin 3.3.1.I already have Display Tag but would also like to 
use JMesa in the application.The WAR file built runs on Tomcat.
After including the JMesa 3.0.4 in the WAR file, deployment of the WAR file 
fails in Tomcat 3.0.5.

I had added following entry in pom.xml to pull JMesa from Central Repository 
(http://search.maven.org/#artifactdetails|org.jmesa|jmesa|3.0.4|jar)
<dependency>
    <groupId>org.jmesa</groupId>
    <artifactId>jmesa</artifactId>
    <version>3.0.4</version>
</dependency>

I have included for reference 
1>web.xml
2>pom.xml

Please let me know if you need any other files or any other information to 
troubleshoot the cause.

Original issue reported on code.google.com by vilp...@gmail.com on 19 Aug 2012 at 4:59

Attachments: