Drop RPC-style remoting: Hessian, HTTP Invoker, JMS Invoker, JAX-WS

[jhoeller]

Since most of our RPC-style remoting support has been officially and/or effectively deprecated for several years, let's remove it for 6.0 M1 right away (which also reduces subpackage overload in several modules a bit).

[knoobie]

@jhoeller Are there any recommended strategies documented by Spring how to get JAX-WS working with the latest Spring Framework / Boot again? Especially removal of ignoreResourceType("javax.xml.ws.WebServiceContext"); (now jakarta.*) breaks integration with CXF 4.0 by default if WebServiceContextis injected as @Resource with no clear migration path how to overcome this.

[snicoll]

As stated above, it's been deprecated for several years and now removed so we can't recommend anything about those.

[knoobie]

@snicoll Thanks for your comment! I'm aware of the deprecating and removal of RPC-style remoting (I'm totally find with that). I just came across this commit because it also removed JAX-WS "Integration" which I think is not deprecated and still heavily used. For example from the CXF 4 / Jakarta 9+ Migration, there is this open issue that lead me to this change: https://issues.apache.org/jira/browse/CXF-8666

My current workaround is to customize the CommonAnnotationBeanPostProcessorand re-introduce the deleted line.

@Configuration
public class WorkaroundForCxfConfig {

  @Autowired
  private CommonAnnotationBeanPostProcessor processor;

  @PostConstruct
  public void initialize() {
    processor.ignoreResourceType("jakarta.xml.ws.WebServiceContext");
  }
}

[snicoll]

JAX-WS "Integration" which I think is not deprecated and still heavily used.

Our JAX-WS integration is deprecated and has been removed as a result, so whatever you were relying on from there is not available anymore. This isn't the right place to discuss CXF issues either, please raise that on the proper support channel.