@Art - I am running Eclipse with jdk 1.8. I tried to add the jaxws-tools
2.1.7 dependency to the plugin to require the 2.1.7, but it made no
difference.
@Anton - I must be doing something wrong. I tried from the command line to
launch eclipse -consoleLog but saw nothing in my console view. I tried
eclipsec.exe -consoleLog and saw nothign in the stdout window. I even
tried adding -consoleLog in my eclipse.ini file (right before my -vm
argument) and still have nothing additional in my console window.
Am I missing something obvious?
Thanks,
Eric
On Thu, May 19, 2016 at 2:06 PM, Anton Tanasenko <atg.sleepl...@gmail.com>
wrote:
> Try running eclipse with -consoleLog. Jaxws dumps output to System.out,
> which during the mojo execution in eclipse should be plain System.out of
> eclipse itself.
>
> 2016-05-19 21:01 GMT+03:00 Eric B <ebenza...@gmail.com>:
>
>> Great idea. I did. It worked flawlessly - as expected:
>>
>> $ wsimport -d /tmp/ws/bin -p jaxws.server -s /tmp/adams/ws/src -target
>> 2.1 src/main/webapp/META-INF/ProfileWebService.wsdl
>>
>> $ wsimport -version
>> JAX-WS RI 2.1.6 in JDK 6
>>
>>
>> Can it be some version conflicts from the JAX-WS RI that I'm using
>> command line vs something being triggered via m2e?
>>
>> Thanks,
>>
>> Eric
>>
>>
>> On Thu, May 19, 2016 at 1:44 PM, Art Kaufmann <art.kaufm...@frequentz.com
>> > wrote:
>>
>>> Try running wsimport from the command line, rather than letting the
>>> plug-in do the job. That said, wsimport and related tools are sometimes
>>> very, very bad at reporting actual errors. I've spent many hours debugging
>>> this kind of issue. Look first to the changes that you've made to your WSDL
>>> and make sure that they are consistent with the standards.
>>>
>>> Art Kaufmann
>>> Chief Architect, IRIS (Traceability Server)
>>> "The life so short, the craft so long to learn"
>>> "By hammer and hand do all things stand"
>>>
>>> 3960 Fabian Way
>>> Palo Alto, CA 94303
>>> art.kaufm...@frequentz.com
>>> www.frequentz.com
>>> O: (650)397-2553
>>> M: (310)418-8410
>>> *This E-mail and its attachments may contain proprietary and/or
>>> confidential information belonging to Frequentz, LLC. Dissemination and
>>> copying of this E-mail is strictly prohibited. This E-mail is intended
>>> solely for the use of the individual and entity to which it is addressed.
>>> If you have received this E-mail in error, please notify the sender
>>> immediately and delete the original and any copies.*
>>>
>>> On Thu, May 19, 2016 at 10:24 AM, Eric B <ebenza...@gmail.com> wrote:
>>>
>>>> I don't know if this specifically an m2e problem, but it is definitely
>>>> something with a maven plugin within Eclipse. I'm using Eclipse Mars with
>>>> m2e 1.6.2.
>>>>
>>>> I'm trying to generate .java files from an existing WSDL file and am
>>>> using the org.codehaus.mojo:jaxws-maven-plugin:2.4.1 plugin.
>>>>
>>>> If I try running maven on the command line, everything works fine
>>>> (maven 3.2.5 with JDK 1.6). However, if I try to build the project in
>>>> Eclipse, I get the following error message:
>>>>
>>>> Invocation of com.sun.tools.ws.wscompile.WsimportTool failed - check
>>>> output
>>>> (org.codehaus.mojo:jaxws-maven-plugin:2.4.1:wsimport:default:generate-sources)
>>>>
>>>> org.apache.maven.plugin.MojoExecutionException: Invocation of
>>>> com.sun.tools.ws.wscompile.WsimportTool failed - check output
>>>> at
>>>> org.codehaus.mojo.jaxws.AbstractJaxwsMojo.exec(AbstractJaxwsMojo.java:488)
>>>> at
>>>> org.codehaus.mojo.jaxws.WsImportMojo.processLocalWsdlFiles(WsImportMojo.java:340)
>>>> at
>>>> org.codehaus.mojo.jaxws.WsImportMojo.executeJaxws(WsImportMojo.java:289)
>>>> at
>>>> org.codehaus.mojo.jaxws.MainWsImportMojo.executeJaxws(MainWsImportMojo.java:51)
>>>> at
>>>> org.codehaus.mojo.jaxws.AbstractJaxwsMojo.execute(AbstractJaxwsMojo.java:389)
>>>> at
>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
>>>> at
>>>> org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
>>>> at
>>>> org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
>>>> at
>>>> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
>>>> at
>>>> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
>>>> at
>>>> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
>>>> at
>>>> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
>>>> at
>>>> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
>>>> at
>>>> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
>>>> at
>>>> org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
>>>> at
>>>> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
>>>> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>>>> at
>>>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
>>>> at
>>>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
>>>> at
>>>> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
>>>> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>>>> at
>>>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
>>>> at
>>>> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
>>>> at
>>>> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
>>>> at
>>>> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
>>>> at
>>>> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>> pom.xml /adams_ws line 41 Maven Build Problem
>>>>
>>>>
>>>> My pom file is:
>>>>
>>>> <build>
>>>> <plugins>
>>>> <plugin>
>>>> <groupId>org.codehaus.mojo</groupId>
>>>> <artifactId>jaxws-maven-plugin</artifactId>
>>>> <version>2.4.1</version>
>>>> <executions>
>>>> <execution>
>>>> <goals>
>>>> <goal>wsimport</goal>
>>>> </goals>
>>>> </execution>
>>>> </executions>
>>>> <configuration>
>>>> <verbose>true</verbose>
>>>> <xdebug>true</xdebug>
>>>> <!-- The name of your generated source package -->
>>>> <packageName>jaxws.server</packageName>
>>>> <target>2.1</target>
>>>>
>>>> <wsdlDirectory>${basedir}/src/main/webapp/META-INF</wsdlDirectory>
>>>> <wsdlFiles>
>>>> <wsdFile>ProfileWebService.wsdl</wsdFile>
>>>> </wsdlFiles>
>>>> </configuration>
>>>> </plugin>
>>>> </plugins>
>>>> </build>
>>>>
>>>> Is there anything I can do to debug/fix this error? I've tried to
>>>> enable m2e logback debugging but see the same thing in the Maven console -
>>>> no additional information to help me understand what/where the error is
>>>> coming from. So I'm kind of stuck. At this point, I seem to be forced to
>>>> run mvn on the command line to generate sources and then can continue
>>>> working in Eclipse. But whenever I change a WSDL, I have to regenerate the
>>>> files on the command line.
>>>>
>>>>
>>>> Any ideas/suggestions/theories?
>>>>
>>>>
>>>> Thanks,
>>>>
>>>>
>>>> Eric
>>>>
>>>> _______________________________________________
>>>> m2e-users mailing list
>>>> m2e-users@eclipse.org
>>>> To change your delivery options, retrieve your password, or unsubscribe
>>>> from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>>
>>>
>>>
>>> _______________________________________________
>>> m2e-users mailing list
>>> m2e-users@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>
>>
>>
>> _______________________________________________
>> m2e-users mailing list
>> m2e-users@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>
>
>
>
> --
> Regards,
> Anton.
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users
