I see. The current namespace configuration mechanism uses imports to include other namespaces from dependent modules. We are very likely going to modify this so that multiple target namespaces will be used (e.g. integration, integration-adapters, and integration-ws). The motivation was to keep things simpler, but now that the source and source-endpoint definitions are separated, the use of 3 distinct namespaces seems to make the most sense.
In the meantime, this is the way to handle the "ws" namespace. Please note that this is taken directly from the spring-integration-ws test cases:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:si="http://www.springframework.org/schema/integration"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springframework.org/schema/integration
http://www.springframework.org/schema/integration/spring-integration-ws-1.0.xsd">
<si:message-bus/>
<si:channel id="testChannel"/>
<si:ws-target id="adapterWithDefaultSourceExtractor" uri="http://example.org" channel="testChannel"/>
<si:ws-target id="adapterWithCustomSourceExtractor" uri="http://example.org" channel="testChannel"
source-extractor="sourceExtractor"/>
<bean id="sourceExtractor" class="org.springframework.integration.ws.config.StubSourceExtractor"/>
</beans>