juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Closed: (JUDDI-435) Service moves do not appear to be supported
Date Wed, 15 Dec 2010 21:52:02 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kurt T Stam closed JUDDI-435.
-----------------------------

    Resolution: Fixed

We now allow moving services if both businesses are owned by the same publisher, as per the
referenced spec.

> Service moves do not appear to be supported
> -------------------------------------------
>
>                 Key: JUDDI-435
>                 URL: https://issues.apache.org/jira/browse/JUDDI-435
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.3
>         Environment: Apache Tomcat 6.0.24, PostgreSQL 8.4
>            Reporter: Jason Brown
>            Assignee: Kurt T Stam
>             Fix For: 3.0.5
>
>
> Currently, it appears that jUDDI does not support Service moves. When a move is attempted,
we receive an E_invalidkey SOAP fault.
> Setup:
> <?xml version="1.0" encoding="UTF-8"?>
> <save_business xmlns="urn:uddi-org:api_v3">
> 	<!-- saves a business that tries to move a service from an existing business -->
> 	<businessEntity businessKey="uddi:be2">
> 		<name>be2</name>
> 		<businessServices>
> 			<!-- Move the service uddi:be0:bs0 to be2-->
> 			<businessService serviceKey="uddi:be0:bs0" businessKey="uddi:be2">
> 				<name>be2:bs0</name>
> 			</businessService>
> 		</businessServices>
> 	</businessEntity>
> </save_business>
> Attempt to perform the move with the following:
> <?xml version="1.0" encoding="UTF-8"?>
> <save_business xmlns="urn:uddi-org:api_v3">
> 	<!-- saves a business that tries to move a service from an existing business -->
> 	<businessEntity businessKey="uddi:be2">
> 		<name>be2</name>
> 		<businessServices>
> 			<!-- Move the service uddi:be0:bs0 to be2-->
> 			<businessService serviceKey="uddi:be0:bs0" businessKey="uddi:be2">
> 				<name>be2:bs0</name>
> 			</businessService>
> 		</businessServices>
> 	</businessEntity>
> </save_business>
> What we receive from the registry is the following SOAP Fault:
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
>   <soap:Body>
>     <soap:Fault>
>       <faultcode>soap:Server</faultcode>
>       <faultstring>The service being saved has a different parent business key
then the one provided:  uddi:be2, uddi:be0</faultstring>
>       <detail>
>         <dispositionReport xmlns="urn:uddi-org:api_v3" xmlns:ns10="urn:uddi-org:vs_v3"
xmlns:ns2="http://www.w3.org/2000/09/xmldsig#" xmlns:ns3="urn:uddi-org:sub_v3" xmlns:ns4="urn:uddi-org:repl_v3"
xmlns:ns5="urn:uddi-org:custody_v3" xmlns:ns6="urn:uddi-org:vscache_v3" xmlns:ns7="urn:uddi-org:subr_v3"
xmlns:ns8="urn:uddi-org:policy_v3" xmlns:ns9="urn:uddi-org:policy_v3_instanceParms">
>           <result errno="10210">
>             <errInfo errCode="E_invalidKeyPassed">An invalid key has been passed</errInfo>
>           </result>
>         </dispositionReport>
>       </detail>
>     </soap:Fault>
>   </soap:Body>
> </soap:Envelope>
> Is there any plan to support moves as referenced in section 5.2.16.3, Behavior, paragraph
4, of the UDDI Version 3.0.2 Specification ? If not, would a more appropriate error code be
E_unsupported, as it is a feature that is not supported ?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message