Kerry, >Hi Paul. Thanks for your reply. > No probs.
>>No, not all classes need to be components. >> > >That is what I thought, but could you elaborate more here? How would my >non-component classes access component services like logging and >datasource? > Extending AsbtractLogEnabled or implementing LogEnabled is what you want for those. Somthing that is logged has to invoke the enableLogging(..) method. >I didn't see any documentation about how to use the >ExcaliburComponentManager from within a servlet environment. I created >a singleton class called ComponentContainer that uses the >ExcaliburComponentManager. Is this the common way to do set this up? > Not my area... sorry. >I suppose, I could just get the instance of my singleton >ComponentContainer class in any class in my application and then >retrieve a component, but I thought this might not be very good >practice. > >I feel like I am asking pretty fundamental questions. Have I missed >some critical examples or documentation? > It's common. We're all too close to the task to see things from the newbie point of view. If OK with you, when we "get there" could you write a couple or paragraphs under the title of "how to log enable normal classes without making them Components" ? We'd put it in the FAQ with your name as author.. some small fame ;-) Regards, - Paul H -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
