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 75306 - Adding @Resource annotation causes string of exceptions...
Summary: Adding @Resource annotation causes string of exceptions...
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: Sun All
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
: 73936 (view as bug list)
Depends on:
Blocks: 73679
  Show dependency tree
 
Reported: 2006-04-20 20:52 UTC by _ pcw
Modified: 2007-09-26 09:14 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
stack trace (29.78 KB, text/plain)
2006-04-20 20:53 UTC, _ pcw 		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 _ pcw 2006-04-20 20:52:35 UTC 
Start the IDE w/ console window.
Create new Web application (JavaEE5)
Create new Servlet
In the NewServlet.java edit window, go to just inside class declaration, e.g. 
    public class NewServlet extends HttpServlet {
        // go to here
and start typing "@Res" and use code completion to complete the annotation to
@Resource (e.g. type "@Res<ctrl-space><select @Resource from list and hit enter>")

At this point, the attached long string of exceptions was sent to the console
window.
Comment 1 _ pcw 2006-04-20 20:53:34 UTC 
Created attachment 29963 [details]
stack trace
Comment 2 Jiri Kovalsky 2006-04-21 06:30:08 UTC 
Why do you think this is P2 ? It does not impact users and won't be visible in
FCS as all of the exceptions are INFORMATIONAL.
Comment 3 Marek Fukala 2006-04-21 09:53:20 UTC 
Does the exceptions harm you Petre? Isn't the model then properly updated? If
yes, please upgrade priority. As Jirka pointed out the exceptions are only
informational. I see many of these in many situations working with EJB, WP, WS
and  CAR... IMHO they needs to be fixed or suppressed in MDR code. I am CCing
Daniel Prusa and Honza Becicka who are responsible for MDR maintaining and
kindly asking for their opinions to why the exc. occures and whether they can be
fixed.
Comment 4 Jan Becicka 2006-04-21 11:42:01 UTC 
Is it reproducible or just random?
Comment 5 _ pcw 2006-04-21 14:02:57 UTC 
1) It is reproducible, somewhere between being the first action on a freshly
opened file and everytime that sequence is typed in a scenario where the field
it applies to has not been entered yet.

2) It does not seem to cause any harm, so P3 is fine.

However, whether marked informational or not, if code is throwing
RuntimeException or IllegalStateException and feels it's unexpected enough to
print it out, that suggests to me there is a programmer bug there somewhere and
a trace this long from just one action easily obscures real problems even when
itself is not necessarily one, or not that important.
Comment 6 Jan Becicka 2006-04-24 14:31:22 UTC 
Fixed in trunk and release55

Checking in AnnotationImpl.java;
/cvs/java/javacore/src/org/netbeans/modules/javacore/jmiimpl/javamodel/AnnotationImpl.java,v
 <--  AnnotationImpl.java
new revision: 1.31; previous revision: 1.30
done

Checking in AnnotationImpl.java;
/cvs/java/javacore/src/org/netbeans/modules/javacore/jmiimpl/javamodel/AnnotationImpl.java,v
 <--  AnnotationImpl.java
new revision: 1.19.4.5.2.2; previous revision: 1.19.4.5.2.1
done
Comment 7 Jan Becicka 2006-05-04 14:38:39 UTC 
*** Issue 73936 has been marked as a duplicate of this issue. ***
Comment 8 Quality Engineering 2007-09-20 11:58:35 UTC 
Reorganization of java component