jUDDI has the policy tModel defined:
<tModel tModelKey="uddi:uddi.org:specification:v3_policy">
<name>uddi-org:v3_policy</name>
<description>UDDI Policy Description service specification
</description>
<overviewDoc>
<overviewURL useType="text">
http://uddi.org/pubs/uddi_v3.htm#policyDesc
</overviewURL>
</overviewDoc>
<categoryBag>
<keyedReference keyName="uddi-org:types:specification"
keyValue="specification" tModelKey="uddi:uddi.org:categorization:types" />
</categoryBag>
</tModel>
Here is how you would go about using it:
http://documentation.softwareag.com/webmethods/wmsuites/wmsuite8-2_sp2/CentraSite/8-2-SP2_CentraSite/dg-uddi/extensio.htm
It'd be up to you to register the policy under the service (for more
info see also http://uddi.org/pubs/uddi_v3.htm#_Toc85908203)
Is that what you are looking for? If so then the answer is yes jUDDI
supports it.
-Kurt
On 6/27/12 8:25 AM, tech evaluator wrote:
Thanks Kurt for the response.
Though I think the answer is 'No' I still want to get the confirmation
from you
Does JUDDI service registry support policies for Web Services? Can
these policies also be registered in jUddi and linked to services,
deploy time??
On Tue, Jun 26, 2012 at 7:54 PM, Kurt T Stam <[email protected]
<mailto:[email protected]>> wrote:
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.
