This is a limitation of the original JSR-181 specification that is implemented by jbossws 1.0.x. In jbossws 1.2.0JAX-WS support is provided which handles this use case by using JAXB for complex type binding. Therefore since 1.2.0 you can customize the namespace for any type you want using JAXB annotations.
You could find an example at
The problem is that I got problems with the JBossWS namespace mapping when using inherited/aggregated types, though. It works for "simple" complex types, but generates semantically incomplete wsdl when using real world classes with aggregation/inheriatnce from more >1 java packages.
In that case Webservice Client Generation from WSDL is complaining about the incorrect wsdl or even worse failing because of dis ambiguities (tried with .net 2.0; axis 1.4; Oracle)