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 40604 - sun-web.xml in another location: error
Summary: sun-web.xml in another location: error
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Pavel Buzek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-28 18:22 UTC by _ ludo
Modified: 2004-09-20 18:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
exception (2.49 KB, text/plain)
2004-02-28 18:23 UTC, _ ludo 		Details
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 _ ludo 2004-02-28 18:22:01 UTC 
If you copy a sun-web.xml file and paste it on
another location, and double click on it, I have
an exception.

I don't think configure should be possible there.
Only plain XML capabilities (editing, validation).

Also, on the good sun-web.xml in the xml editor, I
don't have the Check XML popup actions...
I did register all our sun* doctypes in the registry.
How can we enable Check XML?
Comment 1 _ ludo 2004-02-28 18:23:42 UTC 
Created attachment 13725 [details]
exception
Comment 2 Pavel Buzek 2004-03-05 19:20:34 UTC 
I believe the check xml portion was fixed (before high resistence) the
other part is not a show stopper and has to wait for promo-D.
Comment 3 Pavel Buzek 2004-09-02 20:06:57 UTC 
The problem with copy/paste is that nb does not invalidate the data
object after c/p. We will need to override paste and invalidate the DO
to force the file being recognized by xml loader. If you just create a
file with the same name it will not be recognized by config loader but
standard xml.
Comment 4 Pavel Buzek 2004-09-20 18:17:28 UTC 
I have added a code that invalidates the new DO at paste and forces
creation of a new DO. If this should fail for any reason (setValid is
vetoable) -- which I am not able to simulate -- I see that now you
only get an informational exception message in log. Nothing would be
displayed to the user and the XML editor would be open instead of the
UI editor.

cvs commit -m "40604 sun-web.xml in another location: error (force
using correct loader when pa..."
org\netbeans\modules\j2ee\deployment\config\ConfigDataObject.java (in
directory E:\nb_all\j2eeserver\src\)
Checking in
org/netbeans/modules/j2ee/deployment/config/ConfigDataObject.java;
/cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/config/ConfigDataObject.java,v
 <--  ConfigDataObject.java
new revision: 1.19; previous revision: 1.18
done