Peter, Eung-ju,

>>one of the joys of commons. People who don't work on the code get voting
>>rights. Fun - aint it?
>>

Oh blimey it is worse that I thought.  I think I should brace for a "no" 
vote.

>>>What we don't know at this stage (making the massive assumption that
>>>Peter, Berin et al are as keen as I am) is how much we use ARMI.  We
>>>could easily create a Cornerstone block that is geared towards the two
>>>remote publications impls (sockets and RMI).  We could also, as outlined
>>>above, allow Phoenix to directly (under configuration) use ARMI to allow
>>>one block to <depend> on a service of others irrespective of the
>>>location of that service.  It could nearly seamlessly mesh into the
>>>current org.apache.avalon.framework.component.ComponentManager API.
>>>
>>I don't think it is time to put it inside the Phoenix "kernel" just yet
>>
>and
>
>>have not yet reached a stable point in ClassLoader etc arrangement. 
>>

I would be inclined to agree.

>>If you
>>want to have an exporter Block then great ;) 
>>

Yes I think that is first - a Cornerstone exporter/publisher

>>It would also be possible to
>>
>add
>
>>a BlockListener that automagiocally published different Blocks into the
>>
>ARMI
>
>>exporter.
>>

This sounds good.  I nead to learn a little about when/why one would use 
a BlockListener I guess.

>
>How about below configuration? But Paul have better idea than me. :-)
>
>-- assembly.xml
>
><block-listener
>class="org.apache.avalon.cornerstone.listeners.armi.ArmiPublisher"
>name="armi">
>    ...
>    ...
></block-listner>
>
><block class="org.apache.avalon.foo.blocks.Bar" name="barbar">
>    ...
></block>
>
>-- config.xml
><armi>
>    <publish name="Bar">
>        <block>barbar</block>
>        <interface>org.apache.avalon.foo.services.Bar1</interface>
>        <interface>org.apache.avalon.foo.services.Bar2</interface>
>    </publish>
>    <publish name="X1">
>        ...
>    </publish>
></armi>
>

One problem is that the ARMI equivalent of RMI syubs need to exist.  I 
planned a BCEL dynamic generator, but am completely stuck (as ever) with 
how to do it in BCEL.
I like the look of this though.

>>I don't have time to play atm but it sounds neat.
>>

Thanks dudes.

Regards,

- Paul H


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to