[jbosscommunity13]

As time goes by...

We migrated successful to rich faces 4, many challenges but found solutions... We implemented an jsf2 spacer

Talking about semantic markup principals in context of sortable rich faces tables. I d like to repeat my question from September 2011

<rich:table... columns="3"

<h:outputText ...

<rich:spacer...

<h:inputText...

What should be used for empty cells in tables?

[rngarnaik]

I am agree with you guys worked hard to improve a lot but same time you should have to have a plan for backward compartibility.

I found many things not working while migrating my old app to new version of richfaces. so finally I am planning to re-write the whole app completely ( I am ready to re-write as my changes are more in functional end).

My kind suggestion please have the back compartibility moving forward with new release of Richfaces.

[peterfry]

This usecase is exactly why I will have to implement a jsf2 spacer!

Regarding backwards compatibility:

How about a 'deprecated' tags library i.e. put all the tags that will be a real pain for people to migrate away from into this. Most would be more than happy with a position where they simply have to add another library!

[ls.santhosh]

Hi Ilya,

The composite component approach fixes rich spacer issue in my application where all we used "<rich:spacer>" tag in .xhtml pages. But, we are facing one more scenario where we have custom component and inside the custom component we are using HtmlSpacer like below.

HtmlSpacer spacer = new HtmlSpacer();
spacer.setWidth("20");

We don't know how to replace this. What is an appropriate solution for this? Thanks in advance.

Thanks,

Santhosh