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 203517 - Spring config files don't have history tab and save action
Summary: Spring config files don't have history tab and save action
Status: VERIFIED DUPLICATE of bug 190343
Alias: None
Product: javaee
Classification: Unclassified
Component: Spring (show other bugs)
Version: 7.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Martin Fousek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-11 14:09 UTC by Jiri Skrivanek
Modified: 2011-10-19 07:31 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 Jiri Skrivanek 2011-10-11 14:09:56 UTC 
Save action is disabled when Spring files applicationContext.xml and dispatcher-servlet.xml are modified. They are also missing History tab in editor. To reproduce:

- create web project with Spring framework
- open WEB-INF/applicationContext.xml and WEB-INF/dispatcher-servlet.xml
- modify each file and try to save it (Ctrl+S). It is not possible. If you expand File main menu, save action is disabled. Additionally there is no history tab.
- open new file wizard
- choose "Spring Framework|Spring XML Configuration File" and finish the wizard
- created config file behaves the same way as two files above

Product Version: NetBeans IDE Dev (Build 201110100600)
Java: 1.7.0; Java HotSpot(TM) Client VM 21.0-b17
System: Windows XP version 5.1 running on x86; Cp1250; en_US (nb)
Comment 1 Martin Fousek 2011-10-11 15:43:38 UTC 
Ups, thanks that you noticed that.
Comment 2 Martin Fousek 2011-10-18 16:06:52 UTC 
Quite probably it's related to bug #190343? Please try to restart your IDE and check history tab and save action on these files then, it should definitely work. Feel free to reopen if not.

Just FYI, I'm investigating what happens in cases of #190343, but it seems that it could be somewhere deeper.

*** This bug has been marked as a duplicate of bug 190343 ***
Comment 3 Jiri Skrivanek 2011-10-19 07:31:37 UTC 
Yes, after restart MIME types are correctly recognized and everything works.