[wildfly-dev] Overwriting WSDL on EAP and Wildfly

Gytis Trikleris gytis at redhat.com
Thu Nov 7 05:36:49 EST 2013


Hello,

I am trying to make wsat-simple quickstart ( 
https://github.com/wildfly/quickstart/tree/master/wsat-simple) to work 
on two Wildfly servers (one as a client, another as a server). For the 
client I use 127.0.0.2 and for the server 127.0.0.3 IP addresses. I 
changed client WSDL to call 127.0.0.3 and it works fine on EAP 6.1 and 
EAP6.2.Beta1. However, it does not work on Wildfly master.

I did some debugging and the main difference I found is that EAP and 
Wildfly calls different constructors on client side Service 
implementation (RestaurantServiceATService class). EAP uses not 
parametrised constructor so the client gets initialized with my modified 
WSDL i.e. makes calls to 127.0.0.3. On the other hand, Wildfly uses 
parametrised constructor and passes URL to the AS generated WSDL which 
makes client to make calls to the same server as it is deployed i.e. 
127.0.0.2.

Is there any way to make Wildfly use WSDL from the deployment the same 
way EAP does it?

Thanks,
Gytis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20131107/e38471dd/attachment.html 


More information about the wildfly-dev mailing list