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 211871 - Issues in handling ApplicationConfig
Summary: Issues in handling ApplicationConfig
Status: NEW
Alias: None
Product: webservices
Classification: Unclassified
Component: REST (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Milan Kuchtiak
Depends on:
Reported: 2012-04-27 17:03 UTC by Petr Jiricka
Modified: 2013-07-24 08:08 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2012-04-27 17:03:04 UTC
After addressing issue 209713 (simplifying REST configuration), there are several problems in handling ApplicationConfig:

1. The default package for ApplicationConfig should not be, as this is not NetBeans code. How about
<application_name>.rest.config, i.e. for example
This would be consistent with the naming of main class in Java SE projects.

2. It happened to me that when I created the first REST service, the
ApplicationConfig was empty, i.e. methods getClasses() and getResourceClasses()
were missing. (They were then created when I created a second web services.)
But this looks like a random issue, in another case these methods were creating
while creating the first service in the project.

3. After we change ApplicationConfig, it should be saved I think - currently we
leave it modified in editor.

4. After moving ApplicationConfig to another package, creating additional REST services will not update ApplicationConfig. The REST support should detect that this class has moved and declare newly created classes in the new moved ApplicationConfig.