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 85298

Summary: External reference resolution using location as backup causes bad performance and user experience
Product: xml Reporter: Nam Nguyen <nnguyen>
Component: XAMAssignee: Nam Nguyen <nnguyen>
Status: VERIFIED FIXED    
Severity: blocker CC: issues
Priority: P2 Keywords: PERFORMANCE
Version: 5.x   
Hardware: All   
OS: Windows XP   
Issue Type: DEFECT Exception Reporter:
Bug Depends on:    
Bug Blocks: 85075    
Attachments: schema/api fix
xam fix
wsdl/api fix

Description Nam Nguyen 2006-09-20 02:35:50 UTC
Currently AbstractDocumentComponent.resolveModel allow subclass to use namespace
as backup hint in resolving import/include/redefine constructs in xsd, wsdl,
bpel files.  Since the large percentage of namespace values does not actually
resolve to a real location, this usage has some impact on performance of
XAM-base systems depending on the underlying catalog implementations.  In
particular, the Retriever (xml/retriever) have background auto retrieval which
makes the impact more pronounced and more visible to IDE users.
Comment 1 Nam Nguyen 2006-09-20 02:39:26 UTC
Since none of the IDE and non-IDE use cases needs to resolve references using
namespace as location hint, the fix to deprecated the usage of namesapce in the
API.  The default behaviour is only use the first hint for location and ignore
the backup hint.
Comment 2 Nam Nguyen 2006-09-20 03:07:48 UTC
Created attachment 34206 [details]
schema/api fix
Comment 3 Nam Nguyen 2006-09-20 03:09:14 UTC
Created attachment 34207 [details]
xam fix
Comment 4 Nam Nguyen 2006-09-20 03:11:16 UTC
Created attachment 34208 [details]
wsdl/api fix
Comment 5 Nam Nguyen 2006-09-20 03:12:44 UTC
Fix checked in release55_dev.  Pending review for release55 approval.
Comment 6 Nam Nguyen 2006-09-21 00:57:38 UTC
Fixes merged into release55.
Comment 7 tonybeckham 2007-04-11 00:43:51 UTC
nnguyen:
This issue is marked as resolved. Since it relates to some source code
specifics, QA is unable to verify it. Could you please verify this issue and
mark it as verified?
Comment 8 Nam Nguyen 2007-04-11 01:11:54 UTC
verified