2012-05-17 75 views
1

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

[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一个BridgeFacesContext.class \ COM \ ICESoft公司\面临\上下文。不知道这是不是它找不到的同一类。

我已经尝试了WebSphere的内置JSF罐子的不同版本(看到this后),但没有运气。有谁知道如何配置ICEFaces 1.8.2以使用WAS 8?

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

在此先感谢!

回答

0

我们的WebSphere官方支持如下:

的WebSphere 6,7和8是由我们的ICEfaces对JSF 1.2运行1.8 EE产品支持。
的WebSphere 7和8是由我们的ICEfaces的支持最新的1.8 EE版本是最近加入3.0 EE产品。JSF 2.1

运行的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(推荐)将是必需的行动方案。

+0

感谢您的回应,Deryk。 IceFaces的开源版本是否支持WAS 8? – Hoogles

+0

总的来说,我们的准则是我们不在我们自己的开源产品中提供对非开源服务器的支持。 –

+0

好的,谢谢你Deryk。我只是想知道为什么在开源版本中支持WAS 6和7,而不是在WAS 8中。我知道它只有一年的时间,但对于想升级服务器的人来说,如果ICEfaces 3.0开源版本也支持它,因为支持旧的WAS版本。 – Hoogles

相关问题