Hi Mike, I think you are right that you *can* store WSDL in doing something like described here: http://books.google.com/books?id=M1rADzqjo2cC&pg=PA181&lpg=PA181&dq=store+wsdl+uddi&source=bl&ots=ugX2QfSARV&sig=izsCwFSVtzVdzyvRJCbs-rNFFAc&hl=en&ei=2E_9TOu2LcP78AaTm9j0Cg&sa=X&oi=book_result&ct=result&resnum=2&ved=0CCEQ6AEwATgK#v=onepage&q=store%20wsdl%20uddi&f=false
However it is more common to just store a reference to the wsdl. So simply host them along with your exisiting services, and add the reference to jUDDI. We are in the process of adding a more substantial client GUI to jUDDI, but right there is no place to add it using that yet (want to help out :)? I would use soapUI if I where you.. Or you can use our unittest code in the juddi-core-(openjpa) package which uses the juddi-client. Hope this helps. --Kurt On Mon, Dec 6, 2010 at 3:20 PM, Mike Smith <[email protected]> wrote: > Hi Kurt, > > I would like to utilize jUDDI v3 to store XSDs and WSDLs that have > been previously created. I believe that I can do this in v2, but for > the life of me I cannot figure how to do in v3 without rebuilding > code, which for many reasons is not an option. > > Going forward, I will build and store service info directly to jUDDI, > so that is not an issue. For my current issue, I think the easiest > thing would be to have some sort of GUI that would allow me to put > previously existing information in. > > Do you have a suggestion or a tool that I could use for this? Or a > suggestion to do this using simple service calls - I'm thinking of > doing a qd PHP page to get this done, but again I am losing how I > would publish the service artifacts. > > Any assistance you could provide would be greatly appreciated. > > Thanks, > > Mike >
