This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 89709 - WSDL, localhost in soap:address doesn't work for remote client.
Summary: WSDL, localhost in soap:address doesn't work for remote client.
Status: VERIFIED INVALID
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@xml
URL:
Keywords:
Depends on:
Blocks: 89926
  Show dependency tree
 
Reported: 2006-11-20 23:10 UTC by Sherry Barkodar
Modified: 2007-04-03 07:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sherry Barkodar 2006-11-20 23:10:14 UTC 
In BPEL project when creating a WSDL document, the soap:address is generated as
following: 
<soap:address
location="http://localhost:18181/LoanRequestorService/LoanRequestorPort"/>
When creating web service client to call the webservice (BPEL) from a remote
machine,  this URL doesn't mean anything.
When webservice client is executed on remote machine it uses: <soap:address
location="http://localhost:18181/LoanRequestorService/LoanRequestorPort"/>. 
You have to manually edit the WSDL document, soap:address to your machine name:
<soap:address
location="http://arash.sfbay.sun.com:18181/LoanRequestorService/LoanRequestorPort"/>
otherwise you can not run the client:
Comment 1 Shivanand Kini 2007-01-18 20:48:35 UTC 
The expectation is that the user always needs to change this attribute and not
go by the default. Marking this as invalid
Comment 2 jlautz 2007-04-03 07:55:11 UTC 
Assuming that this is now acceptible behavior, because the reporter did not push
back on this issue. Verifying that the WSDL wizard is working as designed.