This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 222734 - NPE in EJBValidator
Summary: NPE in EJBValidator
Status: CLOSED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: jst.j2ee CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-14 07:37 EDT by Kaloyan Raev CLA
Modified: 2008-05-08 13:37 EDT (History)
1 user (show)

See Also:

Attachments
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 Kaloyan Raev CLA 2008-03-14 07:37:51 EDT 
Build: I20080313204547

Steps to reproduce:
1. Create an EJB 2.1 project with XDoclet support.
2. Create a XDoclet Session Bean.

2-3 NPEs are logged in the Error Log.


java.lang.NullPointerException
	at org.eclipse.jem.java.internal.impl.JavaClassImpl.isExistingType(JavaClassImpl.java:953)
	at org.eclipse.jst.j2ee.model.internal.validation.EJBValidator.getJavaClass(EJBValidator.java:428)
	at org.eclipse.jst.j2ee.model.internal.validation.EJBValidator.fullValidate(EJBValidator.java:406)
	at org.eclipse.jst.j2ee.model.internal.validation.EJBValidator.commonValidate(EJBValidator.java:80)
	at org.eclipse.jst.j2ee.model.internal.validation.EJBValidator.validateInJob(EJBValidator.java:104)
	at org.eclipse.jst.j2ee.internal.ejb.workbench.validation.UIEjbValidator.validateInJob(UIEjbValidator.java:52)
	at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Comment 1 Carl Anderson CLA 2008-04-04 18:54:53 EDT 
I can't reproduce this.  It looks a lot like what Chuck fixed with a recent change to ResourceSetWorkbenchEditSynchronizer.  So I am resolving this as fixed.  If you can reproduce it, please reopen.
Comment 2 Kaloyan Raev CLA 2008-05-08 13:37:11 EDT 
I was not be able to reproduce this error with the latest drivers.