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 83239 - XDesign: How to inform user about broken import/include and give option to fix it with out wizard?
Summary: XDesign: How to inform user about broken import/include and give option to fi...
Status: NEW
Alias: None
Product: xml
Classification: Unclassified
Component: Schema Tools (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jiri Kopsa
URL:
Keywords:
Depends on:
Blocks: 82944
  Show dependency tree
 
Reported: 2006-08-23 00:57 UTC by Girish Balachandran
Modified: 2006-08-25 23:09 UTC (History)
0 users

See Also:
Issue Type: TASK
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 Girish Balachandran 2006-08-23 00:57:51 UTC 
The premise of this bug is issue:
http://xml.netbeans.org/issues/show_bug.cgi?id=82944


As mentioned in the above issue, I fixed it by automatically retrieving the
missing URL resource (with its closure) and caching it in a private cache. But,
the user experience seems to be really flaky when the retriever is running. For
example, if the user included main UBL file in his schema, then retrieving the
closure of it will take a considerable amount of time depending on the internet
connection speed. UI tends to freeze during this period, if the retriever was
called from a non-swing thread. Also, the user may not have any clue as in why
retriever is suddenly being run. The design view will not funcion properly with
out all the closure schemas.

We need a better way to present the broken import/include information to the
user in all the views. So, as soon as the user opens a schema/wsdl and if that
schema is broken for any import/include for URL resource(s), then we have to
show the broken message to the user and give him a chance to fix it. Retriever
already shows a progress bar while it is downloading so, extra feedback may not
be required while retriever is running.

One solution we think is to show a "Bulb message" (as shown in Design view) in
all the views and give the following options to the user:
1. Use retriever wizard and save remote files in local project.
2. Use retriever API silently (with already existing non-intrusive UI progress
feedback) to pull down and cache in private folder.

Please pass on your suggestions.
Comment 1 Ritesh Adval 2006-08-24 18:52:44 UTC 
Another option to look at is to make it explicit to user:

When user sees broken reference we could show an action to retrieve that 
refercened entity and launch retriever at that point.

Also not sure if creating another catalog and linking it with project catalog
is a good option. Why not use project catalog?

I think this is what you have as option 1 and I prefer that.