great!!!
now i'll have to restructure my system again - but the intervals between restructurings become larger ;-))
One thing you may want to keep in mind is the possibility of using packaged profiles as templates. You can create a [classname].xprofile file and include within it a set of component directives .. for example
<profiles>
<profile name="classic">
<configuration>
<source>Paris</source>
</configuration>
</profile>
</profiles>From with a facility you can do something like the following:
String classname = "IdentifiableDemo";
TypeRepository repo =
m_container.getClassLoaderModel().getTypeRepository();
Type type = repo.getType( classname );
ComponentProfile[] profiles = repo.getProfiles( type );The profiles array is guaranteed to contain at least one profile and if you have a .xprofile resource collocated with the component class then all of the component profiles in the .xprofile will be returned. This makes it drop-dead-simple to construct new profile. Also, if you know the name of the profile you want to use - you can use it as a template against which you can build new profiles:
ComponentProfile template = repo.getProfile( type, "classic" ); ComponentProfile myProfile = new ComponentProfile( name, template );
Cheers, Steve.
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
