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 131779 - Changes to WSIT server properties do not mark service assembly as edited (no asterisk)
Summary: Changes to WSIT server properties do not mark service assembly as edited (no ...
Status: REOPENED
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jun Qian
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-01 23:37 UTC by jlautz
Modified: 2008-04-02 02:08 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 jlautz 2008-04-01 23:37:19 UTC 
Seen with M8 build on Solaris x86:

Product Version: NetBeans IDE Dev (Build 200803251204) - Java CAPS Enabled
Java: 1.5.0_11; Java HotSpot(TM) Client VM 1.5.0_11-b03
System: SunOS version 5.10 running on x86; ISO646-US; en (nb)
Userdir: /Users/lautz/sierrabuilds/JavaCAPSM8/.netbeans/caps

Changing Web Service Property settings in the WS Policy Attachment dialog does not make the service assembly (CASA
document) "edited" -- there is no asterisk indicating that something has changed that needs to be saved and rebuilt.

This is a P3, because the user is prompted to save changes when the document is closed, so the changes are not likely to
be lost.
Comment 1 Jun Qian 2008-04-02 00:15:51 UTC 
This is similar to 96390. Configuring WSIT makes the WSDL document "dirty". The CASA document itself is not really modified.
Comment 2 jlautz 2008-04-02 01:43:08 UTC 
Unfortunately, the WSDL file is not actually changed until we do the Build Project, and there's no indicator that we
need to do that. The WSDL editor does not show the WSDL file as "dirty", because it hasn't been regenerated yet.

I'll change this to a usability enhancement if you'd like (or you can go ahead).
Comment 3 Jun Qian 2008-04-02 02:08:02 UTC 
You are right. When I added the previous comment, I was thinking about 96390. 

Changed to enhancement.