Re: [wildfly-dev] Overwriting WSDL on EAP and Wildfly

Gytis, can you please link me the code of the client mentioned here, both in WFLY and EAP quickstarts? On 07/11/13 11:36, Gytis Trikleris wrote: > 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 > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev -- Alessio Soldano Web Service Lead, JBoss