a

Author: kaspernielsen

modules/packed/src/main/java/app/packed/concurrent/ThreadNamespaceConfiguration.java

@@ -23,7 +23,7 @@
 // Fyldt med Thread factories/pools
 // Hvad med extensions??? Vi vil gerne kunne configure deres.
 // Maaske deler vi en enkelt. Maaske har vi noget hierrakisk hvor vi nedarver settings
-public final class ThreadNamespaceConfiguration {
+final class ThreadNamespaceConfiguration {
 
 //    public DaemonOperationConfiguration addDaemon(Consumer<DaemonContext> action) {
 //        throw new UnsupportedOperationException();
@@ -57,8 +57,7 @@ public final class ThreadNamespaceConfiguration {
 }
 //
 
-//// Hvad hvis vi har flere annoteringer??? Vi kan vel kun have en?
-//// Den giver ikke super mening..
+//// Hvad hvis vi har flere annoteringer??? Vi kan vel kun have en? Den giver ikke super mening..
 //public DaemonOperationConfiguration addDaemonApplication(Assembly assembly, Wirelet... wirelets) {
 //  throw new UnsupportedOperationException();
 //}

modules/packed/src/main/java/app/packed/concurrent/ThreadOverviewMirror.java

@@ -24,9 +24,6 @@
  * <p>
  * A application
  */
-// We must have one per extension...
-// I mean we have a service namespace per extension.
-// So would probably be strange to share one for extensions?
 public final class ThreadOverviewMirror extends OverviewMirror<BaseExtension> {
 
     /**

modules/packed/src/main/java/app/packed/extension/OverviewHandle.java

@@ -52,7 +52,7 @@ public sealed interface OverviewHandle<E extends Extension<E>> permits PackedOve
      */
     <T extends OperationMirror> OperationMirror.OfStream<T> operations(Class<T> operationType);
 
-    Type type();
+    Type overviewType();
 
     enum Type {
         APPLICATION, NAMESPACE, EXTENSION;

modules/packed/src/main/java/app/packed/extension/OverviewMirror.java

@@ -80,4 +80,8 @@ protected final OperationMirror.OfStream<OperationMirror> operations() {
     protected final <T extends OperationMirror> OperationMirror.OfStream<T> operations(Class<T> operationType) {
         return handle.operations(operationType);
     }
+
+    public final OverviewHandle.Type overviewType() {
+        return handle.overviewType();
+    }
 }

…p/packed/namespace/NamespaceContext.java …/app/packed/namespace/NamespaceInfo.javamodules/packed/src/main/java/app/packed/namespace/NamespaceContext.java renamed to modules/packed/src/main/java/app/packed/namespace/NamespaceInfo.java modules/packed/src/main/java/app/packed/namespace/NamespaceContext.java renamed to modules/packed/src/main/java/app/packed/namespace/NamespaceInfo.java

@@ -22,9 +22,8 @@
 /**
  *
  */
-// Giver denne mening, hvis mn ikke har nogle controller metoder???
-// Maaske namespace info er nok
-public interface NamespaceContext {
+// Was NamespaceController, but we have no controller methods
+public interface NamespaceInfo {
 
     /** {@return the component path of the namespace} */
     ComponentPath componentPath();

modules/packed/src/main/java/internal/app/packed/component/PackedOverviewHandle.java

@@ -151,7 +151,7 @@ public OperationMirror.OfStream<OperationMirror> operations() {
         }
 
         @Override
-        public Type type() {
+        public Type overviewType() {
             return Type.APPLICATION;
         }
     }
@@ -171,7 +171,7 @@ public OperationMirror.OfStream<OperationMirror> operations() {
         }
 
         @Override
-        public Type type() {
+        public Type overviewType() {
             return Type.EXTENSION;
         }
     }
@@ -191,7 +191,7 @@ public OperationMirror.OfStream<OperationMirror> operations() {
         }
 
         @Override
-        public Type type() {
+        public Type overviewType() {
             return Type.NAMESPACE;
         }
     }