|
PAX-WICKET is an OSGi-based extension to the Apache Wicket framework allowing to run Wicket applications in bundles easily on OSGi platforms. Whereas a typical Wicket application requires that all component wiring be done at compile time, this extension allows you to model the Wicket application, and move those model parts around and not be resolved until request time. You can add and remove parts of the Wicket application without restarting the application, simply by loading and unloading OSGi bundles. In a nutshell PAX-WICKET tries to solve the following problem statement:
For this goal PAX-WICKET provides the following features:
Based on those features PAX-WICKET allows the following runtime system: Interested? Jump into the Quickstart guide to find out how to use PAX-WICKET. If you still have some questions try the FAQ and the full Documentation or simply join the PAX-WICKET community at the ops4j mailing-lists or irc channel. Is PAX-WICKET already finished? Although the core of pax-wicket is quite old and stable the framework is still in heavy development. While PAX-WICKET has already a wide range of features there is still a lot of work to do and available :) Feel free to take a look at the Issue Tracker or simply jump into the mailing-lists or irc channel. -Enjoy The PAX-Wicket Team |
Download Current Work Quick Links: |
Latest NewsThe 1.0.0 release is the first release with Wicket 5 (aka 1.5.x) support. It contains 5 bug-fixes identified during the 0.8.x line and some small improvements. Besides the Wicket upgrade the 1.0.0 release also contains a Pax Exam (2.4.0) and Pax Logging (1.6.5) upgrade. A small feature had been added to the test framework to workaround some of the harder validation rules of Wicket 5. Besides of that the only things which require an upgrade are related to the Wicket changes between Wicket 4 (aka 1.4.x) and Wicket 5 and not between Pax Wicket 0.8.x and 1.0.0. For the full changelog see Pax Wicket - 1.0.0. The 0.8.4 release of pax-wicket fixes one really nasty class-loading bug which could occur at rare situations during serialization restoring at various places in the code. For the full changelog see Pax Wicket - 0.8.4. The 0.7.8 release of pax-wicket fixes one really nasty class-loading bug which could occur at rare situations during serialization restoring at various places in the code. For the full changelog see Pax Wicket - 0.7.8. |

