hi grzegorz, org.apache.cocoon.components.cron.CronJob/test is a combination of role name and hint.
a role name identifies a work interface (think Java interfaces). if there are several components available to be used for the role/interface a hint is used to select one of them. just think of sitemap components, e.g. generators. all generator components (FileGenerator, RequestGenerator, ...) implement the work interface org.apache.cocoon.generation.Generator and have/implement Generator's role. in the sitemap you declare several components for that role and also name them, e.g. 'file' for FileGenerator. that name is later used as the hint to select the specific generator. > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Auftrag von Grzegorz Goliatus Tańczyk > Gesendet: Samstag, 6. März 2004 08:56 > An: Reinhard Pötz > Betreff: Re[2]: how does CronJob/test work > > > Witaj Reinhard, > > W Twoim liście datowanym 5 marca 2004 (17:51:02) można przeczytać: > RP> have a look at cocoon.xconf . > RP> As jobs are Avalon components they need a role name so that > you can look > RP> up them. > > And why it is called like > this(org.apache.cocoon.components.cron.CronJob/test)? > > Is it any convention? > > -- > Pozdrowienia, > Grzegorz mailto:[EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
