I might actually do something alike. My ws receives a SOAP-request, containing a query (mapped later on an EIS-call). I use Castor generated code to map xml->java-objects. Messy, I had to code a java->java mapper,for filling already used java-objects. Started the thing on jwsdp, will port it on Axis, if jaxm is fully supported, sorry. I'm not sure, if Axis (actually) is able to do the mapping for me/you at runtime. Castor's mapping may be fine-tuned (reading a xml->to java-field in a mapping.xml) during runtime. May be there is something on http://www.castor.org (xml) you might want to use. HTH markus
>>> [EMAIL PROTECTED] 17.01.2003 19.07 Uhr >>> I'm in a situation where I'm needing to essentially create an object of type y from a pre-defined message (rather verbose xml message representing a query) that isn't a direct representation of object y, in other words -- though a document style service looks great, ie, it recieves message x and creates object type x, i'd still have to write code to port object type x --> object type y. Additionally, there could be situations in which I may receive two distinct message types that both need to assume the final form of object type y. It seems to me that I may want to implement a Message style service to handle this and actually parse the XML into a given object type -- was just hoping someone had some insight on how to avoid this step. Additionally -- any good documentation on document style implementation? Thanks for any input, Cory Wilkerson
