Details
Description
The below SOAP call (intercepted by TCPMon) correctly created a subscription, except that the brief flag is set to false.
Setting the flag to false on the client side is still false so it isn't being flipped.
I can't figure out where or why this is happening. It seems when a new subscription comes in jUDDI checks that the key does not already exist (updates if it does) and then persists the object. I will continue to look for a problem spot in this and update this issue if I find the error.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns2:save_subscription xmlns="urn:uddi-org:api_v3" xmlns:ns2="urn:uddi-org:sub_v3" xmlns:ns3="http://www.w3.org/2000/09/xmldsig#" xmlns:ns4="urn:uddi-org:subr_v3" xmlns:ns5="urn:uddi-org:policy_v3" xmlns:ns6="urn:uddi-org:custody_v3" xmlns:ns7="urn:uddi-org:vscache_v3" xmlns:ns8="urn:uddi-org:repl_v3" xmlns:ns9="urn:uddi-org:policy_v3_instanceParms" xmlns:ns10="urn:uddi-org:vs_v3"><authInfo>authtoken:539ad987-1785-4c3a-b32a-76638776b662</authInfo><ns2:subscription brief="true"><ns2:subscriptionFilter><find_service maxRows="10"><findQualifiers><findQualifier>caseSensitiveMatch</findQualifier></findQualifiers><name>AssetService</name></find_service></ns2:subscriptionFilter><bindingKey>uddi:juddi.apache.org:2fab0260-4f9a-48d9-b4ce-9cbe02d50d0e</bindingKey><ns2:notificationInterval>PT5M0.000S</ns2:notificationInterval></ns2:subscription></ns2:save_subscription></soap:Body></soap:Envelope>