Clarification the semantic of defaultEndpoint in the reference documentation

[duskox]

Hello,

I am reading through this documentation and what is unclear in section 5.4. is the defaultEndpoint definition and use.

First in previous sections it is shown how to define the default endpoint only via XML, not with Annotations.

Second issue is that it is mentioned that defaultEndpoint is used when the mapping is not found, in case of processing SOAP messages, where implementation is following these guidelines, but it is not clear if this defaultEndpoint will be called irregardless of namespace and localPart defined in @PayloadRoot or not? I ask this because what happens if namespace and localPart are not defined or empty? How does defaultEndpoint deal with that? This I did not try as I am not managing to define a defaultEndpoint with annotation based definitions.

Thanks,
Dusko

[snicoll]

First of all, sorry it took so long to triage this.

The default endpoint is used if no mapping is found for a particular request. So it doesn't matter what values are specified in the annotation. If those values do not result in finding a mapping, then the default endpoint is invoked.

This I did not try as I am not managing to define a defaultEndpoint with annotation based definitions.

It's a bit tricky I agree. If you use @EnableWs it will configure a number of beans for you automatically. Rather than using @EnableWs you can extend from DelegatingWsConfiguration and override the relevant bean definition:

public class MyWsConfiguration  extends DelegatingWsConfiguration {

	@Bean
	public PayloadRootAnnotationMethodEndpointMapping payloadRootAnnotationMethodEndpointMapping() {
		PayloadRootAnnotationMethodEndpointMapping endpointMapping = super.payloadRootAnnotationMethodEndpointMapping();
		endpointMapping.setDefaultEndpoint(<yourDefaultEndpointHere>);
		return endpointMapping;
	}
}

And then replace @EnableWs by @Import(MyWsConfiguration.class).

You could avoid all of that by overriding the bean but that's not recommended and might go away in a future release of the Spring Framework.

I'll use this issue to clarify the documentation but we'll have to do something for the java-based config in another issue as it looks more involved than it should.

[snicoll]

but we'll have to do something for the java-based config in another issue as it looks more involved than it should.

Turns out I was wrong, this is the expected way. @EnableWebMvc uses the exact same mechanism.

[duskox]

Hey, thanks for getting to this. The project is long over and I forgot a lot since, but I remember I managed to do it in the end by treating any request that does not have a mapped endpoint as an error and then I had a custom error handler I wrote where I examined the message.
I have to say that I believe some messages send were not totally up to the SOAP standard, but I could not change that, it was a 3rd party service.
Will pull this project from history and see if I can do it differently per your suggestions. Thanks!