David, I have described why an ESB should not rely on a certain technology for interactivity. Primarily because in the field we are often using ESBs to integrate legacy systems, which generally don't use JBossWS for web services. This could be Axis providing the WSDL, or CXF, or even a ColdFusion application deployed on JBoss.
The point is, none of our actions should be called SoapProxy and then make it so it only works in certain cases.
Only the internal:// scheme is specific to JBossWS.
Another point is, just by making the thing lazy load, the whole issue and special protocol and the lot could be simply avoided.
In your words, "Brad, read the full post." I have explained why using lazy load would not simply work.