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 100364 - Can not add an external WSDL
Summary: Can not add an external WSDL
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Sherry Weng
Keywords: RELNOTE
Depends on:
Reported: 2007-04-09 14:59 UTC by Oleg Barbashov
Modified: 2007-06-20 21:01 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

External WSDL addition bug (75.11 KB, application/x-compressed)
2007-04-09 15:00 UTC, Oleg Barbashov

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg Barbashov 2007-04-09 14:59:28 UTC
Build 200704082054. Can not add an external WSDL document. Get message box
"Error" "An I/O Error occured. Serverreturned HHTP response code: 415 for URL: ..."
Steps to reproduce:
0. Open attached projects.
1. For BpelModule3 try to add new external wsdl document
Comment 1 Oleg Barbashov 2007-04-09 15:00:15 UTC
Created attachment 40622 [details]
External WSDL addition bug
Comment 2 Shivanand Kini 2007-04-10 18:59:54 UTC
does the wsdl file appear when the URL is accessed from the browser?

Can you provide more steps as to deployment etc of the project, this will help
the QE to verify this easily.

I am guessing that you deployed the synchronoussample project and then are
trying to get that wsdl into bpelmodule3 project. Is this right?

Comment 3 Oleg Barbashov 2007-04-11 12:55:47 UTC
The URL is accessed from the browser. Firewall is disabled.
The WSDL have appeared but there is no XSD file.
You are right. First the SSA is deployed and then I tried to add new External WSDL.

The steps more precisely:
0. Open NB IDE. Start application server. Create new or open existing (see in
attachment) Synchronous BPEL Process Sample. Deploy it.
1. Open (see in attachment) or create new any simple BPEL process.
2. Try to add new external WSDL document to that process

Comment 4 Shivanand Kini 2007-04-13 22:52:29 UTC
While trying to reproduce this bug, following observations:

1. The wsdl file is successfully imported.
2.  But there is a error message box when it tries to retrieve the imported xsd.
and retriever output window has the following message

Apr 13, 2007 2:41:11 PM : Retrieving Location:
        Retrieved :    http://localhost:18181/SynchronousSample?wsdl 
        Saved at:
Retrieving Location:

        Found in document: http://localhost:18181/SynchronousSample?wsdl

Error: An I/O error occured. Server returned HTTP response code: 415 for URL:

Assigning this bug to retriever module owner for further investigation.
Comment 5 Shivanand Kini 2007-04-13 23:09:05 UTC
On further investigation, found that the URL for the xsd file is not accessible
through the browser itself.

And also saw a exception in glassfish log from the soap binding component as
Request doesnt have a Content-Type Request doesnt have a Content-Type
Comment 6 Shivanand Kini 2007-04-14 00:57:10 UTC
It seems like a runtime bug. Assigning to owner of http bc module
Comment 7 Sherry Weng 2007-04-17 00:30:20 UTC
This is actually a runtime issue. A runtime BugTracker ticket CR 6546633 
( is created for this.
Comment 8 Sherry Weng 2007-04-18 23:07:48 UTC
Fix for the runtime issue is committed.
Comment 9 jlautz 2007-04-24 19:19:01 UTC
Verified on NetBeans IDE Dev (Build 070423)
1.6.0_01; Java HotSpot(TM) Client VM 1.6.0_01-b06
Windows XP version 5.1 running on x86
en_US (nb); Cp1252

I no longer produce this error. The wsdl and its xsd are both imported into the
BPEL project when referenced by URL. I can validate the wsdl that references
this wsdl file, and define a comp app that references the BPEL project and
deploy and run it with a test case.

I am encountering what looks like a hang when I deploy the compapp, but the SA
is actually deployed to the runtime. I will log a separate bug for this issue. 

Also marking the runtime bug as verified.
Comment 10 Oleg Barbashov 2007-04-25 11:47:18 UTC
Build 200704250000. Java 1.5.0_11. Windows XP version 5.1 running on x86.

Still observe this bug. 
Comment 11 jlautz 2007-04-25 12:55:45 UTC
My bad. I verified it using an SDK build that isn't in Hula yet. I will wait to
verify this fix until we get SDK b14 into Hula.
Comment 12 jlautz 2007-04-25 12:56:38 UTC
Resetting to fixed. Reverify with Hula M9, which should contain the SDK with the
HTTP binding runtime fix.
Comment 13 Oleg Barbashov 2007-04-25 13:19:57 UTC
Ok. Let's wait.
Comment 14 Jeff Stein 2007-04-28 02:16:46 UTC
Issue: Cannot add an external WSDL document.

Description: This problem arises when importing an external WSDL and resolving
the imported resources (e.g., the XML schema definitions).

Workaround: To resolve the problem, modify the original WSDL to include the XSDs
Comment 15 Annette Wegscheider 2007-05-02 22:39:57 UTC
Added to release notes for M9 with text provided by Jeff.
Comment 16 jlautz 2007-06-20 21:01:42 UTC
Verified fixed with 
Product Version: NetBeans IDE Dev (Build 200706190000, C/C++ Pack 20070619) Java: 1.6.0_01; Java HotSpot(TM) Client VM
1.6.0_01-b06 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\Documents and

I can now perform the described scenario and access both the xsd file and the wsdl file from the deployed