You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hivemind.apache.org by Alexander Fishchuk <al...@ulti.kiev.ua> on 2006/03/14 11:22:20 UTC

Extending (overriding) configuration-point. Is it possible?

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 


Re: Extending (overriding) configuration-point. Is it possible?

Posted by Ben Gidley <be...@gidley.co.uk>.
You can add extra items into to a configuration point - but you can't remove
items from it.

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

On 3/14/06, Alexander Fishchuk <al...@ulti.kiev.ua> wrote:
>
>  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
>