I should add a final note... I haven't tested this, but it may not be
the builder vs non-builder that is at fault here, but hierachical
(since builder uses this via combined configuration) vs non-
hierachical (since the test case uses this - via BaseConfiguration)
On 11/02/2007, at 11:54 PM,
Well, it has become even more confusing :) My assessment is that it
should be left as it is currently for 1.4 (see below).
I've attached some unit tests to the issue.
I've found that under 1.3, the same configurations constructed using
a builder behave differently to those constructed by han
Brett Porter wrote:
> Hi,
>
> I tested out 1.4 on some code I have using 1.3, which has some
> expressions that resolve within the same configuration, but which is
> located at a different prefix (via config-at). This broke under 1.4, as
> it now assumes all interpolations need to happen in the
Hi,
I tested out 1.4 on some code I have using 1.3, which has some
expressions that resolve within the same configuration, but which is
located at a different prefix (via config-at). This broke under 1.4,
as it now assumes all interpolations need to happen in the parent.
The feature is de
