[
https://issues.apache.org/jira/browse/AXIS2-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465630
]
Manoj Khangaonkar commented on AXIS2-1912:
------------------------------------------
Can one of the committer comment on this & perhaps commit it.
It is a trivial fix , but makes the use of java2WSDL less annoying.
The current script overrides any existing CLASSPATH. Any there is simply no
reason to require every user to use to -cp . (dot) command line option every
time.
An even better fix might be to do
set AXIS2_CLASS_PATH=.;%CLASSPATH%;%AXIS2_HOME%
Axis2-1714 seems to be a similar issue.
As already mentioned , on the unix side, this is already done in setenv.sh
thanks
> java2WSDL.bat needs to use existing CLASSPATH as well
> -----------------------------------------------------
>
> Key: AXIS2-1912
> URL: https://issues.apache.org/jira/browse/AXIS2-1912
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen, wsdl
> Affects Versions: 1.2, 1.1.1, 1.1
> Environment: Windows
> Reporter: Manoj Khangaonkar
> Attachments: java2wsdl.bat
>
>
> Users may have an existing environment variable CLASSPATH - that points to
> the current directory and other directories as well as other jars.
> java2WSDL.bat needs to append the existing classpath to AXIS2_CLASS_PATH as in
> set AXIS2_CLASS_PATH=%CLASSPATH%;%AXIS2_HOME%
> This saves user the trouble of adding multiple -cp options at the command
> line.
> Attached is an updated java2WSDL.bat as a patch.
> java2wsdl.sh already does the same
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
