Issue Details (XML | Word | Printable)

Key: GLASSFISH-11208
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Sanjeeb Sahoo
Reporter: sebglon
Votes: 3
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
glassfish

JSP compiler Erro whit OSGI imported class

Created: 29/Nov/09 12:21 PM   Updated: 18/Oct/13 11:37 AM
Component/s: OSGi-JavaEE
Affects Version/s: V3
Fix Version/s: not determined

Time Tracking:
Not Specified

Environment:

Operating System: All
Platform: All


Issuezilla Id: 11,208
Status Whiteboard:

v3_exclude

Tags: 3_1-exclude
Participants: ejroberts, kumara, ruans, Sanjeeb Sahoo, sebglon and Tom Mueller


 Description  « Hide

have 2 bundle:
Bundla A --> a WAB bundle with a JSP pages
and
Bundle B --> that export class with static fields

The JSP pages (in Bundle A) use the exported class (in Bundle B)
When I want to see my page, i have compilation
error "org.apache.jasper.JasperException: PWC6033: Error in Javac compilation
for JSP"

Current GlassFish JSP compiler can't
see classes imported from another WAB. This is because it expects all
the dependencies to be specified in a classpath which it can pass onto
the javac. I have always felt, JSP compiler should use a classloader
backed JavaFileManager.

Forum Thread
http://forums.java.net/jive/thread.jspa?messageID=373634



sebglon added a comment - 30/Nov/09 12:18 AM
      • Issue 11208 has been confirmed by votes. ***

kumara added a comment - 30/Nov/09 11:57 AM

This is an extensive change and too risky for the v3 release targeted for next week. It will be addressed in
the next release.


Sanjeeb Sahoo added a comment - 12/Oct/10 07:50 AM

Unfortunately, because of time constraints, we have to exclude this from 3.1 rel.


ruans added a comment - 27/Jan/12 02:17 PM - edited

Is there any fix for this in 3.* I've tried 3.1.2 build 26-01-2012 and the problem persists. I am forced to run my sites in karaf with pax and jetty at the moment. Much rather be using glassfish.

org.apache.jasper.JasperException: PWC6033: Error in Javac compilation for JSP

PWC6199: Generated servlet error:
string:///index_jsp.java:9: package com.net1.core.commons.web does not exist

PWC6199: Generated servlet error:
string:///index_jsp.java:10: package com.net1.core.commons.web.tag does not exist

PWC6199: Generated servlet error:
string:///index_jsp.java:11: package com.net1.core.commons.web.util does not exist

at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:129)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:299)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:392)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:453)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:625)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:377)


Tom Mueller added a comment - 06/Mar/12 09:56 PM

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.


Sanjeeb Sahoo added a comment - 30/Sep/13 12:26 PM

This issue is difficult to fix until JSP compiler allows us to use class loaders to be used for searching classes. So deferring it for now. Recommended work around is to use offline JSP compiler to precompile JSPs and package them in the WAB.


ejroberts added a comment - 18/Oct/13 11:36 AM - edited

One workaround is to push the use of the OSGi provided classes out of the JSP pages and into a local class available from within the WAB.

I have found that this manages to defer the class loading until such a point where it is then the compiled Servlet class that loads the OSGi provided classes.