From: Mark F. <mar...@ea...> - 2004-04-19 02:50:28
|
From: "Paul Kulchenko" <pau...@ya...> > Just create a hash with those parameters and set only ones you need: Hi Paul, I appreciate your prompt responses. It has helped me test UDDI v2 quickly. I've executed all the inquiry methods and processed every element and attribute. It works fine. The only issue is "lang" namespaced to "xml" (and, in v3, the element "Signiture" namespaced to "dsig"). And the v2 "find_businessExt" method which provides for unknown schemas in the result. There could be some crossover between this and the attributes and elements in the UDDI schema namespaced elsewhere. I've attached the script I used to test all the v2 inquiry services. If you would like to add it to the "samples" I would appreciate it. Something like this would have helped me get up to speed with UDDI::Lite. I think it will be useful to others. If you see any glaring mistakes, or alternative ways to do things, you're welcome to change the script. I'd like to update the POD for UDDI::Lite and make it easier to comprehend (from my "newbie" perspective). But, there's so many ways to invokeUDDI::Lite functions that I'm not sure I can improve on the POD. As a newbie, I wish it would have been simpler and more straightforward. From what I know, I think I could improve upon the POD. But, I'm worried about the things I don't know. :) Do you think it might be better to have a single syntax rather than so many alternatives? I'll test v3 in a month when I have a v3 server. I'd like to create a v3inquire script similiar to v2inquire. Thanks, Mark |