Actually, I would call that bug. Can you log an issue? It kind of gets worse. If you have a namespace of v1.1, it ALSO would just map to v1. Thus, two namespaces mapping to the same place. Not good.
That said, the RI does the same thing. I'm not seeing anything in the JAX- WS spec that would call for this though. I'll need to dig in some more tomorrow, but I definitely think I'd consider this a bug. Dan On Wed August 12 2009 2:58:29 pm Agustin Barto wrote: > I'm generating the server code for a WSDL which namespace ends with a > version number "http://foo.bar.com/service/v1.0";, and the generated > java package is com.bar.foo.service.v1. The service refers to types > defined on the namespace "http://foo.bar.com/service/v1.0/types"; and > the generated package for those is com.bar.foo.service.v1_0.types. > > Is this the expected behavior? Shouldn't the service package also end > with v1_0 ? > > Aside from explicitly supplying the package, is there a way to solve this? > > Agustin -- Daniel Kulp [email protected] http://www.dankulp.com/blog
