I found a post here (
http://n2.nabble.com/BPEL-abstract-WSDL-with-two-operations-td1628886.html) with a partial work around but it looks like the answer is "No CASA does not support that" - which is really too bad because it adds to the complexity of client applications.
If you have a hard time understanding the problem Im referring to, take the standard Purchase Order application that is often used as an example (see HTTP/Soap BC documentation). In that example a single operation was used: purchaseOrder. In the real world there would be (at least) 3 other operations, findOrder, changeOrder and cancelOrder. A client application would then need to connect and maintain contexts for 4 web services. Likewise if WS-import is used in the build process there will be 4 WS-import steps generating essentially the same code because all 4 wsdls contain the same operations, classes etc. Each client interface would have 4 methods - three of which are unimplemented on the service side. This is a coding nightmare in the making.
Anyone else have a problem with this?
[Message sent by forum member 'beaninfo' (beaninfo)]
http://forums.java.net/jive/thread.jspa?messageID=333416