The JDatePicker suite distribution package comes with the following jar files:
jdatepicker.jar contains the core classes needed to use the components,
jdatepicker-i18n.jar contains translations for other locales than English-based ones,
jdatepicker-beans.jar contains helper classes for UI builders (JBuilder, Netbeans, IntelliJ IDEA),
jdatepicker-binding.jar contains a helper class that allows the date editing components to work with the JGoodies data binding framework,
jdatepicker-jclient.jar contains a helper class that allows the date editing components to work with the Oracle ADF JClient data binding framework,
jdatepicker-dbswing.jar contains helper classes that allow the date editing components to work with JBuilder's dbSwing/DataExpress data binding framework,
jdatepicker-demo.jar contains a demo application that shows the capabilities of the components.
Usually, you will need only jdatepicker.jar for your application. If you intend to use other locales than English-based ones, then you will also need jdatepicker-i18n.jar. We will show later how to localize the components for a locale that does not exist in the jdatepicker-i18n.jar file.
If you want to build your application using a UI builder like those found in JBuilder or Netbeans, then make sure that jdatepicker-beans.jar is registered correctly. The IDE Integration section gives detailed explanations on how to integrate the JDatePicker suite components within an IDE.
If you are using a data binding framework, then:
For JGoodies data binding framework, you also need jdatepicker-binding.jar. Please read this section for more details.
For Oracle ADF JClient data binding framework, you also need jdatepicker-jclient.jar. Please read this section for more details.
For JBuilder's dbSwing/DataExpress data binding framework, you also need jdatepicker-dbswing.jar. Please read this section for more details.