You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Adam Pryce (JIRA)" <ju...@ws.apache.org> on 2010/03/05 22:11:27 UTC
[jira] Created: (JUDDI-373) Brief flag is not read properly by
save_subscription
Brief flag is not read properly by save_subscription
----------------------------------------------------
Key: JUDDI-373
URL: https://issues.apache.org/jira/browse/JUDDI-373
Project: jUDDI
Issue Type: Bug
Components: core
Affects Versions: 3.0.1
Environment: Using SOAP generated by juddi client to create asynchronous subscription.
Reporter: Adam Pryce
Assignee: Kurt T Stam
The below SOAP call (intercepted by TCPMon) correctly created a subscription correctly, 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JUDDI-373) Brief flag is not read properly by
save_subscription
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam updated JUDDI-373:
------------------------------
Fix Version/s: 3.0.2
> Brief flag is not read properly by save_subscription
> ----------------------------------------------------
>
> Key: JUDDI-373
> URL: https://issues.apache.org/jira/browse/JUDDI-373
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.1
> Environment: Using SOAP generated by juddi client to create asynchronous subscription.
> Reporter: Adam Pryce
> Assignee: Kurt T Stam
> Fix For: 3.0.2
>
>
> 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JUDDI-373) Brief flag is not read properly by
save_subscription
Posted by "Adam Pryce (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843294#action_12843294 ]
Adam Pryce commented on JUDDI-373:
----------------------------------
Note that my main method of confirming the flag is incorrectly set to false is to look in the db (postgres).
> Brief flag is not read properly by save_subscription
> ----------------------------------------------------
>
> Key: JUDDI-373
> URL: https://issues.apache.org/jira/browse/JUDDI-373
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.1
> Environment: Using SOAP generated by juddi client to create asynchronous subscription.
> Reporter: Adam Pryce
> Assignee: Kurt T Stam
> Fix For: 3.0.2
>
>
> 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (JUDDI-373) Brief flag is not read properly by
save_subscription
Posted by "Tom Cunningham (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Cunningham closed JUDDI-373.
--------------------------------
> Brief flag is not read properly by save_subscription
> ----------------------------------------------------
>
> Key: JUDDI-373
> URL: https://issues.apache.org/jira/browse/JUDDI-373
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.1
> Environment: Using SOAP generated by juddi client to create asynchronous subscription.
> Reporter: Adam Pryce
> Assignee: Tom Cunningham
> Fix For: 3.0.2
>
>
> 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JUDDI-373) Brief flag is not read properly by
save_subscription
Posted by "Tom Cunningham (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Cunningham resolved JUDDI-373.
----------------------------------
Resolution: Fixed
Fix the mapping of the brief flag in MappingAPIToModel.
> Brief flag is not read properly by save_subscription
> ----------------------------------------------------
>
> Key: JUDDI-373
> URL: https://issues.apache.org/jira/browse/JUDDI-373
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.1
> Environment: Using SOAP generated by juddi client to create asynchronous subscription.
> Reporter: Adam Pryce
> Assignee: Tom Cunningham
> Fix For: 3.0.2
>
>
> 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JUDDI-373) Brief flag is not read properly by
save_subscription
Posted by "Adam Pryce (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Pryce updated JUDDI-373:
-----------------------------
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>
was:
The below SOAP call (intercepted by TCPMon) correctly created a subscription correctly, 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>
> Brief flag is not read properly by save_subscription
> ----------------------------------------------------
>
> Key: JUDDI-373
> URL: https://issues.apache.org/jira/browse/JUDDI-373
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.1
> Environment: Using SOAP generated by juddi client to create asynchronous subscription.
> Reporter: Adam Pryce
> Assignee: Kurt T Stam
>
> 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (JUDDI-373) Brief flag is not read
properly by save_subscription
Posted by "Adam Pryce (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843294#action_12843294 ]
Adam Pryce edited comment on JUDDI-373 at 3/9/10 9:18 PM:
----------------------------------------------------------
Note that my main method of confirming the flag is incorrectly set to false is to look in the db (postgres). Also, if I manually switch the brief flag the subscription no longer updates on new entities.
was (Author: atp):
Note that my main method of confirming the flag is incorrectly set to false is to look in the db (postgres).
> Brief flag is not read properly by save_subscription
> ----------------------------------------------------
>
> Key: JUDDI-373
> URL: https://issues.apache.org/jira/browse/JUDDI-373
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.1
> Environment: Using SOAP generated by juddi client to create asynchronous subscription.
> Reporter: Adam Pryce
> Assignee: Kurt T Stam
> Fix For: 3.0.2
>
>
> 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (JUDDI-373) Brief flag is not read properly by
save_subscription
Posted by "Tom Cunningham (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Cunningham reassigned JUDDI-373:
------------------------------------
Assignee: Tom Cunningham (was: Kurt T Stam)
> Brief flag is not read properly by save_subscription
> ----------------------------------------------------
>
> Key: JUDDI-373
> URL: https://issues.apache.org/jira/browse/JUDDI-373
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.1
> Environment: Using SOAP generated by juddi client to create asynchronous subscription.
> Reporter: Adam Pryce
> Assignee: Tom Cunningham
> Fix For: 3.0.2
>
>
> 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.