Griffith, We've professional applications hosted on our servers -- they use jUDDI v3.1.0. I agree with Tom's suggestion -- you move away from JAXR, switch to juddi-client. Things will pick up good pace after that.
Cli ________________________________ From: Tom Cunningham <[email protected]> To: [email protected] Cc: "George, Griffith" <[email protected]> Sent: Thursday, October 27, 2011 6:56 PM Subject: Re: Trouble connecting to a v3 registry What version of the JBoss SOA Platform are you using? It definitely looks like you have a v2/v3 mismatch going on here. You said that you're using JAXR to connect - I think you need a scout.properties file on your classpath with the following set : scout.proxy.uddiVersion=3.0 scout.proxy.uddiNamespace=urn:uddi-org:api_v3 My other suggestion would be to skip JAXR if you can and use the juddi-client. --Tom On 10/26/2011 03:47 PM, George, Griffith wrote: >Hi there. > >I’m an intern prototyping SOA, running a brand new install of JBoss SOA >Platform, which comes with jUDDIv3. My knowledge of web services and the >surrounding technologies is limited and self taught, so go easy on me ;). > >I have been trying to register a sample web service I wrote on the jUDDI >registry. I have tried many different methods of publication. > >Using the uddi browser, Eclipse WTP Web Services Explorer, and >programmatically using JAXR I receive the following error: > > >WARNING >[PhaseInterceptorChain]Interceptorfor{urn:uddi-org:v3_service}UDDI_Publish_Port > has thrown an exception,unwinding now >org.apache.cxf.interceptor. Fault:Messagepart >{urn:uddi-org:api_v2}get_authToken was notrecognized.(Doesit exist inservice >WSDL?) > > >Using JDeveloper 11g I receive the following status message when I try to >create a UDDI Registry Connection: > > >Testing connection with no proxy... >Contacting http://127.0.0.1:8080/juddiv3/services/inquiry >The inquiry endpoint could not be contacted. Test Failed. >Unmarshalling Error: unexpected element (uri:"urn:uddi-org:api_v2", >local:"name"). Expected elements are <{urn:uddi-org:api_v3}name>,<{urn:uddi-org:api_v3}authInfo>,<{urn:uddi-org:api_v3}discoveryURLs>,<{urn:uddi-org:api_v3}categoryBag>,<{urn:uddi-org:api_v3}findQualifiers>,<{urn:uddi-org:api_v3}find_relatedBusinesses>,<{urn:uddi-org:api_v3}tModelBag>,<{urn:uddi-org:api_v3}identifierBag> > > >Given that those errors point to a discrepancy between api_v2 and api_v3, I >downloaded jUDDIv2.0.1 in the tomcat bundle, ran that, and connected with no >problem. This leads me to believe that all of the methods I have tried so far >use the v2 API instead of v3, but I have no idea how to fix that. > >Do you have any idea how I could solve this problem using relatively simple >means? > >I appreciate your time. >Griffith George >Application Developer (FSWEP Student) | Développeur d'application (étudiant >PFETE) >Information Technology Division | Division de la technologie de l'information >Chief Information Officer Branch | Direction du dirigeant principal de >l'information >Treasury Board of Canada Secretariat | Secrétariat du Conseil du Trésor du >Canada >Ottawa, Canada >Government of Canada | Gouvernement du Canada >
