We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Affects: \6.0.13
I am migrating code from Spring 5 to 6. This code was working in 5 but not in 6.
@Configuration public class MyBeansProducer { @Bean public MyDAO createDAO() { return new MyDAO(); } }
public class MyDAO { @WebServiceRef(WSMyInterfaceHttpService.class) public void setRef(Ref wsRef ) { this.wsRef = wsRef ; } }
Problem is that setRef is never invoked.
setRef
I have found this code in Spring 5 that used to make this work: https://github.com/spring-projects/spring-framework/blob/5.3.x/spring-context/src/main/java/org/springframework/context/annotation/CommonAnnotationBeanPostProcessor.java#L406
I'm not sure if this is a bug? If it is not a bug, I think it should be mentioned clearly somewhere in the docs.
I also asked on StackOverflow
The text was updated successfully, but these errors were encountered:
@tomasbjerre I am afraid this is to be expected. JAX-WS support has been removed in Spring Framework 6, see #27422, and the now upgraded Upgrading to Spring Framework 6.x wiki page.
Sorry, something went wrong.
No branches or pull requests
Affects: \6.0.13
I am migrating code from Spring 5 to 6. This code was working in 5 but not in 6.
Problem is that
setRef
is never invoked.I have found this code in Spring 5 that used to make this work:
https://github.com/spring-projects/spring-framework/blob/5.3.x/spring-context/src/main/java/org/springframework/context/annotation/CommonAnnotationBeanPostProcessor.java#L406
I'm not sure if this is a bug? If it is not a bug, I think it should be mentioned clearly somewhere in the docs.
I also asked on StackOverflow
The text was updated successfully, but these errors were encountered: