"kukeltje" wrote : So you prefer 1, while I prefere 2. | i don't really have a preference about how the schema looks like. in both cases it is readable. more important is which techniques we'll be using to do the java-to-XML conversion and the SOAP framework we'll use for exposing our webservice. So you would start with JSR 109: Web Services for Java EE, Version 1.2 This relies on JAX-WS (next version of JAX-RPC) and JAXB 2.0. I don't know these technologies. But my concern is: how easy or hard will it be to create new commands and expose them through that web service ? I want to get a better understanding of the ins and outs going from development to deployment: * we need a J2EE 1.4 container * we have to put @WebService in the CommandService SLSB ? * we have to generate the JAXB bindings from the command beans themselves ? is it hard to customize ? do you think that will be needed often or will the default name mappings be sufficient ? * anything else we need to do ? You don't have to convince me yet... cause i just don't get it yet. One way to get more insights is if you just go ahead and implement the basic structure. So that we can have a look out how it works. Alex's opinion is always appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968052#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...