Invocation of bin/wsprovide.sh without any parameter produces this help message: [root@dev131 jbossas]# bin/wsprovide.sh Error: endpoint implementation was not specified! WSProvideTask generates portable JAX-WS artifacts for an endpoint implementation. usage: WSProvide [options] <endpoint class name> options: -h, --help Show this help message -k, --keep Keep/Generate Java source -w, --wsdl Enable WSDL file generation -a, --address=<address> The generated port soap:address in wsdl -c, --classpath=<path> The classpath that contains the endpoint -o, --output=<directory> The directory to put generated artifacts -r, --resource=<directory> The directory to put resource artifacts -s, --source=<directory> The directory to put Java source -e, --extension Enable SOAP 1.2 binding extension -q, --quiet Be somewhat more quiet -t, --show-traces Show full exception stack traces -l, --load-provider Load the provider and exit (debug utility) [root@dev131 jbossas]# Problematic part is 'usage: ...', there should be sth like (remove upper-letters): "usage: wsprovide [options] <wsdl-url>" Or better there should be wsprovide.sh for UNIX-like shells and wsprovide.bat for Windows-like, but I'm not sure if it is possible there.
There's a system property "program.name" which can be set to control the name there. Pavel, can you verify if adding "-Dprogram.name=wsconsume.sh" / "-Dprogram.name=wsconsume.bat" to the JAVA_OPTS in the wsconsume.sh/bat scripts addresses your concerns? If that's ok, I can create jiras for fixing upstream and fix it here too.
Hi Alessio, that's exactly what I'm looking for. Could you change both - wsconsume.sh/bat and wsprovide.sh/bat shell wrappers please? Thank you.
Verified on EAP 6.2.0 ER3