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 157170 - "Package xxxxxx does not exist" bullet top of page on jsp source
Summary: "Package xxxxxx does not exist" bullet top of page on jsp source
Status: RESOLVED INCOMPLETE
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker with 1 vote (vote)
Assignee: Tomasz Slota
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-21 01:13 UTC by dougdsa
Modified: 2009-09-08 15:02 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dougdsa 2009-01-21 01:13:46 UTC
I am coding several JSP's in the IDE which use beans. All of the JSP's can see the package.beanclasses exdept for a 
couple of JSP's using a newly coded bean, which resides in the same package as the other beans. When I run the 
project, all of the JSP's work up to the ones trying to access the new bean. The IDE tells me that the package in the 
<jsp:useBean id="beanName" class="package.beanName" scope="session" /> does not exist. I see this message at the top 
of the JSP source when I click on the red bullet. So far, I have tried creating a new package for the bean with the 
same results. I have checked that the JSP page itself is correctly formatted. I have checked the bean and it looks 
like the other ones in the same package, at least the first few common lines. I have even changed the bean to one the 
other JSP's can see, but then the IDE tells me that that package does not exist. Has anyone else had this experience? 
I am new to NetBeans, but not to JAVA.
Comment 1 pslechta 2009-05-14 19:46:51 UTC
Do you still see this problem?
Can you send us the project (or some other sample) that does not work for you? Thanks!
Comment 2 Petr Jiricka 2009-09-08 15:02:34 UTC
I suspect this may happen when the Java bean is not compiled yet. Does compiling it fix the problem? If not, can you
please provide detailed steps to reproduce? Thanks.