I have looked at SoapUI, including the tutorial on the blog. (In fact I've read a lot of the pertinent posts on your blog.)
We are prototyping, and so my primary goal is to prove that there is tooling available to publish and dynamically find web services. I agree that SoapUI is a good place to start. I suppose I will have to dig deeper into juddi-client and see if I can get that working. Also, Tom mentioned that I need a scout.properties file on the classpath if I'm going to use scout/JAXR, so I will give that another shot. Thanks for all of your help guys. I'll be back if I have more concrete problems that I can't figure out. :) 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 ________________________________ From: Kurt T Stam [mailto:[email protected]] Sent: October 27, 2011 11:27 AM To: George, Griffith Cc: [email protected] Subject: Re: Trouble connecting to a v3 registry BTW The easiest way to get going it probably to start with a tool like SoapUI. --K On 10/27/11 11:12 AM, George, Griffith wrote: Kurt, 1. Thanks, I am now subscribed. 3. I set the endpoint to be http://127.0.0.1:8080/juddiv3/services/inquiry. Is that correct? 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 ________________________________ From: Kurt T Stam [mailto:[email protected]] Sent: October 27, 2011 9:25 AM To: [email protected]<mailto:[email protected]>; George, Griffith Subject: Re: Trouble connecting to a v3 registry Hi George, 1. If you want to receive future responses please register with the user mailing list. 2. Yes you will need a v3 client to connect to a v3 UDDI server. You can use the juddiv3-client code to do so, and with that and scout-1.2.3 you can also use JAXR. 3. I don;t know about JDeveloper 11g, but it maybe that you did not set the end points correctly. I hope this helps! Cheers, --Kurt On 10/26/11 3: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] Interceptor for {urn:uddi-org:v3_service< font face="Courier New">}UDDI_Publish_Port has thrown an exception, unwinding now org.apache.cxf.interceptor.Fault: Message part {urn:uddi-org:api_v2}get_authToken was not recognized. (Does it exist in service WSDL?) < /o:p> 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
