Well, it's not a bug in JAXB. I just checked the JAXB 2.2 spec and the behavior below for it is exactly as per spec. In Appendix D, it basically says only "/" and ":" are separators for tokens and the "." is only treated specially in the first token (basistech.com token). For the other tokens, it would just be mapped to _.
Thus, this looks like a bug in CXF. Dan On Sunday 25 July 2010 8:32:06 am Benson Margulies wrote: > This may be more JAXB than CXF, but here goes. > > Step 1: > > My SEI is annotated: > > @WebService(targetNamespace = "urn:basistech.com:rosette.analysis") > > My SEB is annotated: > > @WebService(endpointInterface = "com.basistech.ras.Extraction", > targetNamespace = "urn:basistech.com:rosette.analysis") > > And the package-info.java for com.basistech.ras contains: > > @javax.xml.bind.annotation.XmlSchema(namespace = > "urn:basistech.com:rosette.analysis" , > elementFormDefault = > javax.xml.bind.annotation.XmlNsForm.QUALIFIED) > package com.basistech.ras; > > Not too surprisingly, the wsdl and the schema within say: > > tns="urn:basistech.com:rosette.analysis" > > Next I run wsdl2java to set up a client. > > Well, the classes for the schema (the beans) wind up in: > > com.basistech.rosette_analysis > > while the classes for the service end up in: > > com.basistech.rosette > > So the 'analysis' end of things disappeared. Presumably changing the . > to a colon would cure this, but should I file a JIRA or a JAXB bz? -- Daniel Kulp [email protected] http://dankulp.com/blog
