Start planning for element namespacing

Author: hugithordarson

ng-appserver/src/main/java/ng/appserver/elements/NGSwitchComponent.java

@@ -14,6 +14,7 @@
 import ng.appserver.NGElement;
 import ng.appserver.NGRequest;
 import ng.appserver.NGResponse;
+import ng.appserver.templating.NGElementManager;
 
 /**
  * Implementation based on Project Wonder's ERXWOSwitchComponent by
@@ -83,7 +84,7 @@ public NGElement _realComponentWithName( final String name, final String element
 
 		// No component instance found so we're going to have to construct a new one
 		if( localWOElement == null ) {
-			localWOElement = NGApplication.application().elementManager().dynamicElementWithName( name, _componentAssociations, _contentTemplate );
+			localWOElement = NGApplication.application().elementManager().dynamicElementWithName( NGElementManager.GLOBAL_UNNAMESPACED_NAMESPACE, name, _componentAssociations, _contentTemplate );
 
 			if( localWOElement == null ) {
 				throw new RuntimeException( "<" + getClass().getName() + "> : cannot find component or dynamic element named " + name );

ng-appserver/src/main/java/ng/appserver/templating/NGElementManager.java

@@ -13,8 +13,20 @@
 import ng.appserver.NGElement;
 import ng.appserver.NGElementUtils;
 
+/**
+ * Manages access to and location of dynamic elements and components registered with a project
+ */
+
 public class NGElementManager {
 
+	/**
+	 * I WO, elements are not namespaced. To help porting older templates, we therefore allow unnamespaced elements
+	 * by designating the namespace "wo" a "magic namespace" which when used for locating elements means searching every namespace.
+	 *
+	 * This is probably/hopefully temporary.
+	 */
+	public static final String GLOBAL_UNNAMESPACED_NAMESPACE = "wo";
+
 	/**
 	 * @return The named component, where [componentName] can be either the component's simple class name or full class name.
 	 */
@@ -73,7 +85,7 @@ private static NGComponentDefinition componentDefinition( final String component
 	 *
 	 * FIXME: We're missing a cache for dynamic element name resolution // Hugi 2025-03-05
 	 */
-	public static NGDynamicElement dynamicElementWithName( final String elementIdentifier, final Map<String, NGAssociation> associations, final NGElement contentTemplate ) {
+	public static NGDynamicElement dynamicElementWithName( final String namespace, final String elementIdentifier, final Map<String, NGAssociation> associations, final NGElement contentTemplate ) {
 		Objects.requireNonNull( elementIdentifier );
 		Objects.requireNonNull( associations );
 

ng-appserver/src/main/java/ng/appserver/templating/NGTemplateParserProxy.java

@@ -73,7 +73,7 @@ private static NGElement toDynamicElement( final PBasicNode node ) {
 		final NGElement childTemplate = toTemplate( node.children() );
 
 		try {
-			return NGApplication.application().elementManager().dynamicElementWithName( type, associations, childTemplate );
+			return NGApplication.application().elementManager().dynamicElementWithName( NGElementManager.GLOBAL_UNNAMESPACED_NAMESPACE, type, associations, childTemplate );
 		}
 		catch( NGElementNotFoundException e ) {
 			// FIXME: Experimental functionality, probably doesn't belong with the parser part of the framework.