Geir, Use the Axis TCP Monitor and take a look at the SOAP request message that Scout/jUDDI is sending to the IBM registry. Would be a good idea to validate it against the UDDI v2 XML schema.
Steve -----Original Message----- From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] Sent: Monday, February 14, 2005 12:55 PM To: [email protected] Subject: jUDDI and IBM's test registry I was having problems when working on Apache Scout using IBM's test registry http://uddi.ibm.com/testregistry/inquiryapi https://uddi.ibm.com/testregistry/publishapi and all problems went away when talking to JUDDI's registry. This made me suspicious, of course. I just tried the SaveBusinessSample.java program with the same result. Using the properties file juddi.proxy.inquiryURL = http://uddi.ibm.com/testregistry/inquiryapi juddi.proxy.publishURL=https://uddi.ibm.com/testregistry/publishapi with my username and password, I got the same problem : AxisFault faultCode: Client faultSubcode: faultString: Client Error faultActor: faultNode: faultDetail: {urn:uddi-org:api_v2}dispositionReport:<result errno="10500"><errInfo errCode="E_fatalError">E_fatalError (10500) Serious technical error has occurred while processing the request. cvc-complex-type.4: Attribute 'businessKey' must appear on element 'businessEntity'.</errInfo></result> Has anyone experienced this? I'm going to go digging, but any hints or suggestions would help. geir -- Geir Magnusson Jr +1-203-665-6437 [EMAIL PROTECTED]
