You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Stephan Michels <st...@apache.org> on 2003/03/21 10:12:20 UTC
ExcaliburCompoenentSelector and component-instance
Hi,
I would love to use a syntax like
<conditions>
<condition name="cond1" value="i<5"/>
<condition name="cond2" class="org.domain.FileChanged"/>
</conditions>
with the ExcaliburCompoenentSelector.
<role name="org.domain.ConditionSelector"
shorthand="conditions"
default-class="org.apache.avalon.excalibur.component.ExcaliburComponentSelector">
<hint shorthand="condition" class="org.domain.ExpressionCondition"/>
</role>
But the ECS only allows 'component-instance' with a class attribute
or a defined element name and using the class specified the
the hint role. It is perhaps possible to change the implementation
to use the class attribute in other elements than
'component-instance'?
I attached a patch file for the ECS.
Thank you, Stephan Michels.
_______________________________________________________________________
Stephan Michels EMail: stephan@apache.org
ICQ: 115535699 Tel: +49-030-314-21583
----+----|----+----|----+----|----+----|----+----|----+----|----+----|-|
Re: ExcaliburCompoenentSelector and component-instance
Posted by Stephan Michels <st...@apache.org>.
On Fri, 21 Mar 2003, Sylvain Wallez wrote:
> Stephan Michels wrote:
>
> >Hi,
> >
> >I would love to use a syntax like
> >
> > <conditions>
> > <condition name="cond1" value="i<5"/>
> > <condition name="cond2" class="org.domain.FileChanged"/>
> > </conditions>
> >
> >with the ExcaliburCompoenentSelector.
> >
> > <role name="org.domain.ConditionSelector"
> > shorthand="conditions"
> > default-class="org.apache.avalon.excalibur.component.ExcaliburComponentSelector">
> > <hint shorthand="condition" class="org.domain.ExpressionCondition"/>
> > </role>
> >
> >But the ECS only allows 'component-instance' with a class attribute
> >or a defined element name and using the class specified the
> >the hint role. It is perhaps possible to change the implementation
> >to use the class attribute in other elements than
> >'component-instance'?
> >
> >I attached a patch file for the ECS.
> >
>
> You should also look at Cocoon's ExtendedComponentSelector which allows
> this kind of features
I know the cocoon selector, but I don't want to write an own selector. But
perhaps I must :-/
Stephan.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: ExcaliburCompoenentSelector and component-instance
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Stephan Michels wrote:
>Hi,
>
>I would love to use a syntax like
>
> <conditions>
> <condition name="cond1" value="i<5"/>
> <condition name="cond2" class="org.domain.FileChanged"/>
> </conditions>
>
>with the ExcaliburCompoenentSelector.
>
> <role name="org.domain.ConditionSelector"
> shorthand="conditions"
> default-class="org.apache.avalon.excalibur.component.ExcaliburComponentSelector">
> <hint shorthand="condition" class="org.domain.ExpressionCondition"/>
> </role>
>
>But the ECS only allows 'component-instance' with a class attribute
>or a defined element name and using the class specified the
>the hint role. It is perhaps possible to change the implementation
>to use the class attribute in other elements than
>'component-instance'?
>
>I attached a patch file for the ECS.
>
You should also look at Cocoon's ExtendedComponentSelector which allows
this kind of features
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org