Right, just know that UDDI can help you find a service and its WSDL, it
only contains a reference to the WSDL, you can add references to
documentation about the service, and one of the documents would be the
WSDL. You'd only add a binding Element under the BusinessService for
each live service endpoint. So the developer can add this binding
Element (where the endpoint can be of type wsdlDocument, which would be
the URL to the WSDL that the live service hosts).
On 6/25/12 7:28 AM, tech evaluator wrote:
Hi,
Is it possible to work with JUDDI in the following scenario
- An architect defines the service contract with name, input
parameters, output parameters, other information in a WSDL file.
Right he can register a BusinessService.
- A service developer finds the unimplemented contract and provides
the implementation for the WSDL. He then maps the contract to its
implementation.
- A service consumer knows about the contract for a service defined by
an architect. He creates an application with service consumption code
just based on the defined contract i.e. he can work on development of
his service consumer code even before the implementation has been
completed for the contract.
Please let me know if I need to be more explanatory.
Thanks a lot for your help.
