The way round this is to provide an alternative implementation tag for the service you want to change configuration on. On the implementation tag add your own configuration point instead of the standard one.
Thanks
Ben
Hi guys,
I need to override (extend) the schema definition for configuration point.
It would allow me to replace one of the classes used in <conversion …> element with my own implementation (subclass).
Is it possible to override the configuration-point schema?
If not possible, is there a way to provide my own implementation for one of the classes used in <conversion …> element?
For reference:
The real-world problem is as follows
Tapestry 4 Portlet library has PortletPageResolver service which uses PageResolverContribution class in configuration point.
I need to extend PageResolverContribution to allow not only direct matching (find the page based on given mimeType, portletModen and windowState),
but also REVERSE MATCHING (find mimeType, portletModen and windowState based on the page) .
thanks
