still running in problems with my nested containers. attached you will find a testcase which fails. and a hack which solves the problem,
but it is a hack. should be done cleaner.
the point is that an implecit compoenent from a jar file carries its default configuration in its type, but when the DefaultDeploymentService
goes through the lifecycle, it uses the default configuration from appliance-context.
if the component is declared in the block.xml without configuration, the correct default configuration from its type is used, but not if the
component is not declared in the block.xml.
I hope the hack is not too far away from a patch.
with best wishes Kristian
PS you need to adjust the path within the engine-tag of the tmp/conf/block.xml
testcase.zip
Description: Zip archive
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
