...
Depending on the protocols used by the services, you might also be able to use third-party tools like soapUI, JMeter, or various commercial tools to test the services when they are deployed to ServiceMix.
Complex Services
Can you have a mix of WSDL standards (1.1 and 2.0) in the same deployment?
Sure. Each Normalized Message will typically correspond to the WSDL for a given service, and there's nothing preventing different services from using different WSDL versions. Just make sure your messages comply with the WSDL for the service they're going to.
What is the service lifecycle?
This is defined by JBI. For a Service Unit, states can be:
- Deployed (but not initialized or running)
- Initialized (but not running)
- Running
For some more insight into state transitions, see the JBI ServiceUnitManager JavaDoc.
However, not all services will necessarily see the initialized state – it depends on the JBI component hosting the service and what it exposes to its services.
What happens if a service is updated with different WSDL?
So long as existing operations are not changed, the service should continue to accept all Normalized Messages that it previously would have.
If new operations are added, then they will become available when the new WSDL takes effect (e.g. when the Service Unit with the WSDL is redeployed).
Of course, you would want to coordinate changes to routing, transformation, or orchestration that depend on changes to the service's WSDL. (This is easiest for anything deployed in the same Service Assembly as the service in question.)