Hi Gytis,
I assume the client you're interested in and that's calling the
service classes mentioned below is what is injecting the
@WebServiceRef annotated '
client' attribute in
WSATSimpleServletClient.
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.
Can you try specifying the wsdlLocation for example in the
@WebServiceClient annotation?
Moreover, I'd ask you to also try the latest EAP 6.x, as I believe
that should behave the same as WFLY master.
Cheers
Alessio
[1]
https://issues.jboss.org/browse/JBWS-3679
On 07/11/13 12:01, Gytis Trikleris wrote: