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 173028 - AssertionError: null TypeElement for "pkgname.DiscountCode"
Summary: AssertionError: null TypeElement for "pkgname.DiscountCode"
Status: RESOLVED INVALID
Alias: None
Product: javaee
Classification: Unclassified
Component: Persistence (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Sergey Petrov
URL: http://statistics.netbeans.org/except...
Keywords: RANDOM
: 184337 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-09-24 14:44 UTC by Petr Jiricka
Modified: 2012-04-20 08:02 UTC (History)
6 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 159093


Attachments
stacktrace (2.38 KB, text/plain)
2009-09-24 14:45 UTC, Petr Jiricka
Details
stacktrace (2.30 KB, text/plain)
2010-01-12 06:21 UTC, Petr Jiricka
Details
stacktrace (3.17 KB, text/plain)
2010-05-11 10:22 UTC, mpapamichael
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2009-09-24 14:44:55 UTC
Build: NetBeans IDE Dev (Build web-main-1675-on-090924)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.1-b02-92, Java(TM) SE Runtime Environment, 1.6.0_15-b03-226
OS: Mac OS X, 10.5.8, x86_64

User Comments:
pjiricka: Entity from DB wizard.



Stacktrace: 
java.lang.AssertionError: null TypeElement for "prdel.DiscountCode"
        at org.netbeans.modules.j2ee.persistence.wizard.fromdb.JavaPersistenceGenerator$Generator$EntityClassGenerator.generateRelationship(JavaPersistenceGenerator.java:931)
        at org.netbeans.modules.j2ee.persistence.wizard.fromdb.JavaPersistenceGenerator$Generator$ClassGenerator.run(JavaPersistenceGenerator.java:676)
        at org.netbeans.modules.j2ee.persistence.wizard.fromdb.JavaPersistenceGenerator$Generator$1.run(JavaPersistenceGenerator.java:441)
        at org.netbeans.modules.j2ee.persistence.wizard.fromdb.JavaPersistenceGenerator$Generator$1.run(JavaPersistenceGenerator.java:437)
        at org.netbeans.api.java.source.JavaSource$1.run(JavaSource.java:653)
        at org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:129)
Comment 1 Petr Jiricka 2009-09-24 14:45:00 UTC
Created attachment 88292 [details]
stacktrace
Comment 2 Petr Jiricka 2009-09-24 14:58:16 UTC
This only happened to me once -> RANDOM.
Comment 3 Sergey Petrov 2009-10-26 17:03:32 UTC
see issue 152634, it's first time the issue happened in 6.8, still have no ideas how to reproduce if it's still
reproducible.
Comment 4 Petr Jiricka 2010-01-12 06:21:27 UTC
Created attachment 93216 [details]
stacktrace

Generating entities from database.
Comment 5 Sergey Petrov 2010-01-26 07:32:20 UTC
issue #177341 may contain some details for evaluation
Comment 6 Sergey Petrov 2010-02-02 07:00:35 UTC
just tried with fixed sql from issue #177341  and still have no assertion, but will look at the issue  as I see it as important one and I have some ideas on reasons.
Comment 7 Sergey Petrov 2010-02-03 06:24:15 UTC
I though I was able to reproduce the issue somehow before but can't any more, will try again a bit later
Comment 8 Exceptions Reporter 2010-04-10 13:21:15 UTC
This bug already has 5 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=159093
Comment 9 Sergey Petrov 2010-04-19 13:06:15 UTC
*** Bug 184337 has been marked as a duplicate of this bug. ***
Comment 10 Sergey Petrov 2010-04-22 13:39:09 UTC
JPAGenTest::testGenerateRelatedEntitiesFromSampleSchema unit test generate the same fail.
Comment 11 mpapamichael 2010-05-11 10:22:21 UTC
Created attachment 98750 [details]
stacktrace

updating entities using persistence
Comment 12 Exceptions Reporter 2011-01-22 12:30:30 UTC
This bug already has 10 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=159093
Comment 13 Sergey Petrov 2011-10-18 15:19:04 UTC
7.0 beta is latest build with the report so far, need to wait and may be it's not reproducible in 7.0-7.1 any more.
Comment 14 Sergey Petrov 2012-04-20 08:02:42 UTC
latest report is from 110110 build, suppose the issue isn't valid any more or fixed