[
https://issues.apache.org/jira/browse/JUDDI-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037420#comment-13037420
]
Kurt T Stam commented on JUDDI-481:
-----------------------------------
Hi Dc,
You got a authentication token for the user 'root' which means that you are
using the 'root' publisher. By default the key generator for the root publisher
defines a publishing domain of 'juddi.apache.org'. See:
http://svn.apache.org/repos/asf/juddi/tags/juddi-3.0.4/juddi-core/src/main/resources/juddi_install_data/root_tModelKeyGen.xml
This means that your keys need to be in that domain. i.e.:
businessKey="uddi:juddi.apache.org:mybusiness
If you choose to NOT specify a key it will create a key for you. However
supplying a key of value "" means an a string with zero value, and not omission.
So in my case
<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>
results in:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
<soap:Body>
<ns2:businessDetail xmlns:ns11="urn:uddi-org:policy_v3_instanceParms"
xmlns:ns10="urn:uddi-org:vs_v3" xmlns:ns9="urn:uddi-org:vscache_v3"
xmlns:ns8="urn:uddi-org:subr_v3" xmlns:ns7="urn:uddi-org:sub_v3"
xmlns:ns6="urn:uddi-org:custody_v3" xmlns:ns5="urn:uddi-org:repl_v3"
xmlns:ns4="urn:uddi-org:policy_v3"
xmlns:ns3="http://www.w3.org/2000/09/xmldsig#"; xmlns:ns2="urn:uddi-org:api_v3">
<ns2:businessEntity
businessKey="uddi:juddi.apache.org:b2186866-0e55-444a-8ff7-0d69f2cadae6">
<ns2:name>mybusiness</ns2:name>
</ns2:businessEntity>
</ns2:businessDetail>
</soap:Body>
</soap:Envelope>
Note that the businessKey ends up in the right domain.
You may want to read some more about keys:
http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-understandingkeypartitions-20061128.htm
Cheers,
--Kurt
> Bug? One of the last "2" businesses deleted, recreated the business and
> received juddi.rootPartition error!
> -----------------------------------------------------------------------------------------------------------
>
> Key: JUDDI-481
> URL: https://issues.apache.org/jira/browse/JUDDI-481
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
> Affects Versions: 3.0.4
> Environment: jUDDI version 3.0.4
> juddi.authenticate.Inquiry=false
> juddi.authenticator = org.apache.juddi.v3.auth.JUDDIAuthenticator
> Scout version 1.2.2
> JDK 1.6.0 u16
> Windows XP Pro 64-bit
> Reporter: Cli Dc
> Assignee: Kurt T Stam
> Priority: Critical
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I have explained this to Kurt Stam over e-mail. He encouraged to open a JIRA
> issue to look closely into this, and possibly resolve this bug! We need a
> resolution at a very high priority.
> The following behavior has been very (>95%) consistent.
> ===========
> Error Scenario:
> ===========
> jUDDI version 3.0.4
> juddi.authenticate.Inquiry=false
> juddi.authenticator = org.apache.juddi.v3.auth.JUDDIAuthenticator
> Scout version 1.2.2
> With the above settings, we start off by having "2" businesses in UDDI
> registry -- one is our own and second is jUDDI's default business "An Apache
> jUDDI Node".
> Then, we our delete own business in the UDDI registry. At this point, there
> is only *one* default business "An Apache jUDDI Node" in the j3_business_name
> table.
> Then, we go ahead and recreate (save) a new business with the name *same as*
> that of the business deleted earlier.
> At that point, the new business is *not* created. Instead we receive an
> error as below at that time:
> =================
> Error in Tomcat console:
> =================
> May 17, 2011 10:54:49 AM org.apache.cxf.phase.PhaseInterceptorChain
> doDefaultLogging
> INFO: Application
> {urn:uddi-org:v3_service}UDDI_Publish_Port#{urn:uddi-org:v3_service}save_business
> has thrown exception, unwinding now: org
> .apache.juddi.v3.error.FatalErrorException: An error occurred attempting to
> retrieve configuration information: juddi.rootPartition
> =================================
> How we temporarily overcome the above error:
> =================================
> We overcome, for now, the above error by doing this:
> 1. Shutdown jUDDI 3.0.4 instance.
> 2. Clean up database, delete database, delete user, recreate database,
> recreate user.
> 3. Start jUDDI 3.0.4 instance.
> 4. Immediately, shutdown jUDDI 3.0.4 instance.
> 5. Then, again (yeah, it's crazy), restart jUDDI 3.0.4 instance.
> At the end of step #5 above, we are able to recreate the business that we
> deleted with no errors.
> This is a painful procedure, and may need jUDDI team's immediate attention
> for a possible patch to jUDDI 3.0.4 app.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
