Integrate RichFaces component in custom JSF component or extend RichFaces component?

[daniell]

Hi there!

I'm working with RichFaces Version 3.3.0.GA, using many components of the rich library.
Due to special requirements, I need to modify/extend a component respectively to use a RichFaces widged in a custom JSF component (I don't know which way is better to go).

I need a calendar component with separated input fields for date and time. Furthermore, these two fields have to use custom converers since many different inputs are allowed to specify a day or time.
I've successfully created a new JSF component (incl. converters) fulfilling all these requirements - including Ajax support to react on events.
But now, instead of providing only two input fields, I want also add the possibility to select a day with the RichFaces calendar widget. So a basic question is:

• is it possible to use the RichFaces calendar widget inside my custom JSF component in order to fill one of the input fields if the user selects a day in the calendar
  
• is it better to take the RichFaces calendar component and somehow modify it to meet my requirements

Since we already have some other custom JSF-components, I would prefer the first option - the sourcecode would fit perfectly into our source tree.

Many thanks!

[nbelaevski]

Hi,

is it possible to use the RichFaces calendar widget inside my custom JSF component in order to fill one of the input fields if the user selects a day in the calendar

Yes, you can create RF calendar widget programmatically and attach it to your component.

Another widely-used option is creation of Facelets tag that integrates several existing components (see Facelets manual for more). Note: these tags have some limitations that common components don't have.  

is it better to take the RichFaces calendar component and somehow modify it to meet my requirements

I think that is really dependent on how well the first variant (i.e. integration of unchanged widget) will satisfy your requirements. Sure you can take sources and modify them as you need, however consider maintenance effort for your customized version of the widget(s) and various cases like migration to a new RF version.   

[daniell]

Thank you, Nick!

I'll start with the programmatically creation of the calendar. This seems to be the best option for me.

[daniell]

Works perfectly for me - exactly what I was looking for. Thanks again!