You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Mark Streit <mc...@gmail.com> on 2012/02/24 06:16:30 UTC
Re: Java2WS and WSDL2Java Pro
FWIW, and we use a lot of Ant (with Ivy as well - not fully on the Maven
wagon yet)... to Glen's point - we never rely on the IDE plugins for
anything and have never had any issues. The same Ant build scripts
(build.xml files) will run in the *Ant view* in the Eclipse IDE (equivalent
to a command line invocation of your build.xml ) and we're using Windows
7...and then these also run on our Jenkins server (Suse Linux) upon
checkout from SVN during a build *w/o any modifications or problems*. We
are currently investigating the use of (CXF 2.5.2 at this point) in a move
away from Websphere 7 and its Fixpack mess (including its embedded Axis2
stack). So far, it's been impressive.
We have used both the *Java2WS *and *WSDL2Java *classes defining our own
Ant targets per the CXF documentation at:
http://cxf.apache.org/docs/java-to-ws.html and it has worked flawlessly
every time.
Following the CXF example, we have targets like this....
<target name="cxfJavaToWS" depends="compile-server">
<java classname="org.apache.cxf.tools.java2ws.JavaToWS" fork="true">
<arg value="-wsdl" />
...
...
...
<target name="cxfWSDLToJava" depends="init, copy-wsdl-local">
<java classname="org.apache.cxf.tools.wsdlto.WSDLToJava"
fork="true">
<arg value="-wsdlLocation" />
<arg value="/META-INF/wsdl/${ws.endpointName}.wsdl" />
...
...
...
These have always worked without any problems.
Regards,
Mark
On Thu, Feb 23, 2012 at 11:42 PM, Glen Mazza <gm...@talend.com> wrote:
> The way I see it, we have nothing to do with Eclipse or any other IDE--if
> we did it would mean something is wrong with CXF architecture. Your
> headaches seem to be an unfortunate consequence of not heeding Mr.
> Franklin's fine advice (http://cxf.547215.n5.nabble.**
> com/RE-How-to-deploy-to-JBoss-**td571885.html#a571888<http://cxf.547215.n5.nabble.com/RE-How-to-deploy-to-JBoss-td571885.html#a571888>),
> i.e., using cutesy toys--i.e., mittens--to get the job done rather than
> learning how to get these tasks done at the base level (i.e., from a
> command prompt window, no bells and whistles) and then (via mvn
> eclipse:eclipse) importing your project into your IDE of choice. Rather
> than learn how to get an IDE to do something--and be a slave to that IDE's
> hiccups--why not get rid of the middleman & its headaches and learn how to
> directly do that "something" instead? Take off the mittens and crack open
> a terminal window[1].
>
> Any build process that is dependent on usage of a particular IDE is
> suboptimal anyway. Most Apache projects have committers using any number
> of different IDEs--it doesn't matter because we use Maven to define the
> build process, wonderfully providing IDE independence so each developer can
> use whichever IDE he's most comfortable with.
>
> Does WSDL2Java work (1) command-line and (2) via Maven? If yes, then our
> job is done. Any IDE difficulties will be with either the IDE itself or
> with Maven (specifically, a failure in its tools that allow you to import
> its projects into your IDE.)
>
> Regards,
> Glen
>
> [1] http://www.jroller.com/gmazza/**entry/web_service_tutorial<http://www.jroller.com/gmazza/entry/web_service_tutorial>
>
>
> On 02/23/2012 08:48 PM, Michael wrote:
>
>> There appears to be a problem when generating WSDL for Java code and when
>> generating Java clients from WSDLs from Eclipse. I have searched for the
>> error received
>>
>> (java.io.IOException: Cannot run program "C:\Program
>> Files\Java\jre6\bin\javaw.exe"**: CreateProcess error=87, The parameter
>> is
>> incorrect) and it appears that this is caused by a command line that is
>> too
>> long.
>>
>>
>>
>> If this is the case I am surprised that this problem has not been
>> resolved.
>>
>>
>>
>> It appears that both Eclipse and Apache are making no attempt to fix this.
>> The impression I am getting is that it is being called a Windows problem.
>>
>>
>>
>> This may certainly be the case but one thing that might be done to fix
>> this
>> is to provide an option to have the command line parameters read in from a
>> file.
>>
>>
>>
>> I don't know if such a change is the responsibility of Eclipse, Apache or
>> both and I will be posting this same message to the Eclipse forums.
>>
>>
>>
>> Tools like Eclipse are valuable to software developers but only if they
>> work
>> properly. I urge the Apache CXF contributors to approach Eclipse about
>> this and work with them to resolve it.
>>
>>
>>
>
> --
> Glen Mazza
> Talend Community Coders
> coders.talend.com
> blog: www.jroller.com/gmazza
>
>
* **
*
RE: Java2WS and WSDL2Java Pro
Posted by Michael <mt...@optonline.net>.
Thank you both gentleman for your reply.
I am only interested in achieving successful builds consistently.
We will look into using both Ant and Maven from Eclipse to do our CXF Web
Services builds.
Mike
-----Original Message-----
From: Mark Streit [mailto:mcs130@gmail.com]
Sent: Friday, February 24, 2012 12:17 AM
To: users@cxf.apache.org
Subject: Re: Java2WS and WSDL2Java Pro
FWIW, and we use a lot of Ant (with Ivy as well - not fully on the Maven
wagon yet)... to Glen's point - we never rely on the IDE plugins for
anything and have never had any issues. The same Ant build scripts
(build.xml files) will run in the *Ant view* in the Eclipse IDE (equivalent
to a command line invocation of your build.xml ) and we're using Windows
7...and then these also run on our Jenkins server (Suse Linux) upon
checkout from SVN during a build *w/o any modifications or problems*. We
are currently investigating the use of (CXF 2.5.2 at this point) in a move
away from Websphere 7 and its Fixpack mess (including its embedded Axis2
stack). So far, it's been impressive.
We have used both the *Java2WS *and *WSDL2Java *classes defining our own Ant
targets per the CXF documentation at:
http://cxf.apache.org/docs/java-to-ws.html and it has worked flawlessly
every time.
Following the CXF example, we have targets like this....
<target name="cxfJavaToWS" depends="compile-server">
<java classname="org.apache.cxf.tools.java2ws.JavaToWS" fork="true">
<arg value="-wsdl" />
...
...
...
<target name="cxfWSDLToJava" depends="init, copy-wsdl-local">
<java classname="org.apache.cxf.tools.wsdlto.WSDLToJava"
fork="true">
<arg value="-wsdlLocation" />
<arg value="/META-INF/wsdl/${ws.endpointName}.wsdl" /> ...
...
...
These have always worked without any problems.
Regards,
Mark
On Thu, Feb 23, 2012 at 11:42 PM, Glen Mazza <gm...@talend.com> wrote:
> The way I see it, we have nothing to do with Eclipse or any other
> IDE--if we did it would mean something is wrong with CXF architecture.
> Your headaches seem to be an unfortunate consequence of not heeding Mr.
> Franklin's fine advice (http://cxf.547215.n5.nabble.**
> com/RE-How-to-deploy-to-JBoss-**td571885.html#a571888<http://cxf.54721
> 5.n5.nabble.com/RE-How-to-deploy-to-JBoss-td571885.html#a571888>),
> i.e., using cutesy toys--i.e., mittens--to get the job done rather
> than learning how to get these tasks done at the base level (i.e.,
> from a command prompt window, no bells and whistles) and then (via mvn
> eclipse:eclipse) importing your project into your IDE of choice.
> Rather than learn how to get an IDE to do something--and be a slave to
> that IDE's hiccups--why not get rid of the middleman & its headaches
> and learn how to directly do that "something" instead? Take off the
> mittens and crack open a terminal window[1].
>
> Any build process that is dependent on usage of a particular IDE is
> suboptimal anyway. Most Apache projects have committers using any
> number of different IDEs--it doesn't matter because we use Maven to
> define the build process, wonderfully providing IDE independence so
> each developer can use whichever IDE he's most comfortable with.
>
> Does WSDL2Java work (1) command-line and (2) via Maven? If yes, then
> our job is done. Any IDE difficulties will be with either the IDE
> itself or with Maven (specifically, a failure in its tools that allow
> you to import its projects into your IDE.)
>
> Regards,
> Glen
>
> [1]
> http://www.jroller.com/gmazza/**entry/web_service_tutorial<http://www.
> jroller.com/gmazza/entry/web_service_tutorial>
>
>
> On 02/23/2012 08:48 PM, Michael wrote:
>
>> There appears to be a problem when generating WSDL for Java code and
>> when generating Java clients from WSDLs from Eclipse. I have
>> searched for the error received
>>
>> (java.io.IOException: Cannot run program "C:\Program
>> Files\Java\jre6\bin\javaw.exe"**: CreateProcess error=87, The
>> parameter is
>> incorrect) and it appears that this is caused by a command line that
>> is too long.
>>
>>
>>
>> If this is the case I am surprised that this problem has not been
>> resolved.
>>
>>
>>
>> It appears that both Eclipse and Apache are making no attempt to fix
this.
>> The impression I am getting is that it is being called a Windows problem.
>>
>>
>>
>> This may certainly be the case but one thing that might be done to
>> fix this is to provide an option to have the command line parameters
>> read in from a file.
>>
>>
>>
>> I don't know if such a change is the responsibility of Eclipse,
>> Apache or both and I will be posting this same message to the Eclipse
forums.
>>
>>
>>
>> Tools like Eclipse are valuable to software developers but only if
>> they work properly. I urge the Apache CXF contributors to approach
>> Eclipse about this and work with them to resolve it.
>>
>>
>>
>
> --
> Glen Mazza
> Talend Community Coders
> coders.talend.com
> blog: www.jroller.com/gmazza
>
>
* **
*