asynchronous Processing with BPEL

Hi, I have two issues regarding the server: 1. asynchronous processing 2. keep WSDL 1) I have tried to manage creating an asynchronous process with Eclipse and wso2. I have examined the example- process in the /samples-dir which had two portsTypes/bindings etc. . During design time there is no problem but deployment of the process shows that only one portType/binding etc. is created for the process. This also happens if the sample- process is removed from the server (removing .zip from /bpel-dir) and deployed after that again. I have read that it is a problem with axis2- wsdl generation. But how can this be solved for wso? Example: bpel-wsdl (designtime): portType name="sampleProcess" operation name="initiate" input message="tns:sampleProcessRequestMessage" operation portType portType name="sampleProcessCallback" operation name="onResult" input message="tns:sampleProcessResponseMessage" operation portType bpel-wsdl (runtime): portType name="sampleProcess" operation name="initiate" input message="tns:sampleProcessRequestMessage" operation portType 2) How is it possible to define for the server to keep the created WSDL for the server and not to generate new names for e.g. "portType" Example: bpel-wsdl (designtime): portType name="sampleProcess" operation name="process" input message="tns:sampleProcessRequestMessage" output message="tns:sampleProcessResponseMessage" operation portType bpel-wsdl (after deployment): wsdl:portType name="sampleProcessServicePortType" wsdl:operation name="process" wsdl:input message="ns0:sampleProcessRequestMessage" wsaw:Action="http://soa.bpm.sample.process/process" wsdl:output message="ns0:sampleProcessResponseMessage" wsaw:Action="http://soa.bpm.sample.process/sampleProcess/processResponse" wsdl:operation wsdl:portType Best reagrds thomas