File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Web Services and the fly likes Manipulate WSDL documents. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Manipulate WSDL documents." Watch "Manipulate WSDL documents." New topic
Author

Manipulate WSDL documents.

Janfry Nice
Greenhorn

Joined: Oct 10, 2005
Posts: 7
Hello.

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?

2) Any other solution to define the repository?

Any other ideas will be appreciated.

Thanks in advance,

Janfry
Jesus Angeles
Ranch Hand

Joined: Feb 26, 2005
Posts: 2046
UDDI might help. Java has an API for it - JAXR.
Peer Reynders
Bartender

Joined: Aug 19, 2005
Posts: 2906
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:

Playing Together Nicely: Getting REST and SOAP to Share Each Other's Toys

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.

UDDI repositories are limited to SOAP Web Services.
Apache jUDDI
UDDI4J (Formerly from IBM)
[ July 07, 2006: Message edited by: Peer Reynders ]

"Don't succumb to the false authority of a tool or model. There is no substitute for thinking."
Andy Hunt, Pragmatic Thinking & Learning: Refactor Your Wetware p.41
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Manipulate WSDL documents.
 
Similar Threads
Any feedback for SCDJWS Beta?
[Query on Discovery of RESTFul Services] Leonard , Sam
Newbie
General Doubts in WebServices after Fibonacci Example
Need some explanations about web-services basics.