Hi, thanks for the advice. I must be honest though, I don't really understand whats happening in the example. I can't find any real documentation either. Perhaps you can point me in the right direction.
Do I need to change my WSDL to use it? or just the WSDD file? I can't change the WSDL as it is given to me from an external source, and is being used by others besides myself. What about the stubs etc generated by axis? Do I update those. In the example there are no stubs at all, so I'm a bit confused. I currently use a test client which creates a stub and calls methods on it. Must the stub be changed to accept and return Element[]? Sorry, but I am new to this, and confused. Thanks Joel On Mon, 2004-07-12 at 15:58, Davanum Srinivas wrote: > Did you try the message service example on the server-side? > (samples\message) You can use that with a custom WSDL. (This will get > around the Handler Hack and easier to support/implement) > > -- dims > > On 12 Jul 2004 15:52:04 +0200, Joel Carklin <[EMAIL PROTECTED]> wrote: > > Hi, wonder if anyone can recommend or advise on a strategy for dealing > > with the following scenario. I already have a system in place which > > accepts xml, uses dom to extract info from it, does business logic, > > creates an xml response and returns it. The xml schema is specific to > > this system. The system does not use soap and is not a web service. > > > > Now, however, we have a requirement, that, in addition to what it > > already does, this system needs to become a web service, and needs to > > process both 'native xml' and soap messages. > > > > The strategy I tried (which isn't working) is as follows: > > - I set up tomcat with axis to handle the rpc calls coming from the > > client. > > - Instead of filling business logic code into the stub's Implementation > > class, as is usual, I created a custom handler which routs the soap xml > > to the existing system. > > - Within the existing system I created another axis server to receive > > the soap message to invoke the appropriate methods for business logic, > > then to return a response soap message to tomcat, which then sends the > > response back to the client. > > > > -now, this almost works. Some requests are dealt with successfully in > > this way, but others throw an error when the invoke method on the axis > > engine within the existing system is called (as opposed to axis on > > tomcat) and the errors are giving me a lot of grief, cause I don't > > really understand them, or how to fix them without delving into axis > > source. The axis on tomcat part works perfectly. > > > > -so now I thought maybe I'll take Axis out of the existing system, but > > then I need another way to process the soap messages, to extract info > > from the request and generate a proper soap response. > > > > Any ideas > > Thanks > > Joel > > > > > > > -- > Davanum Srinivas - http://webservices.apache.org/~dims/
