WSDL is fine if you're in a Web Services world and even then up to a point. It isn't a generic contract definition language. A combination of WSDL and WS-Policy gets you a little closer to things, but even then you can't define meta-data easily, such as SLAs. WSDL tools are also pretty poor for working at the SOA level: most take the approach of distributed objects, which isn't what SOA is about. Finally, WSDL isn't simple! WSDL 2.0 adds more complexity. We should add nothing to the ESB that acts as a barrier to adoption and ease of use. People who are using JBossESB for Web Services may well expect to see some aspect of the contract definition appear in XML and WSDL. People who are using JBossESB for REST, JMS, or anything other than Web Services, may not expect to see WSDL anywhere. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969248#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...