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
