autowiring problem when deploying on Jboss through eclipse

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:

<listener>
        <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
    </listener>

<context-param>
        <param-name>contextConfigLocation</param-name>
        <param-value>
            classpath*:/ma/epromo/spring-base-*.xml
            classpath*:/ma/epromo/spring-server-*.xml
        </param-value>
    </context-param>

<servlet>
        <servlet-name>Ressources</servlet-name>
        <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
        <init-param>
            <param-name>contextConfigLocation</param-name>
            <param-value>/WEB-INF/spring-context-ressources.xml</param-value>
        </init-param>
        <load-on-startup>1</load-on-startup>
    </servlet>

<servlet-mapping>
        <servlet-name>Ressources</servlet-name>
        <url-pattern>/res/*</url-pattern>
    </servlet-mapping>

<servlet>
        <servlet-name>bijour</servlet-name>
        <servlet-class>org.springframework.web.context.support.HttpRequestHandlerServlet</servlet-class>
    </servlet>
    <servlet-mapping>
        <servlet-name>bijour</servlet-name>
        <url-pattern>/bijour</url-pattern>
    </servlet-mapping>

spring-context-ressources.xml:

the bean PromoteurPres.java:

the interface implemented by my bean

PromoteurPresInt.java:

La servelett Bonjour.java:

package ma.epromo.servlet;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import ma.epromo.presentation.common.PromoteurPresInt;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.transaction.annotation.Transactional;
import org.springframework.web.HttpRequestHandler;

public class Bonjour  implements HttpRequestHandler {

private static final long serialVersionUID = 1L ;

@Autowired
    private PromoteurPresInt promoteurPresInt;
    @Transactional
    public void handleRequest(HttpServletRequest request, HttpServletResponse httpServletResponse) throws ServletException, IOException {

//The call where the bean is null!!!!!
        promoteurPresInt.createPromoteur();

httpServletResponse.setContentType("text/html");

PrintWriter out = httpServletResponse.getWriter();
        out.println("<html>");
        out.println("<head>");
        out.println("<title>XOR</title>");
        out.println("</head>");
        out.println("<body>");
        out.println("<h1>servlet !</h1>");
        out.println("</body>");
        out.println("</html>");
    }

}

It seems like jboss need some additional library or config when launching a spring application on it through eclipse???
Pliz Save me!

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

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.

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!