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: | Erroneous J2EE hints/warnings when not using J2EE project. | ||
---|---|---|---|
Product: | javaee | Reporter: | dave.trombley |
Component: | Persistence | Assignee: | Sergey Petrov <sj-nb> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | hmichel, jlahoda |
Priority: | P3 | ||
Version: | 7.2.1 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
dave.trombley
2013-01-11 00:57:49 UTC
As persistence know nothing about hibernate/spring and it's better to keep this independence as much as possible, best would e to allow to disable this warnings. - above comment is about pu warning. - regarding accessors, I see only "When property access is used, the property accessor methods must be public or protected." and nothing related to ee or se environment. but there is an issue, the warming may appear even in case of fields access as I see from code but I'm not sure if it's the reported case. - serializable is good to implemet regardless of ee also, I suppose to keep thois warning "If an entity instance is to be passed by value as a detached object (e.g., through a remote interface), the entity class must implement the Serializable interface" serilizable entity may be used more freely. But in general it's nice to be able to configure hints as it's possible for most java hunt (disable/enable). So if someone don't like serializable hint it will be possible to switch off. I'm keeping this one issue open to update setter/getter hint. Configurable hints are tacked under another task issue. *** This bug has been marked as a duplicate of bug 232006 *** I don't think this issue is a duplicate of #232006. It is about erroneous hints for non Java EE projects. The other issue is about erroneous hints for some cases at Java EE projects. To be more specific, these issue is more about non-JPA frameworks and 232006 is about JPA hint bug. see comment #2, this issue was kept to cover the same use-case as in 232006, intiially there was a set of sunbissue and it's improper issues usage as it's much better to have one problem per issue. *** This bug has been marked as a duplicate of bug 232006 *** |