E-mail
One of the core adavantages of Pax-Wicket, compared to Wicket itself, is that it's content can be combined from various bundles and various sources. E.g. it's easy to start with developing your application using Spring and then switch to Blueprint bundle by bundle. The mixed samples shows how this can work.
The API
To show how dynamic content can work the mixed samples define an API to retrieve Pages and Components:
Core
To use those providers the main page uses spring to retrieve implementing serivces...
...and Pax-Wicket to inject them into the Homepage.
Finally they can be added quite easily to the homepage:
Implementation
The implementations could be now exported using e.g. blueprint as for the Page Provider or plain java as for the Component Provider. Of course such implementations can be changed as pleased.
What's next
Basically you've just seen how you can use Pax-Wicket to create dynamic content from various sources. You should have learned everything by now you'll need to get quickly into Pax-Wicket. The next step would be to learn the more advanced features of Pax-Wicket jumping into the Extended Quickstart guide.
