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 164161 - There is no way to edit added referenced resource
Summary: There is no way to edit added referenced resource
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-30 10:04 UTC by Vitaly Bychkov
Modified: 2009-12-11 17:01 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vitaly Bychkov 2009-04-30 10:04:49 UTC
There is no way to edit added Referenced resource.

For now there is no property sheet for the node representing referenced resource nor edit action.
Also since referenced resource node name is a referenced resource URI it would be nice to have a quick edit feature -
single-click on a referenced resource node, or press F2.
Comment 1 Vladimir Yaroslavskiy 2009-04-30 10:29:58 UTC
I think new popup action "Edit" should be implemented and it's enough.
Comment 2 Vladimir Yaroslavskiy 2009-07-21 14:39:13 UTC
implemented: http://hg.netbeans.org/soa-dev65/rev/b90c49844e04

Edit = Add + Delete
Comment 3 Vladimir Yaroslavskiy 2009-10-23 08:28:39 UTC
I'm reopening to implement additional request.

-------- Original Message --------
Subject: Re: Issue 164161
Date: Wed, 21 Oct 2009 08:56:39 -0700
From: Terry Braun
To: Vladimir Yaroslavskiy

Hi Vladimir,

Thank you very much for your explanations. Given what you have said, I 
agree the enhancement does what you want it to.

But since you asked ..... I will accept the challenge to suggest another 
vision for the implementation. How practical this is may be problematic, 
but I think it makes it clearer to the user.

a) If the type of referenced resource can be identified, it would make 
sense to have a different context menu for "Local" and "Remote" resources.

b) For the "Local" resources, the context menu would have three selections:

    1) an "Open resource" selection would behave as the current "Open"
    selection does, with the added clarity that you are opening a
    resource which would suggest the "OpenCookie" implementation you
    have described.

    2) a "Replace with ..." selection to take care of the surprise I
    found in my observation 5. Selecting this would give the "Open"
    dialog, and the user would understand that they were navigating to
    the location of the WSDL, JAR, or whatever file for replacement, and
    when they clicked the "Open" button the replacement would make sense
    as a "Replace with..."

    3) a "Delete resource" selection to take care of the surprise I
    found in my observation 4. Selecting this, would not give the "Open"
    dialog, and the user would understand that they are simply deleting
    the WSDL, JAR, or whatever file.

c) For the "Remote" resources, the context menu would have four selections:

    1) an "Open URL" selection would connect to the browser and display
    exactly what it does now.

    2) an "Edit URL" selection would display and implement the "Input"
    dialog for changing the URL that is currently used.

    3) a "Reload resource ..." selection that would do what the "Reload"
    selection currently does. [Thank you for the clarification how to
    get to this, but it is not clear what reloading does. I would assume
    something is being changed in my project, but since there no visible
    indication of something being done, I don't know what it is. Is
    there some file, reference, or folder I can look at/into to verify
    that changes to the remote resource have been updated in my project?

    4) a "Delete URL" selection which would simply delete the resource.

This vision of the implementation assumes different context menus (which 
may not be possible) and may not be consistent with basic user interface 
principles, but I think it would give the user a better feeling for what 
they are doing.

Terry
Comment 4 Vladimir Yaroslavskiy 2009-10-26 12:05:26 UTC
fixed in gfesbv22: 07d5b847ebe4
Comment 5 terrybraun 2009-12-11 17:01:17 UTC
This issue is tested and verified with the GFESB Build of 12/07/09, including NetBeans IDE 6.7.1 (Build 200911291800).