• Post Reply Bookmark Topic Watch Topic
  • New Topic

Problems with page layout after migrating to JSF 2.0, RichFaces 4.1.0 Final  RSS feed

Adam Kronicki
Ranch Hand
Posts: 68
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have updated my project to richfaces 4.1.0 and JSF 2.0. I have abviously changed the maven dependencies, updated web.xml, faces-config.xml, swtiched from *.jsp files to *.xhtml files, updated all head,body,form to h:head, h:body, h:form. However, I have significant problems with my page layout and a4j:ajax behavior. I think that it's best if I just list the problems:

-My rich:datatable & rich:calendar skin stopped working. I even tried deleting the columnClass etc. attributes from the tag to leave it with default bluesky skin, but the outcome looks just like a plain html table (no lines, no background, no colors). The same with calendar: when I click on the popup button the calendar is plain transparent text - no background color, nothing. When I click on a date it's changing but the event is not fired.
-the a4j:axjax tag works much worse thatn a4j:support did. For my selectOneMenus I tried event="change" but it doesn't work. Only after adding a valueChangedListener to the tags and tried event="valueChange" it worked.
-Although event="valueChange" worked on selectOneMenu, my a4j:mediaOutput image is not re-rendered. And the chart was the reason why I switched to JSF 2.0 because I needed to use the session-data-helper mechanism to load the images. Is there a special mechanism to rerender (or now 'render' with a4j:ajax) this element when it's using the session-data-helper for loading data?

Moreover I have discovered that apart from my css files the page has only skinning.css file which does not have the classes form calendar & datatable. Shouldn't be more css files with the classes?

Here are the web.xml and index.xhtml files:


here is a list of .jar files deployed with the webapp:

  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!