Hello,
I want to provide an easy way, for users (developpers), to
extend GUI modules (CRUD tapestry pages/components). So we give them a
"generic" module (a component library) that they can extend/override.
The constraint is that we don't want to use url rewriting. So,
we use the same alias for both mappings (generic and extended modules) and the
users have to use the same name for their extended pages and components as the
generic ones.
The ideal would be to have an ordered list for libraries
mapping (I know that the method contributeComponentClassResolver uses an
unordered list)
Any idea to handle libraries mapping order ?
Nourredine.