RE: [OS-webwork] How do you define a component ?

[Jason Carreira]

Title: Message

Think of them as services... your persistence manager might be a good candidate. You could bind a Hibernate implementation, for instance, into the persistence manager spot in the registry. It could declare that it depends on a ConnectionProvider (another component) so it would be provided one when it is instantiated. You could also have a ShoppingCart component / service which depends on the PersistenceManager, etc... -----Original Message----- From: Christian Meunier [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:37 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] How do you define a component ? Refining a little bit my question, what does make a good candidate for a component ? Obvious examples we see everywhere is bridge component ( Trade component to query a trade engine etc...) but beside this ? Many things can be done with interceptors and you can always re use your business layer or part of it in another applications, guess i dont get it :)   Chris   ----- Original Message ----- From: Christian Meunier To: [EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 12:20 PM Subject: [OS-webwork] How do you define a component ? Hi everyone, while reading the topic about nano/pico container, few questions keep coming to my mind, what exactly is a component, which purpose does it have ? How exactly is it different from an aspect in AOP ? How do you choose to code something as a component rather than as a 'module' in your business logic ?   Thanks in advance for any though you can share on this topic. Christian Meunier