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 87510 - Scalability: With big WSDL file, new port type creation does not define matching partnerlink type
Summary: Scalability: With big WSDL file, new port type creation does not define match...
Status: RESOLVED WONTFIX
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Shivanand Kini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-19 13:17 UTC by jlautz
Modified: 2016-07-07 09:56 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
original big file and copy of big file with results of adding a new port (723.82 KB, application/octet-stream)
2006-10-19 13:23 UTC, jlautz 		Details
Stack trace from log file -- possibly unrelated to this bug. (11.13 KB, application/octet-stream)
2006-10-19 13:23 UTC, jlautz 		Details
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 jlautz 2006-10-19 13:17:10 UTC 
Seen on Windows XP with NB 55 and JDK 1.5.0_07:

This is based on minimal scalability testing with a 3+ meg WSDL file.

1. Choose a big, fast machine and crank up the netbeans.conf memory settings. I
went with -J-Xmx1024m to get the port type generated at all.
2. Import the attached ebay WSDL file from
http://developer.ebay.com/webservices/latest/eBaySvc.wsdl. (Go get a cup of coffee.)
3. Select the Port Types node and choose Add Port Type from the context menu.
4. Go with the default values or change them. I:
-- changed the names of the port type and operation 
-- chose an existing message type for the input
-- chose an element for the output message part
-- added a part to the fault
-- clicked Next.
( . . This takes a really long time . . . . )
==> The port type seems to be correctly added, but the partnerlink type that is
usually generated when we used the New Port Type dialog is not generated. No
error message or other indication of a problem is seen in the UI, although the
attached exception was in the NB log, although I have no idea whether it's
related to this issue.

Attached is a zip containing both the original wsdl file, a copy of the same
file that I added the port type to, as described. Also attached is the stack
trace I found in the NB log.
Comment 1 jlautz 2006-10-19 13:23:12 UTC 
Created attachment 35378 [details]
original big file and copy of big file with results of adding a new port
Comment 2 jlautz 2006-10-19 13:23:43 UTC 
Created attachment 35379 [details]
Stack trace from log file -- possibly unrelated to this bug.
Comment 3 jlautz 2006-10-19 13:41:49 UTC 
Additional note, although I specified the default Request-Response operation
type, no input message was generated for the port type. See "newPortType" port
type in the eBaySvc_copy.wsdl file.
Comment 4 Shivanand Kini 2007-06-26 22:12:25 UTC 
This seems to have been fixed after performance related changes.

I was able to go through the scenario without any changes.
Please try without changing the memory setting first.
Comment 5 jlautz 2007-08-21 22:23:25 UTC 
I see the same behavior with 
Product Version: NetBeans IDE Dev (Build 200708210000) 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 Settings\lautz\.netbeans\dev

My machine has "only" 1GB RAM.
Comment 6 Martin Balin 2016-07-07 09:56:17 UTC 
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss