Basically what you are proposing to implement is a
Business Delegate which in itself uses aspects of the
Facade and
Adapter pattern. Business Delegates are used to decouple the core business logic from the complexity of dealing with distributed functionality that may be
exposed as EJBs, Message beans, or web services, etc.
The main challenge you will be facing is that most
SOAP web service toolkits will provide their own infrastructure code. Each application server development environment will have its own SOAP toolkit and infrastructure code - so as a rule any "component" built with these tools will not be portable between application servers much less to standalone clients. If portability is a requirement, you either have to use an independent SOAP toolkit that is redistributed with your client package or develop your own infrastructure code based on a lower level API like
SAAJ or even URLConnections with the XML APIs (both of which will duplicate features that are already present in the various development environments).
See also:
Portable J2EE 1.4 Web Services? Facade pattern and Web services