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 Howard Henson <hh...@aosl.co.za> on 2002/11/20 12:43:09 UTC
Ability to hide assembly file complexity -
I have been working with Phoenix for a short while now and am trying to
generically access services I have created without having to pre-configure
every possible dependency.
If there a way to rather be able to access a service registry where the
service could be found dynamically and accessed dynamically?
Also it seems like the assembly file and the @phoenix comments seem to be a
duplication of effort. What was the thinking behind this?
If you left the @phoenix comments in place would it not make sense to
simplify the assembly file to only bind the role to implementation and not
have to specify the dependencies since they are already specified in the
@phoenix comments?
Along the same lines it does not seem sensible to not be able to use
components in a self contained fashion, currently if I want to use a
component I need to define the component and all components that the
component relies on, etc. and then only can I define my component that makes
use of the other component. If there were some way to define a standard use
of a component with all the information that would exist in the assembly
file for that component in a seperate file that can be included (like in a C
#include) to facilitate simplier re-use.
Regards
Howard Henson
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ability to hide assembly file complexity -
Posted by Greg Steuck <gr...@nest.cx>.
>>>>> "Mateusz" == Mateusz Szczap <ma...@ncdc.pl> writes:
>> KISS? You could use a separate tool to pre-generate tentative
>> assembly.xml from all components you want to include into your
>> system. This is in my opinion the best compromise between run
>> time simplicity and convenience. My experience with Phoenix so
>> far didn't show that assembly file creation is such a difficult
>> undertaking.
Mateusz> For larger projects this could be annnoying and sometimes
Mateusz> leds to mistypings and errors. On the other hand not
Mateusz> everybody want to use phoenix-metagenerate....
Whatever way you slice it, a separate assembly generation tool
taking .xinfo as input and producing assemly.xml on output will
do it. As long as static assembly is possible, of course.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ability to hide assembly file complexity -
Posted by Mateusz Szczap <ma...@ncdc.pl>.
> KISS? You could use a separate tool to pre-generate tentative
> assembly.xml from all components you want to include into your
> system. This is in my opinion the best compromise between run time
> simplicity and convenience. My experience with Phoenix so far didn't
> show that assembly file creation is such a difficult undertaking.
For larger projects this could be annnoying and sometimes leds to mistypings
and errors. On the other hand not everybody want to use
phoenix-metagenerate....
Mateusz Szczap
mati@ncdc.pl
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ability to hide assembly file complexity -
Posted by Greg Steuck <gr...@nest.cx>.
>>>>> "Howard" == Howard Henson <hh...@aosl.co.za> writes:
Howard> If there a way to rather be able to access a service
Howard> registry where the service could be found dynamically and
Howard> accessed dynamically?
You are talking about auto-assembly here. AFAIK Phoenix doesn't do this
(yet?).
Howard> Also it seems like the assembly file and the @phoenix
Howard> comments seem to be a duplication of effort. What was the
Howard> thinking behind this?
KISS? You could use a separate tool to pre-generate tentative
assembly.xml from all components you want to include into your
system. This is in my opinion the best compromise between run time
simplicity and convenience. My experience with Phoenix so far didn't
show that assembly file creation is such a difficult undertaking.
Howard> Along the same lines it does not seem sensible to not be
Howard> able to use components in a self contained fashion,
Howard> currently if I want to use a component I need to define the
Howard> component and all components that the component relies on,
Howard> etc. and then only can I define my component that makes use
Howard> of the other component. If there were some way to define a
Howard> standard use of a component with all the information that
Howard> would exist in the assembly file for that component in a
Howard> seperate file that can be included (like in a C #include) to
Howard> facilitate simplier re-use.
XML external entities allow inclusion of external fragments into XML
documents.
Bye
Greg
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>