• Post Reply Bookmark Topic Watch Topic
  • New Topic

Do I need to use local WSDL file if at server side http get WSDL is blocked

 
walter wang
Ranch Hand
Posts: 159
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

At Server side the http get is blocked for wsdl, in this case, Is there a good way to make soap client call?

Any hints will be more than welcome!


 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13078
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If access to the WSDL is blocked - presumably by security - it seems likely that access to the web service itself will have the same restrictions.

Time to get some documentation on the service itself perhaps?

Bill
 
walter wang
Ranch Hand
Posts: 159
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
only http get for serverside wsdl is blocked. post still works , but i have this wsdl file at soap client before hand already.
what i did is just use this local wsdl file, but replace soap address with real server address. I want to replace the soap address (dummy address) in local wsdl
with real soap address on the fly(at run time)

Rgds
 
stewchicken
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
below way could solve the problem

BindingProvider provider = (BindingProvider) port;
// You can set the address per request here
provider.getRequestContext().put(
BindingProvider.ENDPOINT_ADDRESS_PROPERTY,
soapAddressURL);

 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!