Go ahead, Jesse. Wsdl2java tool will use different class to process customization(binding file), so we need to process the URI contains spaces before it invokes JAXWSDefinitionBuilder class.
Cheers Jim Ma On Wed, Mar 5, 2008 at 10:56 PM, Jesse McLaughlin <[EMAIL PROTECTED]> wrote: > > Cool. Thanks Ian. I changed my setup so as to avoid any spaces in the > full > project path, and everything started working as expected. So I take it > this > means there is a bug there... ie. you can't have spaces in your project > path > if you want to use a binding customization such as this (where as > normally, > leaving out the binding file, spaces pose no issue). > > Unless there are any objections, or unless a similar bug has already been > logged, I'll add this one into JIRA. > > Cheers, > Jesse. > > > > ianroberts wrote: > > > > Jesse McLaughlin wrote: > >> Hi Jim, > >> > >> No, there's no strange characters in the full path. There are spaces, > >> but > >> that's about as strange as it gets. > > > > You can't have spaces in a java.net.URI, they have to be escaped as %20. > > I'm not sure whose responsibility it is to do this though... > > > > Ian > > > > -- > > Ian Roberts | Department of Computer Science > > [EMAIL PROTECTED] | University of Sheffield, UK > > > > > > -- > View this message in context: > http://www.nabble.com/WSDL2Java-error-when-using-%3Cjaxb%3Aserializable-%3E-binding-customization-tp15786637p15852009.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
