I want to define in a "repository" all my own services, whrere some of them will be finally "web services", and other will be invocated in other ways (directly how Java class, RMI, JMS, ....).
I want to standardize the input/output of all my services and keep a definition service of each one into a repository, and create a little framework to manage services through that repository information.
I have thought to do it using a WSDL document for each one of my own service (although I know some parts of the WDSL only can be applied to Web services).
1) How I don't want to reinvent the wheel, how can I manipulate the WSDL documents in Java?
Originally posted by Janfry Nice: I have thought to do it using a WSDL document for each one of my own service (although I know some parts of the WDSL only can be applied to Web services).
Well matters are even worse than that. In terms of long term stability you would be well advised to not exercise the WSDL specification to the full extent but actually constrain yourself to the subset as allowed by the WSI Basic Profile (e.g. Basic Profile Version 1.1)
Now if you want some ideas on how to structure services so that they can be more easily exposed thought multiple interfacing technologies or protocols then this article might be of interest:
In it the same service is simply exposed via "SOAP over HTTP" and "XML over HTTP" (so it can use WSDL to describe both).
Other than that, trying to describe all kinds of interfaces implemented using different technologies and protocols in one uniform way and storing these descriptions in one single repository is a bit ambitious unless you restrict your spectrum of supported interfacing technologies and protocols severely.