Re: Bad namespace in WSDL when adding custom classes

2009-09-14 Thread Daniel Kulp
The easiest way is to add a package-info.java to the package the beans are in that has something like: @javax.xml.bind.annotation.XmlSchema(namespace = "http://domain.test.com/";) package com.test.domain; That should take care of it. If not, you'll need to add @XmlRootElement and @XmlType ann

Re: Bad namespace in WSDL when adding custom classes

2009-09-14 Thread zem_user
Any Suggestionsthis is driving me to my wits end? -- View this message in context: http://www.nabble.com/Bad-namespace-in-WSDL-when-adding-custom-classes-tp25410793p25439577.html Sent from the cxf-user mailing list archive at Nabble.com.

Bad namespace in WSDL when adding custom classes

2009-09-11 Thread zem_user
essage in context: http://www.nabble.com/Bad-namespace-in-WSDL-when-adding-custom-classes-tp25410793p25410793.html Sent from the cxf-user mailing list archive at Nabble.com.