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.
Summary: | Exception from registry loader when platform.properties not defined | ||
---|---|---|---|
Product: | javaee | Reporter: | _ pcw <pcw> |
Component: | Code | Assignee: | _ pcw <pcw> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Stack trace |
Description
_ pcw
2004-09-28 20:02:42 UTC
Created attachment 17906 [details]
Stack trace
The NPE is easy enough to fix... the real problem is that the registry module now depends on the appserver jars at runtime, including startup. If this path has not been set, the module should not enable itself (but if the path is found on next start, it should not stay disabled.) What is the best way to do that? Registry module now behaves nicely when no SJSAS support (and thus no backing for web services) is available. Node is present, marked Disabled, with a tool tip telling to go to Tools | J2EE Platform Manager to enable it. *** Issue 49681 has been marked as a duplicate of this issue. *** Build 041004 Move from temp component. |