generator, inputmodule, selector, transformer, etc can just access the
interface methods by adding
m_filesystemSources = (FileSystemSources)
manager.lookup(FileSystemSources.ROLE);
Hope this is a little what you meant...
Regards Ard
Is there a way to have the same component instance
.
-Original Message-
From: Ard Schrijvers [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 11, 2007 2:05 AM
To: users@cocoon.apache.org
Subject: RE: Same component instance but multiple roles
Hello,
I do not really understand why you want to implement both DupChecker
role
Simon Stanlake napisał(a):
Hi,
I think I have a simpler example that better illustrates the idea of 2
roles 1 component instance. Think of a producer-consumer application. A
producer component creates objects of type X. It then passes it to a
component - call it the translator - for handling.
manager in cocoon?
Thanks for all the help,
Simon
-Original Message-
From: Grzegorz Kossakowski [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 11, 2007 11:29 AM
To: users@cocoon.apache.org
Subject: Re: Same component instance but multiple roles
Simon Stanlake napisał(a):
Hi,
I think I
Is there a way to have the same component instance implement multiple
roles?
In short, I have a component that stores name-value pairs. The component
persists the list of pairs in a file. Some parts of the system need to
check for duplicates using the DupChecker interface like...
public
