Hi Muhammad, components are exchangeable and should have a relatively small and well defined interface. In most applications you will find some natural candidates for components since these candidates are the main building blocks of the application. Then there often have to be some classes between these building blocks. If they can becombined with some resonable interfaces they are good components, too. This way you have covered your whole application with components. This is what we have dome with GloBUS. If your application is very big and you still have got components that aren't really maintainable because they are too big, split them up into several subcomponents. Finally if you want to be able to exchange the implementation of some classes they probably should be components, too.
Regards, Ole P.S.: Greetings to the rest of the EBP-Team! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
