1

我已将我的 WebSphere Application Server 从版本 6.1 升级到 8.0,但我的应用程序不再工作并出现以下错误。它使用 ICEFaces 1.8.2 和 JSF 1.1。它似乎缺少类 BridgeFacesContext2,但之前在 WAS 6.1 中从未遇到过问题。

[5/17/12 16:43:20:552 EDT] 00000026 MainServlet   I com.icesoft.faces.webapp.http.servlet.MainServlet setUpCoreMessageService Blocking Request Handler: "auto-detect"
[5/17/12 16:43:20:802 EDT] 00000026 EnvironmentAd I com.icesoft.faces.webapp.http.servlet.EnvironmentAdaptingServlet <init> Adapting to Thread Blocking environment
[5/17/12 16:43:23:334 EDT] 00000026 MainServlet   W com.icesoft.faces.webapp.http.servlet.MainServlet setUpCoreMessageService Push Server not found - the Push Server must be deployed to support multiple asynchronous applications.
[5/17/12 16:43:23:334 EDT] 00000026 MainServlet   I com.icesoft.faces.webapp.http.servlet.MainServlet setUpCoreMessageService Adapting to Push environment.
[5/17/12 16:43:23:459 EDT] 00000026 AssociatedPag I com.icesoft.faces.webapp.http.portlet.page.AssociatedPageViewsImpl getImplementation using com.icesoft.faces.webapp.http.portlet.page.NoOpAssociatedPageViews
[5/17/12 16:43:23:678 EDT] 00000026 View          E com.icesoft.faces.context.View servePage Problem encountered during View.servePage 
                             java.lang.ClassNotFoundException: org.icefaces.x.context.BridgeFacesContext2
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:132)
at com.icesoft.faces.context.View$2.serve(View.java:68)
at com.icesoft.faces.context.View.servePage(View.java:149)
at com.icesoft.faces.webapp.http.core.MultiViewServer.service(MultiViewServer.java:67)
at com.icesoft.faces.webapp.http.common.ServerProxy.service(ServerProxy.java:11)
at com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet$4.service(MainSessionBoundServlet.java:149)
at com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer.service(PathDispatcherServer.java:24)
at com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:23)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:53)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:23)
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1147)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:722)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:449)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1020)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:1382)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:191)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:648)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1020)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3639)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:950)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1659)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1648)

我正在查看 icefaces.jar 并注意到 icefaces.jar\com\icesoft\faces\context 中有一个 BridgeFacesContext.class。不确定这是否是它找不到的同一类。

我尝试了不同版本的 WebSphere 内置 JSF jars(在看到这个之后),但没有运气。有谁知道如何配置 ICEFaces 1.8.2 以使用 WAS 8?

我需要升级到 ICEFaces 3 吗?如果是,开源版本是否与 WAS 8 兼容?(WAS 8 似乎只列在此处的 EE 版本下)

提前致谢!

4

1 回答 1

0

我们对 WebSphere 的官方支持如下:

我们在 JSF 1.2 上运行的 ICEfaces 1.8 EE 产品支持 WebSphere 6、7 和 8。
我们在 JSF 2.1 上运行的 ICEfaces 3.0 EE 产品支持 WebSphere 7 和 8

最近在最新的 1.8 EE 版本中添加了对 WebSphere 8 的支持:

http://res.icesoft.org/releasenotes/icefacesEE-1.8.2.GA_P04-RN.html#Supported_Platforms

因此,在您的情况下,升级到 ICEfaces EE 1.8 或 ICEfaces EE 3.0(推荐)将是必需的操作过程。

于 2012-05-22T20:22:24.677 回答