I have not got any answer to this question in the users forum, so so I'll try here. With JBoss 4.0.4, the JBoss developers have passed on the responsibility of specifying the package to namespace mapping of java-wsdl to the user. As a result, people who are writing tools that takes in user-defined interfaces and use wstools to generate the wsdl need to figure out and supply the package name to namespace mapping in the java-wsdl config. This works fine as long as the SEI and its associated classes that it references are in the same package, but in an enterprise setup, this is a rarity - the SEI uses classes from various other packages. At the moment, JBoss expects that all pkg->namespace need to be supplied, which puts a heavy burden on the tool-writer in this case. Is this a first shot approach and the goal is to add the code to generate a default mapping if the user does not supply them (like what is done by all other vendors) at a later stage? Or is this a permanent design that will always expect the user to supply the mapping? If yes, then I am curious why you chose this approach where all the other vendors provide a default mapping and have the user-defined mapping as optional. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958235#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...