Rick, I don't know the answers....My initial thought was, let me code it up, make it as a sample, see how many folks are interested and then go on from there :) Also it would be a quick and dirty way to test some stuff. for example see invocations below that i tested with.
java samples.client.DynamicInvoker http://www.xmethods.net/sd/2001/TemperatureService.wsdl getTemp 02067 java samples.client.DynamicInvoker http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl getQuote IBM java samples.client.DynamicInvoker http://mssoapinterop.org/asmx/xsd/round4XSD.wsdl echoString "Hello World!!!" java samples.client.DynamicInvoker http://samples.gotdotnet.com/quickstart/aspplus/samples/services/MathService/VB/MathService.asmx?WSDL Add 3 4 Thanks, dims --- Rick Rineholt <[EMAIL PROTECTED]> wrote: > well... I think Axis itself only uses directly two externals to figure out > the input/output parms: the WSDL it self, and WSDL4J. So that should be > sufficient for it to be discovered again :-) Granted it may not be optimal > from a performance or code re use aspect. As for Axis providing this > information; Does Axis plan to externalize this as a service (i.e. API) ? > Is it something if I write code to will be supported and can be depend on > not changing? Or, should/will it be something internal to Axis? > > Rick Rineholt > "The truth is out there... All you need is a better search engine!" > > [EMAIL PROTECTED] > > > Please respond to [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > cc: > Subject: Re: Call Parameter details > > > > well...If you see samples\client\DynamicInvoker.java, you will see that > wsdl4j is not enough. I > needed patch and use our org.apache.axis.wsdl.gen.Parser. So the WSDL is > actually parsed twice :( > > Thanks, > dims > > --- Rick Rineholt <[EMAIL PROTECTED]> wrote: > > There is ... that's what WSDL4J is for. > > > > Rick Rineholt > > "The truth is out there... All you need is a better search engine!" > > > > [EMAIL PROTECTED] > > > > > > Please respond to [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > > cc: > > Subject: Call Parameter details > > > > > > > > Question: why isn't there a way to list the input/output parameters that > > have been configured on the org.apache.axis.client.Call object? > > > > Example, using the code below, I can initialize a call object from WSDL, > > but never see what parameters the initialization added to the Call. > > > > Service service = new Service("implementation.wsdl", serviceQN); > > Call op1 = (Call)service.createCall(portQN, "operation1"); > > // how do I get information about the expected parameters? (e.g. > > names, parameter mode, type) > > > > At the very least, we should have a method that returns an array of > > parameter names that we can feed into the getParameterTypeByName and > > getParameterTypeByQName methods, etc. Ideally, there should be a method > of > > inspecting the entire operation description. Am I missing something? > > > > - James Snell > > IBM Emerging Technologies > > [EMAIL PROTECTED] > > (559) 587-1233 (office) > > (700) 544-9035 (t/l) > > Programming Web Services With SOAP > > O'Reilly & Associates, ISBN 0596000952 > > > > Have I not commanded you? Be strong and courageous. > > Do not be terrified, do not be discouraged, for the Lord your > > God will be with you whereever you go. - Joshua 1:9 > > > > > > > ===== > Davanum Srinivas - http://xml.apache.org/~dims/ > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > > ===== Davanum Srinivas - http://xml.apache.org/~dims/ __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
