Keep in mind that SOAP is service-oriented rather than object-oriented. Although plenty of people do it, you should not assume that a service exposes getter and setter methods on each of its attributes. The better way to design services is to expose higher order operations.
The JAX-RPC DII (the Call API) provides an API to dynamically invoke a service. You use WSDL4J to parse the WSDL and identify the supported operations and their message formats. Anne On 2/24/07, TriggerHappy <[EMAIL PROTECTED]> wrote:
Hi I'm trying to create a generic class which will invoke any service (provided it knows the service name and WSDL URL). Hypothetically speaking, if I had a 'Car' class with methods: - int getMaxSpeed() - String getModel(String saloonOrEstate) How would these map onto the Axis API? I ideally want a list of methods available, each with their respective input and output types. Is a mechanism to do this? Many thanks William -- View this message in context: http://www.nabble.com/Getting-method-input-output-types-tf3284218.html#a9135324 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
