This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

The bean that has problems is the xfire.servletController. When I remove its definition, my WebContext loads without any problem. When I add it, it gives me this exception :
org.springframework.beans.factory.UnsatisfiedDepen dencyException: Error creating
bean with name 'xfire.servletController' defined in class path resource [spring
/xfire.xml]: Unsatisfied dependency expressed through constructor argument with
index 1 of type [javax.servlet.ServletContext]: Ambiguous constructor argument t
ypes - did you specify the correct bean references as generic constructor argume
nts?

Comment

I get that exception if I have two constructor-args with the same index, but it doesn't look like you have that problem.....

This problem is really weird because I seem to be the only guy on earth to have this problem. Tons of users seem to use XFire SOAP support without any problem, and I can't even deploy it because of this Spring error...

Comment

Are you 100% sure there is not in fact an older version of XFire somewhere in your classpath (look in your servlet container's lib dir for example), which possibly is being picked up (and has a constructor with two arguments)?

Comment

This is definitely what is happening here. You are actually instantiating an old version of XFire, which is somewhere on your classpath: The constructor in this class changed some time back in February. See here:

Comment

This is definitely what is happening here. You are actually instantiating an old version of XFire, which is somewhere on your classpath: The constructor in this class changed some time back in February. See here: