Disclaimer: newbie talking, wishful thinking mode on.

If this has been brought up before, my apologies. One of the things
I would like to see in Avalon 5 (4.5, x+1, whatever) is documented
patterns for integration with other component models (I'm using the
word component in a loose sense here). For example, we are using
EJBs in other projects, and I think it would be great to have a
documented way of approaching these scenarios:

* Components are implemented as Avalon components, EJBs are shallow
  bridges to them.
* Components are implemented as EJBs, Avalon components serve as
  interfaces to the components from the non-EJB world (is this doable
  at all?).
* Hybrid mode: some components are EJBs, some are Avalonized.

The EJB model is just an example here, it would be nice to have well
documented patterns for doing this integration with Servlets, CORBA,
COM, etc. I don't know all of these very well, so it may be that it
is simply not possible to have this degree of integration, but I
think it would be very good to have documented patterns for Servlets
and EJBs at least.

Best regards, and thanks for a solid architecture.


-- 
Gonzalo A. Diethelm
[EMAIL PROTECTED]


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

Reply via email to