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 182847 - [69cat][issuereporter][bugzilla] Issue Reporter can submit issue without providing confirmation to user.
Summary: [69cat][issuereporter][bugzilla] Issue Reporter can submit issue without prov...
Status: RESOLVED WONTFIX
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: 6.x
Hardware: PC Linux
: P4 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-26 06:14 UTC by esmithbss
Modified: 2012-12-05 12:55 UTC (History)
0 users

See Also:
Issue Type: DEFECT
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 esmithbss 2010-03-26 06:14:56 UTC 
[ BUILD # : 201003230200 ]
[ JDK VERSION : 1.6.* ]

Product Version = NetBeans IDE Dev (Build 201003230200)
Operating System = Linux version 2.6.32-17-generic running on i386
Java; VM; Vendor = 1.6.0_18
Runtime = Java HotSpot(TM) Client VM 16.0-b13

There exists a possibility within the issue reporting workflow for an issue to
be submitted to the bugzilla system without providing sufficient feedback to
the user that the bug was submitted.

If the bug is submitted and the return message is not received by the IDE, then
the error that is displayed is a Socket Time Out exception which typically
indicates a failure on communication that demands the user re-submit their
issue.  This leads to duplication issues within the Bugzilla system.

Without letting the user know the state of the submission, the user has no way
of knowing whether the submission failed on the send or on the receive.

The system needs to have one of either:

* A status indicator telling the user where in the transmission sequence the
reporter is (sending, waiting, receiving, etc...)
or
* A two phase commit where the message is sent, then the commit is issued.
Comment 1 Tomas Stupka 2010-03-30 13:25:11 UTC 
agree. more detailed info about the progress and at what phase an error happened would be useful 

> A two phase commit where the message is sent, then the commit is issued.
not sure i understood this part. elaborate please ?
Comment 2 Tomas Stupka 2012-12-05 12:55:13 UTC 
doesn't seem to be that bothering and hence something we should focus on. closing for now.