It turned out to be issue with configuration - bindings were
configured via extraargs (one with -b switch, followed by other
extraarg with value file:${basedir}/pathtowsdl). Since I'm working on
Windows those path separators in basedir are "\" and with spaces in
between it would cause generation to fail. I've change configuration
to use bindingFiles/bindingFile configuration parameter instead and it
works. Maybe extraargs approach would work if configured with addition
of quotes.I'm trying now to implement m2e connector for cxf-codegen-plugin so that it can be used at least to generate java from wsdl. There is a support ticket for this at https://bugs.eclipse.org/bugs/show_bug.cgi?id=350081 I'm using https://github.com/bitstrings/m2e-jaxb2-connector as starting point, hoping it won't be much different for cxf. Did any of cxf developers already do anything on that issue? I've seen there's some work done at https://github.com/mtpettyp/m2eclipse-extras/tree/master/org.sonatype.m2e.cxf Regards, Stevo. On Tue, Aug 23, 2011 at 9:08 PM, Daniel Kulp <dk...@apache.org> wrote: > > > Can you produce a full maven base testcase using a hello-world wsdl or similar > and file a JIRA? > > Our Windows nightly at: > https://builds.apache.org/view/A-F/view/CXF/job/CXF-trunk-windows/ > > is specifically setup to run in a directory with a space as well as to have a > maven-repo in a directory with a space. We pretty much did that to test some > of the handling of the various pieces when there are spaces there. Thus, I'm > slightly surprised by this. > > Dan > > > On Monday, August 22, 2011 12:36:28 PM Stevo Slavić wrote: >> Hello cxf users, >> >> cxf-codegen-plugin v 2.1.x (tried 2.1.3 & 2.1.10), 2.2.12 and 2.3.6 >> have issue with spaces in wsdl path when generating Java classes >> (tried with 2.4.2 too but dependencies of plugin and project are not >> compatible). >> >> In use case where issue is reproduced there are two child modules W >> (for wsdl) and J (for java) of parent module P, W has WSDL files, J >> has wsdl2java configured. J declares property wsdl.project.location >> equal to ../W, while wsdlOption/wsdl references this property. When P >> is built on a path with spaces build fails, otherwise it's successful. >> >> It seems wsdl2java wrongly interprets full path with spaces as >> relative path and then decides to append current directory prefix >> twice. >> >> Can anyone reproduce this? >> >> Regards, >> Stevo. > -- > Daniel Kulp > dk...@apache.org > http://dankulp.com/blog > Talend - http://www.talend.com >
