Writing non paxrunner based connectors is cumbersome because currently they have to deal with adding url handlers.
A new commons subproject in connector module should provide composits to easily pick functionality a connector wants to add.
the commons project will provide prebuild functionality using qi4j markup.
a connector developer can stack together a new connector using entirely its own implementation (standard java) or re-use prebuild functionality (different url handlers, session handling, configuration support e.g.) using qi4j.
This item covers the implementation of basic functionality currently build into paxrunnerconnector in qi4j semantics. (e.g. a urlhandler is a qi4j concern).
All connectors that are being shipped with paxdrone will use the functionality if appropriate.
Complete rewrite of Pax Drone (Pax Exam)