why do you mention the xsd. if i look at your examples (which is very similar to what i want), i see a very limited schema that is fixed for all commands: <command name="[xsd:string]" [other attibutes optional]> | [any mixed content] | </command> | then at the server side, we would need a mapping command names and ParsableCommand classes. do you think it would be suitable if we would use DOM for this parsing/generation of XML ? then a ParsableCommand parser interface could look like this: public interface ParsableCommand { | Element execute(Element element); | } then we need to write the infrastructure for 1 document style webservice with one method that unwraps these command from the SOAP envelopes, extract the command DOM element, lookup/instantiate the appropriate parsable command and invoke the execute method. is that close to what you had in mind too ? but i don't know yet which java WS technology we can use to implement this kind of infrastructure. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968018#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...