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 226435 - NoClassDefFoundError: Could not initialize class org.netbeans.modules.j2ee.jpa.verification.JPARulesEngine
Summary: NoClassDefFoundError: Could not initialize class org.netbeans.modules.j2ee.jp...
Status: RESOLVED INCOMPLETE
Alias: None
Product: javaee
Classification: Unclassified
Component: Persistence (show other bugs)
Version: 7.3
Hardware: All Windows 7 x64
: P3 normal with 1 vote (vote)
Assignee: Sergey Petrov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-21 08:08 UTC by danfalos
Modified: 2013-07-28 04:33 UTC (History)
6 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 198724

Attachments
stacktrace (3.74 KB, text/plain)
2013-02-21 08:08 UTC, danfalos 		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 danfalos 2013-02-21 08:08:36 UTC 
Build: NetBeans IDE Dev (Build 201302132300)
VM: OpenJDK 64-Bit Server VM, 23.2-b09, OpenJDK Runtime Environment, 1.7.0_09-icedtea-mockbuild_2013_02_07_23_07-b00
OS: Linux

Stacktrace: 
java.lang.NoClassDefFoundError: Could not initialize class org.netbeans.modules.j2ee.jpa.verification.JPARulesEngine
   at org.netbeans.modules.j2ee.jpa.verification.JPAProblemFinder.processClass(JPAProblemFinder.java:173)
   at org.netbeans.modules.j2ee.jpa.verification.JPAProblemFinder.access$000(JPAProblemFinder.java:95)
   at org.netbeans.modules.j2ee.jpa.verification.JPAProblemFinder$1.run(JPAProblemFinder.java:146)
   at org.netbeans.modules.j2ee.jpa.verification.JPAProblemFinder$1.run(JPAProblemFinder.java:134)
   at org.netbeans.modules.j2ee.persistenceapi.metadata.orm.annotation.EntityMappingsMetadataModelImpl$2.call(EntityMappingsMetadataModelImpl.java:89)
   at org.netbeans.modules.j2ee.metadata.model.api.support.annotation.AnnotationModelHelper.runCallable(AnnotationModelHelper.java:256)
Comment 1 danfalos 2013-02-21 08:08:38 UTC 
Created attachment 131646 [details]
stacktrace
Comment 2 Sergey Petrov 2013-02-27 05:05:30 UTC 
I can expect it's related or a duplicate with issue 226296.
Comment 3 Sergey Petrov 2013-03-16 12:42:09 UTC 
I expect it may be fixed at least in some cases, need more steps for remaining cases, what build, and what update was done here and what need to be done to reproduce. Please reopen with details and rereport exception with latest builds.
Comment 4 Megachip 2013-03-16 15:27:15 UTC 
(In reply to comment #21)
> do you mean you have 226435 reproducible?
> also, it may be hard to track core dependency and may not be fixed properly
> with "update" from dev and/or to dev build as all possible actions including
> dependency on latest core is done. but there may be some change sin platform
> also.

Sure.. Open an Java file with SQL code inside... but thats seems written some exception reports...
Comment 5 Megachip 2013-03-16 15:50:15 UTC 
sorry, not needed any SQL code inside
Comment 6 Sergey Petrov 2013-03-16 17:44:57 UTC 
please provide update information also, from what to what build (of cause it's matter if from what to latest still fails)
Comment 7 Sergey Petrov 2013-03-20 11:34:20 UTC 
it may matter also if it'z zip distribution and what version and also what distribution (java/jee/full etc.).
please reopen once more with details, yet it still may be to much efforts to fix dev-dev but without details it's hard to decide - fix or won't fix.