I think you want to use the webservice_producer quickstart as your SOAP entry point reference. This will require JBossAS and JBossWS.
I posted an example of this on a thread a week or 2 ago http://www.jboss.com/index.html?module=bb&op=viewtopic&t=127028 that does this using PHP as the client but can easily be changed to whatever you want.
Hope this helps
I think that I'm having the same roadblock as the orig poster, and the response post didn't clear up my confusion.
My requirement is to have a web service (for which we have a WSDL defined) exposed on the bus, which can then satisfy the request using one of a few legacy services. The web service is a proxy, hosted by the bus, for legacy functionality. The webservice producer quickstart appears to demonstrate transport mediation. Control leaves the bus when the JBossWS web service is called (thus the JBossWS service isn't 'fronting' for the Bus at all). The idea of web service proxying in the sense that I described is core in some other bus products, such as BEA's aqualogic.
If I am misunderstanding the webservice producer action or am otherwise confused, please accept my apologies in advance. ;)
Here is one general rule of thumb.
If the WS in question is hosted in-vm, in-container on JBossWS then use SOAPProcessor as that also allows you to expose your ESB Service as a WS as well (seen in webservice_producer)
If the WS in question is hosted on BEA, IBM, Tomcat, .NET, Coldfusion, etc. in other words on some 3rd party and you simply wish to interact with that WS endpoint somewhere in the action pipeline then use the SOAPClient action (seen in webservice_consumer)
Here is the worst case scenario, use wsconsume.bat to build a proxy/client/stub for the remote WS and use those classes in side of your action.