--- Aaron Mulder <[EMAIL PROTECTED]> wrote:
> So with the new multi-parent class loader > support, what's the > difference between parentId, import, include, and > dependency? parentId and import both relate to other configurations. A list consisting of parentId followed by any imports is constructed and used as the parent classloaders. The first element of this list is used to get the domain and server for the object names in the configuration. For a configuration without any parentId or imports, you must specify the domain and server explicitly. parentId is theoretically unnecessary but I suggest retaining it for backward compatibility, ease of use when only one parent is needed, and clarity of determining which parent configuration determines the domain and server object name components. Include and dependency both relate to items in the repository and add them to the URL[] of the current configurations classloader. dependency elements use the items in place in the repo, whereas include elements result in the item being copied into the configuration itself. I'm not sure include is tested enough to be reliable. thanks david jencks
