Most likely, with method sigs like that, you want to flip to "Bare" mode. The default is to take the return object and wrap it in a schema wrapper. That is what is happening here. It's trying to create a wrapper named "createUserResponse", but you already have one named that. Add an annotation like:
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
to the operation or to the SEI if all operations should be bare.

Dan



On Jul 3, 2008, at 7:55 AM, John-M Baker wrote:

Hello,

I have a method:

public CreateUserResponse blah() {

}

where CreateUserResponse extends an object called GenericResponse (as do
many other objects).  When I start CXF, the following exception is
generated:

Two classes have the same XML type name
"{http://admin.services.websso.db.com/}createUserResponse";. Use
@XmlType.name and @XmlType.namespace to assign different names to them.
       this problem is related to the following location:
               at
com.db.websso.legacy.businessobject.admin.CreateUserResponse
               at private
com.db.websso.legacy.businessobject.admin.CreateUserResponse
com.db.websso.services.admin.jaxws_asm.CreateUserResponse._return
               at
com.db.websso.services.admin.jaxws_asm.CreateUserResponse
       this problem is related to the following location:
               at
com.db.websso.services.admin.jaxws_asm.CreateUserResponse

And there is one for every extension of GenericResponse.

Does CXF not support inheritence of return types?


John Baker
--
Web SSO
IT Infrastructure
Deutsche Bank London

URL:  http://websso.cto.gt.intranet.db.com


---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e- mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog




Reply via email to