You are viewing a plain text version of this content. The canonical link for it is here.
Posted to phoenix-dev@avalon.apache.org by Andrei Ivanov <my...@surfeu.fi> on 2002/06/12 23:58:12 UTC
block version usage
Hi,
Where I can find example of how to use correctly version of Phoenix block
and version attribute of service.
Suppose I have two blocks of different versions and some services which have
different versions but same contract. How I can manipulate those in Phoenix
xinfo / assembly?
Andrei
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: block version usage
Posted by Peter Donald <pe...@apache.org>.
At 12:58 AM 6/13/2002 +0300, you wrote:
>Hi,
>Where I can find example of how to use correctly version of Phoenix block
>and version attribute of service.
>Suppose I have two blocks of different versions and some services which have
>different versions but same contract. How I can manipulate those in Phoenix
>xinfo / assembly?
The version of the service is part of its contract. Only change the version
number of service when you cahnge the interface of the service. So if you
add a new method then you must bump the service version number (and also
version attribute in <service/> in any <dependency/> for blocks that use
service).
Block version is completely unused in kernel at this stage. It is intended
to help assemblers know which version of block/implementation they are uing
when doing assembly.
>Andrei
>
>
>
>--
>To unsubscribe,
>e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail:
><ma...@jakarta.apache.org>
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
- John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>