Configuring RichFaces to use a meaningful custom skin is easy. A person only needs to define a skin that can be used in web.xml:

org.richfaces.SKIN Ruby

It is sometimes considered desirable to change hide at runtime. Users may even want to register a specific skin with their unique ustriplets. Here’s how.

First, we’ll hard-code the wrapper we recognize and set it to EL:

org.richfaces.SKIN # skinBean.skin

SkinBean is a special name for the JSF Manged Bean, reminiscent of the following:

Public class SkinBean special chain leather; public string getSkin ()Back of the skin; public void setSkin (chain skin)this.skin is equal to skin;

Register in JSF file:

SkinBean configuration Demo SkinBean Meet leather Ruby

We want to initialize how the Skin property is initialized with a value. We also put beans in the training area. It wouldn’t make sense to put beans in the demand area because the skin type is shedding with every request. We want the user to be able to select skins and apply them to every session.

Test it quickly, you can use the following page:

sameTabs change color…

The tab is only intended to show how the look is updated. Place almost all other RichFaces UI components in the Mark pageetplace to see how the look will be updated.

Result:

If you would like to learn how to create your own skins, check out this blog post. Learn More

richfaces change skin at runtime

One action you can try is skinning the standard controls, in our example this would be h: selectOneListbox:

org.richfaces.CONTROL_SKINNING Activate

Learn more about the skinning standard.