cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sarris Overbosch (JIRA)" <j...@apache.org>
Subject [jira] Created: (CXF-1903) Maven Codegen Plugin Fails For CXF WSDL
Date Fri, 07 Nov 2008 14:52:55 GMT
Maven Codegen Plugin Fails For CXF WSDL
---------------------------------------

                 Key: CXF-1903
                 URL: https://issues.apache.org/jira/browse/CXF-1903
             Project: CXF
          Issue Type: Bug
          Components: Configuration
    Affects Versions: 2.1.3, 2.1.2
         Environment: Windows XP, maven, eclipse
            Reporter: Sarris Overbosch
             Fix For: 2.1.4


I've set the wsdlRoot to c:/Repository and when you then issue the statement mvn -x cxf-codegen:wsdl2java,
this results in the following:

[DEBUG] Calling wsdl2java with args: [-verbose, -d, C:\projects\java\workspaces\iPrimaPortal\iPrimaClients\target\generated\src\main\java,
file:/c:/Repository/EMSPublishingServiceConcrete.wsdl]
Loading FrontEnd jaxws ...
Loading DataBinding jaxb ...
wsdl2java -verbose -d C:\projects\java\workspaces\iPrimaPortal\iPrimaClients\target\generated\src\main\java
file:/c:/Repository/EMSPublishingServiceConcrete.wsdl
wsdl2java - Apache CXF 2.1.3

[WARNING] Could not create marker file C:\projects\java\workspaces\iPrimaPortal\iPrimaClients\target\cxf-codegen-plugin-markers\.file:_c:_Repository_EMSPublishingServiceConcrete.wsdl.DONE
[DEBUG]
java.io.IOException: The parameter is incorrect
        at java.io.WinNTFileSystem.createFileExclusively(Native Method)
        at java.io.File.createNewFile(File.java:850)
        at org.apache.cxf.maven_plugin.WSDL2JavaMojo.processWsdl(WSDL2JavaMojo.java:355)
        at org.apache.cxf.maven_plugin.WSDL2JavaMojo.execute(WSDL2JavaMojo.java:249)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

IMO the : in C: should be replaced with something which is allowed by Windows

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message