Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Import cannot be resolved

154 views
Skip to first unread message

hamis...@oddpost.com

unread,
May 29, 2007, 6:51:17 AM5/29/07
to
Hi

I am trying to deploy a WAR that worked previously under 5.1, when I deploy under WAS 6.1.0.7, I get an "Import cannot be resolved error":

com.ibm.ws.jsp.JspCoreException: JSPG0049E: /index.jsp failed to compile :
JSPG0091E: An error occurred at line: 7 in the file: /index.jsp
JSPG0093E: Generated servlet error from file: /index.jsp
C:\Program Files\IBM\WebSphere6.1\AppServer1\profiles\AppSrv01\temp\HBNode01\server1\mpos_war\mpos.war\_index.java : 11 : The import com.xiam.content.servlet.login cannot be resolved
JSPG0091E: An error occurred at line: 39 in the file: /index.jsp
JSPG0093E: Generated servlet error from file: /index.jsp
C:\Program Files\IBM\WebSphere6.1\AppServer1\profiles\AppSrv01\temp\HBNode01\server1\mpos_war\mpos.war\_index.java : 288 : LoginForm cannot be resolved to a type
JSPG0091E: An error occurred at line: 39 in the file: /index.jsp
JSPG0093E: Generated servlet error from file: /index.jsp
C:\Program Files\IBM\WebSphere6.1\AppServer1\profiles\AppSrv01\temp\HBNode01\server1\mpos_war\mpos.war\_index.java : 289 : LoginForm cannot be resolved to a type
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.translateJsp(AbstractJSPExtensionServletWrapper.java:380)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper._checkForTranslation(AbstractJSPExtensionServletWrapper.java:345)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.checkForTranslation(AbstractJSPExtensionServletWrapper.java:254)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:136)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.handleRequest(AbstractJSPExtensionProcessor.java:275)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:308)
at com.ibm.ws.webcontainer.servlet.FilterProxyServlet.dispatch(FilterProxyServlet.java:73)
at com.ibm.ws.webcontainer.servlet.FilterProxyServlet.service(FilterProxyServlet.java:52)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.xiam.servlet.UTF8EncodingFilter.doFilter(UTF8EncodingFilter.java:52)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:761)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:673)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:688)
at com.ibm.ws.wswebcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:96)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.invokeFilters(DefaultExtensionProcessor.java:652)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:472)
at com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:113)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3168)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:254)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:96)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:394)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213)
at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:741)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)


Although the error states "The import com.xiam.content.servlet.login cannot be resolved", my problem is the actaul import line in the jsp is

<%@ page import="com.xiam.content.servlet.login.forms.LoginForm" %>

as you can see WAS is truncating the import. This is one of many imports on the jsp, all the rest are resolved correctly.

Anyone any ideas what might be going wrong?

Thanks in advance

Sven Vermeulen

unread,
May 29, 2007, 9:05:12 AM5/29/07
to
On May 29, 12:51 pm, <hamishbr...@oddpost.com> wrote:
> C:\Program Files\IBM\WebSphere6.1\AppServer1\profiles\AppSrv01\temp\HBNode01\server1\mpos_war\mpos.war\_index.java : 289 : LoginForm cannot be resolved to a type
[...]

> Although the error states "The import com.xiam.content.servlet.login cannot be resolved", my problem is the actaul import line in the jsp is
>
> <%@ page import="com.xiam.content.servlet.login.forms.LoginForm" %>
[...]

> Anyone any ideas what might be going wrong?

Perhaps WebSphere v5 has a package in one of its core jars you use in
the application whereas the WebSphere v6 doesn't have this package
anymore, or your application is not correctly deployed on the
WebSphere v6 environment.

Find out what jar file you need and add it to your classpath.

The truncation WebSphere performs might be because it cannot find the
package declaration itself (so it doesn't need to search for the class
further).

Wkr,
Sven Vermeulen

0 new messages