Status: Closed (View Workflow)
Affects Version/s: EAP_EWP 5.1.1 ER1, EAP_EWP 5.1.1 ER2
Fix Version/s: EAP_EWP 5.1.2 ER1
Component/s: Web Services
Release Notes Text:JBossWS shell script and batch files from the CXF stack (wsconsume, wsprovide, wsrunclient) were inconsistent with their use of the <code>-Djava.net.preferIPv4Stack</code> configuration option. This has been changed and both the Native and CXF stacks are configured with an IPv4 preference.
Release Notes Docs Status:Documented as Resolved Issue
There is inconsistency in WS .sh/.bat files in jboss-as/bin between Native and CXF stack.
All WS Native .sh files in EAP contain JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true", but WS CXF .sh files not.
All WS Native .bat files in EAP contain set JAVA_OPTS=%JAVA_OPTS% -Djava.net.preferIPv4Stack=true, but WS CXF .bat files not.
Chnages in WS Native .sh/.bat files are done in EAP build process, see  and search for IPv4Stack.
JBPAPP-2868 is tracking JIRA for this change. Regarding JBPAPP-2868 comments EAP 5.1 does not support IPv6.
CXF zip is not influenced by EAP tag build process, it's just dependency. Changes need to be done in WS CXF EAP branch .
I suggest to the the same changes in WS Native EAP branch  too and than later remove IPv4 string replace target in build-distr.xml from EAP branch  - I can do that.
Alessio, what do you think about it?