stackoom
  简体   繁体   中英

t:saveState does not work anymore after migrating JSF 1.x to JSF 2.x in WebSphere 8

 原文  2013-04-09 13:06:34  5   1    jsf/ migration/ websphere/ tomahawk/ savestate

Question

I have used JSF 1.x with Tomahawk 1.1.9 in my project and I'm now migrating this project to Websphere 8. I have changed the Faces config and web.xml configuration.

All components are working fine except of t:savestate . I am still using Tomahawk 1.1.9.
Is there any issue in using Tomahawk 1.1.9 version in JSF 2.x application?

1 answers

solution1
 0 ACCPTED  2013-04-10 11:21:43

You need to upgrade Tomahawk to a JSF 2.x compatible one.

In their download page , pick the one saying "for JSF 2.0" and not the one saying "for JSF 1.2".

暂无
暂无

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

Related Question JSF - t:saveState x @ConversationScope Migrating JSF 1.1 with Ajax4jsf 1.x to JSF 2 What needs to be change when migrationg from jsf 1.x to jsf 2.x , richafaces 3.x to 4.x java.lang.NullPointerException at org.jboss.seam.pdf.DocumentStorePhaseListener.beforePhase after migrating Seam 2.3.1 project from JSF 1.2 to JSF 2.x validation of multiple fields in jsf 1.x JSF 1.x generic exception handling Bookmarking URL in the JSF 1.x version JSP & EL conflict with JSF 1.x actionListener JSTL xmlns namespace differences between JSF 1.2 and JSF 2.x? Is there any way to use JSF 2.x in JSF1.2 environment
Related Tags
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM