cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-1708) wsdl2java creates java.io.IOException: The parameter is incorrect
Date Tue, 28 Jul 2009 20:06:14 GMT

     [ https://issues.apache.org/jira/browse/CXF-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-1708.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.4


This is a duplicate of a resolved issue.

> wsdl2java creates java.io.IOException: The parameter is incorrect
> -----------------------------------------------------------------
>
>                 Key: CXF-1708
>                 URL: https://issues.apache.org/jira/browse/CXF-1708
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 2.1.1
>         Environment: Windows XP Service Pack 3 JDK 1.5.0_15 Maven 2.0.8
>            Reporter: Bill Leck
>             Fix For: 2.1.4
>
>
> Changed POM to use 2.1.1 from 2.1.  Executing mvn to generate-source using wsdl2java
plugin now generates the following exception:
> 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:345)
> 	at org.apache.cxf.maven_plugin.WSDL2JavaMojo.execute(WSDL2JavaMojo.java:223)
> 	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> 	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> 	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> 	at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> 	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)
> wsd2java works correctly in when switching back to 2.1.

-- 
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