qwe

a

Author: kaspernielsen

.gitignore

@@ -10,4 +10,5 @@ target.tmp
 dependency-reduced-pom.xml
 .DS_Store
 /trace*
-*.jfr
+*.jfr
+*.versionsBackup

architecture/TODO.txt

@@ -0,0 +1,3 @@
+Priorities
+
+MultiApp <-- Ikke super vigtig førend vi nejler app, men stadig 

architecture/application/multi/ManagedVsUnmanaged.txt

@@ -0,0 +1,5 @@
+Multi app er vel kun "svært" når man har managed applikationer.
+
+Når det er managed har man jo bare en reference.
+Det eneste er at man kan spawne en App fra en eksisterende app.
+Og den spawnede app kan så nedarve et eller andet

architecture/application/multi/Relationship.txt

@@ -0,0 +1,5 @@
+Der er vel flere typer relationer.
+
+Der er noget parent<->child noget, hvor man "arver" noget funktionalitet.
+
+Og saa maa der vaere noget temporal noget.

architecture/application/multi/hierarchical/Overview.txt

@@ -0,0 +1,6 @@
+Single Application
+
+Deployed at build time vs Deployed at runtime
+
+Application Instance Management vs other containers
+  Forskellen er lidt at applikationer kan afinstalleres

architecture/bean/Installation.txt

@@ -0,0 +1,14 @@
+4 Parties
+
+Framework - Extension - Hooks - Users
+
+// Installation flow
+User|Extension -> Extension -> Framework
+
+
+
+install(Object) [User] -> newBeanInstaller [Extension] -> Bean 
+
+
+BeanIn
+prep(Object).install()

architecture/bean/SidecarAttachment.txt

@@ -0,0 +1,23 @@
+Lige nu har vi
+
+Attachment                                   [Per Bean]
+Proxy <- Wrapper Bean Instancen (Skannes)
+Sidecar (Scannes som en bean)                [Per Bean Instance]
+
+
+
+Attachments er en slags runtime storage (Stable Value)
+  Det er ikke en constant eftersom vi saa bare kunne gemme den direkte et eller andet sted
+  Fx LocalDateTime for hvornaar beanen er instantieret. 
+
+
+Sidecars er fullblown beans... Med nogle markers  (Unlike attachments)
+
+Usecases
+ * Gem BuildTime og inject senere  [Attachment]
+ 
+ * Schedule en bean
+   
+  
+  
+  

architecture/bindings/Overview.md

@@ -0,0 +1,60 @@
+Resolution 
+  Manual  -> 
+  Hook    ->
+  Service ->
+  
+// Problemet er her AutoService...
+// Okay saa baade Service og Hook har en eller anden form for BindingMatcher [Annotation | Key]
+
+Services Resolution: Operation->Bean->Context->ServiceNamespace
+
+Resolution = [Manual | Service [Operation, Bean, Extension Context[Class?], Namespace], Annotation[...]]
+
+
+// Prep
+
+// Early Resolution
+//// Look for Annotated Variable Bean Trigger
+//// Look for Extension/Context Service Bean Trigger
+
+////  [These cannot be rebound], thats it, can either be manually bound later, will attempt to be service resolved later
+
+The rest will be resolved as a service (Key) or m
+
+/ Can manually override by binding index or as Service, will fail for bindings that have been resolved already
+
+//// AssemblyResolution
+// Resolution -> Keys bound to operation, Keys bound to bean, Keys bound to service namespace
+
+
+
+-------------------- Injectors
+FooInjector
+  call();
+
+
+MyExtensionBean
+   MyExtensionBean(FooInjector[] injectors) maybe MyExtensionBean(@Injectors FooInjector[] injectors) 
+  
+
+
+
+boundBy = Realm
+
+Context = Hook
+
+  
+Constant vs Operation
+
+Buildtime vs Runtime
+
+Service vs Hook
+
+Constant Runtime -> Constant per Bean Instance? or Application Instance
+
+----
+De der abstract invokers. De er maaske en (scan free) bean i virkeligheden... Eller maaske en sidecar de foelger jo instancen og faar injected instancen???
+  
+  [Build time value][Runtime value]
+
+Der er build values, saa kan der kommer run

architecture/build/order/OpenQuestions.txt

@@ -1,4 +1,4 @@
-Can an operation be added after Bean.OnConfigured?
+? Can an operation be added after Bean.OnConfigured?
 
 Jeg tror simpelthen alle hooks er koert nar vi begynder paa det..
 

architecture/operation/invoker/TypedInvoker.txt

@@ -4,7 +4,6 @@ Istedet for for en extension injected en invoker[] i en bean af eget valg.
 
 // Saa vi skal instantiere et array hver gang (StableValue??)
 
-
 ? Hvordan faar dem knyttet Invokeren til en Bean
 
 Man maa angive beanen naar man registere invokeren...