I'm not aware that there is a WSDL based restriction against mixing message exchangepatterns in the same port type. In fact it is quite natural to have a "subscribe" In-Out operation and a "publish" Out-In (or Out-Only) operation in the same portType.
However looking at the semantics of your portType the Out-In message exchange seems misplaced. If a service offers an In-Out "searchEmployee" operation then I would also expect an In-Out "getEmployeeDetails" operation.
Also just because something is legal WSDL doesn't automatically imply that it is supported by your SOAPweb service stack (or that of your web service consumer for that matter).
Ayub ali khan
posted 9 years ago
Thank you for your comment. I agree with you. I wanted to have an independent view on this point. I was also expecting getEmployeeDetails would have same symantics as that of searchEmployee.
SCEA part I,TOGAF Foundation
If you try to please everybody, your progress is limited by the noisiest fool. And this tiny ad: