LDEV-5147 fix debug template error on mode switch

Reset cached configuration fields (debugEntries, mailServers, restMappings)
when switching between Single and Multi mode contexts. These lazily-initialized
fields would become stale after mode switching, causing component loading to fail
with "can't find component [lucee.admin.debug.Simple]".

The fix ensures a fresh reload from the new configuration context by resetting
these fields to empty arrays in MultiContextConfigWeb when setInstance() is called.

Version: 6.2.8.17 → 6.2.8.18-SNAPSHOT

Author: michaeloffner

core/src/main/java/lucee/runtime/config/ConfigWebImpl.java

@@ -1878,6 +1878,12 @@ public ConfigWebImpl setInstance(ConfigWebInner instance) {
 			this.instance.reset();
 		}
 		this.instance = instance;
+		if (instance instanceof MultiContextConfigWeb) {
+			MultiContextConfigWeb mcw = (MultiContextConfigWeb) instance;
+			mcw.setDebugEntries(new DebugEntry[0]);
+			mcw.setMailServers(new Server[0]);
+			mcw.setRestMappings(new lucee.runtime.rest.Mapping[0]);
+		}
 		return this;
 	}
 

loader/build.xml

@@ -2,7 +2,7 @@
 <project default="core" basedir="." name="Lucee" 
   xmlns:resolver="antlib:org.apache.maven.resolver.ant">
 
-  <property name="version" value="6.2.8.17-SNAPSHOT"/>
+  <property name="version" value="6.2.8.18-SNAPSHOT"/>
 
   <taskdef uri="antlib:org.apache.maven.resolver.ant" resource="org/apache/maven/resolver/ant/antlib.xml">
     <classpath>

loader/pom.xml

@@ -3,7 +3,7 @@
 
   <groupId>org.lucee</groupId>
   <artifactId>lucee</artifactId>
-  <version>6.2.8.17-SNAPSHOT</version>
+  <version>6.2.8.18-SNAPSHOT</version>
   <packaging>jar</packaging>
 
   <name>Lucee Loader Build</name>