Farr, Aaron <Aaron.Farr <at> am.sony.com> writes: > > But what is the typical direction for Non components accessing the > > Components. Do you just create regular instances of Component classes and > > use those ? Would that defeat any of Avalon's purposes ? > > Question: How should non-components access components? > Answer: Through the container. > Reality: There's more than one way to do it. > > Here are two ways: > 1. Direct access to components via the container > 2. Mapping components to JNDI lookups
I'm also interested in accessing components from non-components. But I use Cocoon and so still the ECM for the presentation layer and I don't want to create a second Avalon container in parallel like the (really interesting) JingDAO approach. There would be the option of having components in all layers, but that's a bit overhead IMO. Besides the fact that the suggested approaches might only work for Fortress and Merlin I didn't get the stuff that exactly has to be done as this is really new to me. I only worked inside a container (the Cocoon components), but not with a container until now. Thanks in advance, Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
