Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

autowiring problem when deploying on Jboss through eclipse

 
saad bousf
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm developping an application using Jboss-4.2.3.GA, spring 3.1.0.RC1 (framework, aop,...), Maven 3.3 and eclipse Indigo. If i deploy my webApp on Jboss using a command line jboss:deploy without using Eclipse, the project is deployed corrctly and i run my application very well. Now, for quick testing and deploying purpose, i want to use Eclipse to deploy the same web app on a jboss server added to eclipse servers and linked to the same external jboss server. The entry to my web app is always the same: a simple servlet (Bonjour.java) wich must call an autowired spring bean (promoteurPresInt) . The problem is that this bean is not wired. Debug shows that it's null.

Web.xml:




spring-context-ressources.xml:


the bean PromoteurPres.java:



the interface implemented by my bean

PromoteurPresInt.java:




La servelett Bonjour.java:




It seems like jboss need some additional library or config when launching a spring application on it through eclipse???
Pliz Save me!
 
Vyas Sanzgiri
Ranch Hand
Posts: 686
Chrome Netbeans IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would suggest approaching this by using log4j in debug mode so that detailed logs are generated.

I use these logs to understand what is throwing errors or why things are not working
 
saad bousf
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you Vyas!

I have just configured Log4j for spring. It work very well, but no logs are trigered when the problem occur. I m going to chek if it's because i didnt create the project containing the bean the same way than the project containing the servlet. In fact, i created its by 2 diffrents versions of m2eclipse. I will keep you in touch.

 
saad bousf
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hy Vyas!

I found the source of the problem. It was done by cheking the two war. the one genereted by m2eclipse and wtp and the one genrated by maven binaries directly. A spring context file was absent in wtp one. it was due to the bad donwloding of an RC version of spring dependency. now i m using an older version of spring core 3 and it works very well.

Tx!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic