You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@juddi.apache.org by Kurt T Stam <ku...@gmail.com> on 2011/05/23 19:08:29 UTC

Re: JIRA JUDDI-481

Maybe this demo will help you: 
http://apachejuddi.blogspot.com/2011/05/getting-started-with-uddi-v3.html
to create the requests.

--Kurt


On 5/23/11 10:07 AM, Computer Learning Inst wrote:
> Sure Kurt, will send.  Will do whatever it takes to help you (in turn, 
> just helping myself :) ) debug this.
>
> Currently, I have used get_authtoken and save_business methods in 
> soapUI.  If you have any sample of requests (formats you are looking 
> for), please send them over!  Thanks.
>
>
> --- On *Mon, 5/23/11, Kurt T Stam /<ku...@gmail.com>/* wrote:
>
>
>     From: Kurt T Stam <ku...@gmail.com>
>     Subject: Re: JIRA JUDDI-481
>     To: "Computer Learning Inst" <cl...@yahoo.com>
>     Cc: tcunning@redhat.com
>     Date: Monday, May 23, 2011, 9:47 AM
>
>     No problem, remember we need the exact request. 'save_business' is
>     not enough. We need ALL your requests in soap form.
>
>     On 5/23/11 9:42 AM, Computer Learning Inst wrote:
>>     Yes, Kurt.  I was thinking of a "fresh" jUDDI bundle as well.
>>
>>     Thank you for your reply.
>>
>>
>>     --- On *Mon, 5/23/11, Kurt T Stam /<ku...@gmail.com>
>>     </m...@gmail.com>/* wrote:
>>
>>
>>         From: Kurt T Stam <ku...@gmail.com>
>>         </m...@gmail.com>
>>         Subject: Re: JIRA JUDDI-481
>>         To: "Computer Learning Inst" <cl...@yahoo.com>
>>         </m...@yahoo.com>
>>         Cc: tcunning@redhat.com </m...@redhat.com>
>>         Date: Monday, May 23, 2011, 9:39 AM
>>
>>         This is what you have to do:
>>
>>         1. Download a fresh juddi-tomcat bundle.
>>
>>         2. Send in and log your exact requests and add those to the
>>         jira, so that we can reproduce the issue.
>>
>>         --Kurt
>>
>>
>>         On 5/23/11 9:31 AM, Computer Learning Inst wrote:
>>>         Kurt,
>>>
>>>         Thanks for your reply.  However, it is almost the same soap
>>>         request for "save_business" -- only the name of the business
>>>         will change.
>>>
>>>         For example:
>>>         <soapenv:Envelope
>>>         xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>>>         xmlns:urn="urn:uddi-org:api_v3"
>>>         xmlns:xd="http://www.w3.org/2000/09/xmldsig#">
>>>         <soapenv:Header/>
>>>         <soapenv:Body>
>>>         <urn:save_business>
>>>         <!--Optional:-->
>>>         <urn:authInfo>authtoken:ea06abde-da87-4b58-9b8f-731366793d5a</urn:authInfo>
>>>
>>>         <!--1 or more repetitions:-->
>>>         <urn:businessEntity >
>>>         <urn:name>mybusiness</urn:name>
>>>         </urn:businessEntity>
>>>         </urn:save_business>
>>>         </soapenv:Body>
>>>         </soapenv:Envelope>
>>>
>>>
>>>
>>>
>>>         --- On *Mon, 5/23/11, Kurt T Stam /<ku...@gmail.com>/*
>>>         wrote:
>>>
>>>
>>>             From: Kurt T Stam <ku...@gmail.com>
>>>             Subject: Re: JIRA JUDDI-481
>>>             To: "Computer Learning Inst" <cl...@yahoo.com>
>>>             Date: Monday, May 23, 2011, 9:23 AM
>>>
>>>             Hi Dc,
>>>
>>>             Your issue is *data* related. So unless you specify all
>>>             the (soap) requests, it is impossible for us the
>>>             reproduce the issue and to help you.
>>>
>>>             Thx,
>>>
>>>             --Kurt
>>>
>>>
>>>             On 5/23/11 8:56 AM, Computer Learning Inst wrote:
>>>>             Hi Kurt,
>>>>
>>>>             Hope your weekend was good.  Over the weekend, I found
>>>>             out that a restart of jUDDI v3.0.4 instance seems to
>>>>             give rise to jUDDI:rootPartition error with
>>>>             "save_business".
>>>>
>>>>             I have included my comments on the issue.  Please take
>>>>             a look (when you've a chance), and please suggest
>>>>             (whether we're doing anything wrongly or jUDDI needs a
>>>>             correction).
>>>>
>>>>             The behavior of jUDDI is 100% consistent about this
>>>>             error.  Thanks.
>>>>
>>>
>>
>