Is there a way we can control the order on which BPEL jars are deployed? Typically as services depend on one another it'd be nice if the deployer can check the children are up. I'm asking because the UDDI design calls for dynamically pulling in the wdsl from WS endpoints and some of that happens at deploytime.
Gary Brown says:
The services only depend upon the interfaces of the other services, not the actual implementations.
Don't think we should be expecting all services to be up and running before an invoking service is deployed - that would increase the coupling/dependencies between implementations, which is not a good thing.
What specifically needs to be done at deployment time, that couldn't wait for the actual lookup to occur prior to invocation?
The issue i that createPartnerChannel is called during the deployment of the bpel.jar. So the wsdl can of the partner channel can only be read if it is deployed. This works fine if it is all contained in the one bpel.jar, however if the partner service is deployed in another archive, then we can have deployment order issues.
|Retrieving data ...|