The ICEfaces Enterprise Component Library provides an enhanced set of custom ICEfaces components. These components offer the following:

  • Over 30 New Components to further enrich your ICEfaces application!
  • Simplified components and classes to smooth ICEfaces development
  • Extra features and functionality not found in the standard ICEfaces component suite
  • Best-practice engineered components and JSF bean integration geared for enterprise deployments
ICEfaces Enterprise Components are included in ICEfaces EE. Learn more about the ICEfaces Enterprise Components.

About Enterprise Components:

Enterprise components are composite components created with Facelets technology. Facelets wires together components to build a component tree on the server. This allows for code reuse because with Facelets, you can turn any collection of page markup into a UI component to be inserted into the component tree.

A composite component can be considered a a special type of template that acts as a component. A template does not define content, but provides placeholders for content and the layout, orientation, flow, structure, and logical organization of elements on the page. We can think of a template as a document with "blanks" that will be filled in with real data and user interface controls at request time.

ICEfaces composite components will typically have an attribute 'bean' that will provide content - other attributes are used to configure the component. The composite component jar contains .xhtml markup, bean code, a faces-config.xml file and resources such as stylesheets, images and javascript files. The sophistication of the various components range from simple .xhtml markup to a code base developed over hundreds of hours by the ICEsoft professional services team. If a composite component does not suit your particular use case, the 'template' can be modified or enhanced.

Remember, Facelets and JSP are mutually exclusive, so if you are using the composite component jar, you will be working with Facelets as your page definition language (PDL), not JSP.