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 81608 - Incorrect warning message on EJB Id annotation
Summary: Incorrect warning message on EJB Id annotation
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2006-08-01 15:25 UTC by mcm
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Java class which produces this problem... (2.72 KB, text/plain)
2006-08-02 16:08 UTC, mcm
Details
Netbeans log for session (639.67 KB, text/plain)
2006-08-02 16:08 UTC, mcm
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mcm 2006-08-01 15:25:24 UTC
The following code generates an incorrect yellow-box warning 'Property uses
generated ID, but its type is not an integral type.' in some class files, but is
accepted in others, seemingly at random.

>    private Long mId;
>
>    @Id
>    @Column(name="id")
>    @SequenceGenerator(name="AddressSeqGen", sequenceName="seq_Address_id")
>    @GeneratedValue(strategy=GenerationType.SEQUENCE)
>    public Long getId() {
>        return mId;
>    }
Comment 1 Tomasz Slota 2006-08-02 10:29:43 UTC
Can you please attach complete class examples? It it always reproducible or appears randomly for the 
same class?
Comment 2 mcm 2006-08-02 10:46:34 UTC
The problem is random, and can be cleared by restarting NetBeans. Note that this
isn't just a warning taking a long time to go away. It was never correct and the
accessor / property were always of an integral (Long) type. I can't reliably
reproduce, but will attach an example if / when I can.
Comment 3 Tomasz Slota 2006-08-02 15:21:47 UTC
Have you reproduced it in more than one NB session? A log file would be very helpful.


I'm sorry to bother you with so many questions, but the code for this check is pretty straightforward and 
I'm not able to reproduce this issue even a "theoretic way". It could have been caused by a failure in some 
lower level framework.
Comment 4 mcm 2006-08-02 16:08:19 UTC
Created attachment 32452 [details]
Java class which produces this problem...
Comment 5 mcm 2006-08-02 16:08:57 UTC
Created attachment 32453 [details]
Netbeans log for session
Comment 6 mcm 2006-08-02 16:10:46 UTC
This problem appeared seemingly at 'random' again in a new NetBeans session.
Attached are class file and log file. Hope this helps.
Comment 7 Tomasz Slota 2006-08-03 09:11:02 UTC
The problem is caused by severe inconsistencies in JMI, the type "java.lang.Long" could not be resolved. 
There is a lot of JMI informational exceptions in the log file, reassigning for evaluation.


mcm: try cleaning your NB's user directory
Comment 8 Jan Becicka 2006-10-26 16:26:40 UTC
Javacore module was replaced by Retouche infrastructure. This bug is not valid
in trunk any more.
Comment 9 Quality Engineering 2007-09-20 09:46:06 UTC
Reorganization of java component