Factory In  facelets TagLIb    timing  problem misunderstanding


I  ve got a simple problem with huge consequences. Maybe I  m seeing it wrong but (Please correct me then )



I simply want  to read(modify  but certainly not add records, never initialize to empty record)

 and  facelet records in my database.  But I still get troubled 

 

   

 ive  an @In DBentity  rec;// record   (implicitely  null initialy since I can not specify what  to load )

 

 

 Ive  a @Factory  DBentity   initialize()   //implicitely initializing  my record 

   

 so far all is  good

   

 My facet  is somewhat generic and detects  the Type(DBentity) of the entity Im  handling  and reacts  accordingly

 My  problem is  one  of timing 

   

 


 What  is the  order  of things ??

 WAY 1 I hoped  

 

   

 order :

 0/INitialize the  facelet (class initialisation [fetch arguments]

 1/@Factory    (loading  the  content of the  injection)

 2/ verify initialisation  of the  injection 

 3/ initialize  the  facelet (Facelet  apply()   routine ---

                          ---.parsing and  creating  the facelet context 

 4/execution and    rendering ---

                  

 WAY 2     I seam in SEAM to notice 

 

 

 order :                         

 0/INitialize the  facelet (class initialisation [fetch arguments]

 3/ initialize  the  facelet (Facelet  apply()   routine

                               completrely  ignoring the  inialisation  and not allowing  any  

                               injected values type  evaluation (TYP=NULL)

                          parsing and  creating  the facelet context 

 1/@Factory    (loading  the  content of the  injection)

 2/ verify initialisation  of the  injection 

 4/execution and    rendering 

 


 

                  

           My experiments are  not fully excusive  if WAY 1 or WAY 2  is used.

           I  ve the strong impression the order is different  dependent on other factors (?)

           Can anyone  throw any light on the matter  it would be  very helpfull.

           Detecting the  type  prior to the initialisation is quite a wast of architecture and functionality.

             

           

 There is certainly 1 situation where Way 2 is used, The problem is covered for.

 as the facelets are  part  of h:Datatable,   the variarable  is only initialised  somewhere inbetween execution and rendering

 

 

 

 

 

 Thanks in advance   (SORRY  FORMATTING  SEAM FORUM IS A PAIN IN THE ASS)        


                

                

                

                Invalid markup: unexpected token: DBentity at '... an @In <DBentity> ...'