All,
I've a question regarding architecture. I'm needing to develop a web service to
consume a rather large query into our system that's doesn't really give itself to
implentation via RPC style services because the number of parameters would be
ludicrous (unless they were composite member of an object). That said, it sounds as
though the messaging-style approach might work best for me where I can get at the
actual XML and turn it into a request that our core would understand.
Following is something analogous to the request I need to construct a query object off
of where child-one, child-two, etc. are essentially composite members of object
request, etc. Can someone recommend to me the best route to go here...do I need to
maybe expose my object as a whole over soap, etc. Not really ever seen how that's
done -- just know that it can be.
<request>
<child-one>
<parameter-one/>
<parameter-two/>
<parameter-three/>
<parameter-four/>
</child-one>
<child-two>
<parameter-one/>
<parameter-two/>
<parameter-three/>
<parameter-four/>
</child-two>
<child-three>
<parameter-one/>
<parameter-two/>
</child-three>
</request>
I've already constructed a message style service and the client posts the xml and I
pull the XML and all is well -- but I'd like to eliminate the unmarshaling of data
into my objects and have this accomplished in one fell swoop. Any input on the best
route to go here would be greatly appreciated (I DEMAND INPUT BY 5PM (just kidding, of
course)).
Thanks and more thanks,
Cory
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
