<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Adding wsdlLocation in @WebServiceClient solved the problem. Thanks
Alessio.<br>
<br>
Gytis<br>
<br>
<div class="moz-cite-prefix">On 07/11/13 14:48, Alessio Soldano
wrote:<br>
</div>
<blockquote cite="mid:527BA85A.90209@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi Gytis,<br>
I assume the client you're interested in and that's calling the
service classes mentioned below is what is injecting the
@WebServiceRef annotated '<span class="n">client</span><span
class="o"></span>' attribute in <span class="nc">WSATSimpleServletClient</span>.<br>
My gut feeling is that the behavior you're seeing is an expected
consequence of having fixed a JSR 109 implementation glitch in
[1]; basically, if the wsdlLocation is not specified in the
webserviceref and the referenced Service class has no
wsdlLocation attribute in the @WebServiceClient annotation, the
implementation assumes you're willing to call a co-located
endpoint.<br>
Can you try specifying the wsdlLocation for example in the
@WebServiceClient annotation?<br>
<br>
Moreover, I'd ask you to also try the latest EAP 6.x, as I
believe that should behave the same as WFLY master.<br>
Cheers<br>
Alessio<br>
<br>
[1] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://issues.jboss.org/browse/JBWS-3679">https://issues.jboss.org/browse/JBWS-3679</a><br>
<br>
<br>
On 07/11/13 12:01, Gytis Trikleris wrote:<br>
</div>
<blockquote cite="mid:527B72ED.50106@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
EAP:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="https://github.com/jboss-developer/jboss-eap-quickstarts/blob/master/wsat-simple/src/main/java/org/jboss/as/quickstarts/wsat/simple/jaxws/RestaurantServiceATService.java">https://github.com/jboss-developer/jboss-eap-quickstarts/blob/master/wsat-simple/src/main/java/org/jboss/as/quickstarts/wsat/simple/jaxws/RestaurantServiceATService.java</a><br>
Wildfly:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="https://github.com/wildfly/quickstart/blob/master/wsat-simple/src/main/java/org/jboss/as/quickstarts/wsat/simple/jaxws/RestaurantServiceATService.java">https://github.com/wildfly/quickstart/blob/master/wsat-simple/src/main/java/org/jboss/as/quickstarts/wsat/simple/jaxws/RestaurantServiceATService.java</a><br>
<br>
<div class="moz-cite-prefix">On 07/11/13 10:46, Alessio Soldano
wrote:<br>
</div>
<blockquote cite="mid:527B6F69.6020007@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Gytis,<br>
can you please link me the code of the client mentioned
here, both in WFLY and EAP quickstarts?<br>
<br>
On 07/11/13 11:36, Gytis Trikleris wrote:<br>
</div>
<blockquote cite="mid:527B6D41.5060904@redhat.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hello,<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
I am trying to make wsat-simple quickstart (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="https://github.com/wildfly/quickstart/tree/master/wsat-simple">https://github.com/wildfly/quickstart/tree/master/wsat-simple</a>)
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.<br>
<br>
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.<br>
<br>
Is there any way to make Wildfly use WSDL from the
deployment the same way EAP does it?<br>
<br>
Thanks,<br>
Gytis<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wildfly-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Alessio Soldano
Web Service Lead, JBoss</pre>
</blockquote>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Alessio Soldano
Web Service Lead, JBoss</pre>
</blockquote>
<br>
</body>
</html>