> Glanville, Jay wrote: > > Hello all. > > > > I'm trying to incorporate a web service (axis's > implementation of SOAP) > > into an existing web application. The web application is relatively > > well architected using MVC, so an API of functionality, plus a data > > structure of beans already exists. > > > > My question is a confirmation: is this all I need to do in order to > > integrate axis into my web application? > > 1.) add all the necessary axis jars to the WEB-INF/lib directory > > 2.) add the necessary servlet mapping to map HTTP requests > to axis to my > > web.xml > > 3.) create a server-config.wsdd file containing a <service> entry > > defining my service classes and bean mappings > > > > Is this all that's necessary? > > Up to a point. Just remember that you're not dealing with objects any > more. If you're model classes rely on inter object relationships > significantly (which is a perfectly valid approach) you'll be > bitten by > the object / message difference. If you understand this then > great, but > I've seen quite a few people attempt to use Axis and friends as if it > were an object based system such as RMI and get burned as a result.
Hello Tom. Can you please elaborate on the "inter object relationships" leading to bites from the "object / message difference". The set of java beans that represent my data structure that I'm wanting to publicize does have a lot of inter object relationships. I.e.: class User has two instances of Address (home & work), etc. All of these classes I'll be including in my server-config.wsdd through <beanMapping> entries in my <service>. So, I think this might fit your definition of inter-object relationships. But, how does the object / message difference hurt (bite) me? Thanks for your reply Tom. JDG -- Jay Glanville
