Null pointer access: The variable out can only be null at this location

[nandy desikan]

Hi,

I am deploying a web application in tomcat 4.1 in eclipse galileo.
I dont get any compilation errors. But when I run the jsp on the server, I get this error.

C:\Workspace_Sriram_WorkPlaceWorkFlowOne_12_April_2010\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\work\Standalone\localhost\SsoDigitalCertApps\WorkPlaceRelizon_jsp.java:8: package com.eaton.portal.workPlaceRelizon does not exist
import com.eaton.portal.workPlaceRelizon.*;
^
1 error

The page imports in the jsp are correctly defined as below:

<%@ page import="com.eaton.portal.common.util.*"%>
<%@ page import="com.eaton.portal.common.business.*"%>
<%@ page import="com.eaton.portal.webmd.business.*"%>

So I set the Project-->Validation--> JSP syntax--> Java --> Null Pointer access to "Error".

In all my jsps just before the page imports I get this message:

Null pointer access: The variable out can only be null at this location

Please help!!!

Regards,
Sriram

[Jan Cumps]

I have moved this thread to our "IDEs, Version Control and other tools " forum.
Part of it is related to IDE config, part to Tomcat deployment.

[saurav sarkar]

It does seem that the server classpath needs to have the particular class in it.

[nandy desikan]

It is finally solved!!

For Tomcat 4.1.* versions, guess we may have to define the page imports specifically, not generically with reference to a package.
For eg,

<% @page import = "abcd.ayz.123" %>

I was getting a run time error when I declared imports as

<% @page import = "abcd.ayz.*" %>

Dont know what is the architecture difference between tomcat 4.* and tomcat 6.* to cause the above issue.
Technical advice is most welcome.

Regards,
NandyDesikan