On Mon, 3 Mar 2003 22:35, Schaible, J�rg wrote: > currently I am somewhat puzzled about what implementing as service (a.k.a. > component) and what not. In my application I have a tiny subset of a JNDI > interface and wonder, whether I should implement the "TinyContext" and > "TinyDirContext" as service or not. My current feeling (after the DaW "What > is not a good component?") says no. The single element in such a DirContext > scenario that cound be a service, seems to be the initial DirContext > responsible using some kind of factory for the other elements.
Think of it another way. Services/Components are usually behaviour oriented. Data/Resources do not make good services/components - for every data/resource elemtn people usually have a coresponding factory/manager service. SO in your case you would have a "ContextManager" service that gave you access to the "Context" resource. > Basically all services are installed during the initialization phase and I > should normally not create new ones on the fly - right? thats generally the idea. > Can I use the same role more than once, but use a different > id and different attributes? yes .. but I forget off hand how this is done in fortress .. sorry. Someone else? -- Cheers, Peter Donald ------------------------------------------------------- To fight and conquer in all your battles is not supreme excellence; supreme excellence consists in breaking the enemy's resistance without fighting. - Sun Tzu, 300 B.C. ------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
