Win a copy of Soft Skills: The software developer's life manual this week in the Jobs Discussion forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Issue deploying a JSF 1.2/RF 3.3 on JBoss AS7

 
Ouadi Belmokhtar
Greenhorn
Posts: 6
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
 
Mahendr Shinde
Ranch Hand
Posts: 38
Eclipse IDE Java Tomcat Server
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Somewhere in your configuration files like faces-config.xml or web.xml or persistence.xml lies an Error
error is
lineNumber: 5; columnNumber: 13; Error at line 5 char 13: argument type mismatch

You need to describe your problem with little more details.
 
Ouadi Belmokhtar
Greenhorn
Posts: 6
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
2 days earlier when i deploy a web-app on JBoss AS 7, these errors appears, and i'm not able to resolve them. The errors might's triggered because of parsing a Xml file, but which file ? I brows all these 3 files that you say, but all of them are correct.
Help please
 
Tim Holloway
Saloon Keeper
Pie
Posts: 17615
38
Android Eclipse IDE Linux
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
JBoss has JSF 2.0 built into it, as required by the JEE 6 specification. To get JSF1.2 operating in a JBoss 7 server, you must override the built-in JSF with JSF 1.2 api and implementation libraries in your webapp's WEB-INF/lib directory. You must also set certain parameters in your WEB-INF/web.xml file.

The full details for those parameters are listed in the JBoss documentation.
 
Ouadi Belmokhtar
Greenhorn
Posts: 6
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here is JSF declaration in web.xml file :

<context-param>
<param-name>org.jboss.jbossfaces.JSF_CONFIG_NAME</param-name>
<param-value>Mojarra-1.2</param-value>
</context-param>

 
Ouadi Belmokhtar
Greenhorn
Posts: 6
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The solution is to remove the ajax4jsf dependencies from pom.xml.

 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic