On Friday 17 December 2010 1:15:46 pm Benson Margulies wrote: > So, I've got two services that share some classes, so I run the Maven > java2ws with createxsdimports, and I get a bunch of files with names > like: > > NameIndexService_schema3.xsd > > Has anyone got a procedure for arranging the name to be based on the > schema TNS so that shared things would end with wsdl's consuming the > same file? That would certainly be a good idea. :-)
As a note: the current behavior was specifically done to make CXF pass the JAX-WS TCK. The TCK uses the java2wsdl tool to generate some wsdls and then runs wsdl2java on those wsdls to generate new classes, but passes a binding.xml file to change the package and such. Since the schema name is put in the binding.xml, if we used different naming than the RI, we would have had to do major updates and surgery to get the TCK to build/pass. It was easier to just make what we generate match the RI. What I would support (which would be compatible) is to make it something like: -createxsdimports[=algorithm] where "algorithm" could be something like "simple" (current, default), "ns", or some class that implements someinterface that could do the mapping. -- Daniel Kulp [email protected] http://dankulp.com/blog
