> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] 
> This would solve 90% of the problems I had with Avalon.
> I had to create my container implementation because of this, 
> and it was 
> a real PITA.



> 
> BTW, I regard it as a requirement to be able to do this 
> without having 
> to create my complete version of the 
> container-componentmanager-whateverwecallit.

Understood.  The main challenge is what extensions do we
support.  I.E. Marcus had four phases of component use
when Avalon only ever talks about 3 (init, active,
destruction).

> 
> >>* reference implementation for a session object.  This is 
> how stateful
> >>  session beans (EJB spec) and servlets manage state in an otherwise
> >>  stateless environment.  It is also how they can manage to 
> be used by
> >>  multiple threads or contexts of execution simultaneously. 
>  We should
> >>  put together a reference implentation of this in 
> excalibur and then
> >>  vote whether it should be incorporated as part of Framework (at 
> >>least
> >>  the defining interfaces).
> > 
> > 
> > which raises another question: should we have optional interfaces 
> > (ones a container doesn't really have to recognize) in framework or 
> > not?
> 
> User speak: are they part of Avalon or not? ;-)
> 
> As Paul and I have recently seen on the James list, there is big 
> confusion between Framework, Excalibur and Phoenix.
> 
> One of the reasons is that many features of "Avalon" are not in 
> Framework but in Excalibur, Phoenix etc...

+1

> 
> IMNSHO, we should structure ourselves like this:
> 
>                      API
>                       |
>                       |  ------ Utility classes
>                     /   \
>                    /  |  \
>            Reference implementations
>               |  |  |  |  |  |  |
>        Applications tha work in the above
> 
> 
> 
> IE:
> 
>                    Framework
>                       |
>                       |  ------ Excalibur
>                     /   \
>                    /  |  \
> Phoenix,  Fortress, Merlin, Jesktop (yes, Jesktop)
>              |  |  |  |  |  |  |
>     Cornerstone, Phoenix Apps, Jesktop Apps
> 
> 
> This would clear up some confusion for the users.
> 
> Since we are talking about containers, I wanna commit my container 
> somewhere (since everyone has one, can't I?  ;-)

Don't you want to make what's there better, instead of splitting
attention
even further?

> 
> Where shall I put it, in an Excalibur scratchpad?

that would be the location, but excalibur is pretty crowded already.
why not join forces w/ Fortress or Merlin?


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to