Quoting Torsten Curdt <[EMAIL PROTECTED]>:
> I'm trying to uses more and more of the Avalon interfaces
> for a better C2 integration. I have a taglib that creates
> instances of beans/classes:
>
> taglib:
> ...
> st.dff.test b = new st.dff.test();
> ...
>
> Now I'd like to replace this with the Component pattern
> from Avalon so the Components are accessible from within
> the beans/classes:
>
> taglib:
> ...
> st.dff.test b = (st.dff.test) manager.lookup("st.dff.test");
> ...
>
> But as far as I understand this would require for every
> bean/class a unique entry in the cocoon.roles. Is this right?
>
> And what happens when parameters are need for the constructor?
>
> taglib:
> ...
> s.dff.test b = (st.dff.test) new
> st.dff.test("parameter1","parameter2");
> ...
>
> How is handle with the Component approach?!
Best advice I can give you is "go read the Avalon docs" :)
Giacomo
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
