| Author |
wsgen command line problem
|
John Farrel
Ranch Hand
Joined: May 24, 2010
Posts: 65
|
|
I'm using wsgen to generate a web service on an established system.
We are currently upgrading our java version and run across a problem.
We can no longer run wsgen because of the size of the command-line required to run it on a windows system. This is because the system includes many libraries, and moving java versions has introduced more.
The end result is a command line over 11000 characters long, which is too long for the windows OS.
How can I reduce this to a usable size?
I'm putting the libraries in a directory with a short path, but it's not enough.
I could theoretically put all the libraries into one megalibrary with various bits of code, but it makes our whole development environment less intuitive to use, and may cause other problems.
Any ideas?
John
|
 |
James Boswell
Ranch Hand
Joined: Nov 09, 2011
Posts: 657
|
|
John
I would always use Maven for such a task:
http://mojo.codehaus.org/jaxws-maven-plugin/wsgen-mojo.html
|
 |
John Farrel
Ranch Hand
Joined: May 24, 2010
Posts: 65
|
|
But that would still end up calling wsgen underneath, wouldn't it?
|
 |
James Boswell
Ranch Hand
Joined: Nov 09, 2011
Posts: 657
|
|
|
Yes John but Maven will handle your command line issues for you.
|
 |
 |
|
|
subject: wsgen command line problem
|
|
|