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 132399 - Initializing... error, when dnd from my web service
Summary: Initializing... error, when dnd from my web service
Status: VERIFIED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: Manager (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Peter Liu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-09 13:30 UTC by Jaroslav Pospisil
Modified: 2008-10-02 17:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log (57.62 KB, text/plain)
2008-04-09 13:31 UTC, Jaroslav Pospisil
Details
screenshot (121.48 KB, image/png)
2008-04-09 13:32 UTC, Jaroslav Pospisil
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Pospisil 2008-04-09 13:30:38 UTC
Build 200804082140 (RC1), JDk1.6.0_05, Win Vista

If I add my web service with default operation, created and deployed in JavaEE5 web application and 
dnd its operation just after the operation node become available, I'll get IllegalStateException and 
web service's node will appear with hourglass. This is definitely timing issue, because if i wait a while longer 
before dnd, this don't occur. In this decribed case, however, I have to delete web service's node from manager and add
it again, since only Delete operation is enabled.Attaching screenshot.
Comment 1 Jaroslav Pospisil 2008-04-09 13:31:25 UTC
Created attachment 59896 [details]
messages.log
Comment 2 Jaroslav Pospisil 2008-04-09 13:32:03 UTC
Created attachment 59897 [details]
screenshot
Comment 3 Peter Liu 2008-07-18 23:25:17 UTC
What's happening here is that when the user first adds the web service, the manager immediately tries to load and
compile the wsdl. While that is going one, when the user tries to open the node (before the wsdl is ready), the manager
again tries to load and compile the wsdl. Therefore, there are two threads trying to load the wsdl and hence the race
condition.

The fix is to not initiate the wsdl loading when the ws is first added and only do that when the user opens the node.

Fix checked into the trunk: http://hg.netbeans.org/main/rev/8968685a318e
Comment 4 Jaroslav Pospisil 2008-10-02 17:03:51 UTC
v.