hi berin, xfp is a kind of xml-based scripting framework. > 1) Is XFP an application framework where users extend the basic one and add > their components later?
xfp itself is not actually built with avalon (for now). being it a "scripting" tool, users will use avalon components (and javabeans) as "variables". the framework must take care of managing the life-cycle of components. what i'm trying to do is somewhat similar to the <jsp:useBean> tag in jsp, but instead of supporting only javabeans, i'd like to manage avalon components. > 2) Exactly how does XFP allow users to specify their own components? xfp has its own XML configuration file, where users put their "scripts". the xml the user has to write to get an instance of an avalon component would be something like this: <attribute name="mycomponent" entity="component" class="org.myfirm.MyAvalonComponent"> <property name="myproperty">myvalue</property> <property name="myproperty">myvalue</property> </attribute> flavio On Wednesday 23 July 2003 18:35, Berin Loritsch wrote: > [EMAIL PROTECTED] wrote: > > hi all, > > i'm trying to instance and manage the life-cycle of avalon components > > specified by the user of an application i'm currently writing. what > > container should i use? i think containers that require an XML > > configuration file would not fit because the components to use are > > determined at runtime. as you may have guessed, i'm new to avalon. please > > help! > > > > btw, this is the app: > > http://xfp.sourceforge.net > > The link is temporarily down, so let me ask a couple questions to help me > understand what you are doing. > > 1) Is XFP an application framework where users extend the basic one and add > their components later? > > 2) Exactly how does XFP allow users to specify their own components? > > There are a number of ways to incorporate configuration information, and > it doesn't always have to be done by XML, although that's what most do. > In just about all the Avalon containers, if there is no explicit custom > configuration information, the container will pass in an empty > configuration element. Most components know how to handle that, and they > operate with the default settings for the configurable components. > > You might want to provide a way to let the components be configured, but > to give you ideas I need the answers to the above two questions. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
