> -----Original Message-----
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
> > In particular:
> >
> > 1. usage of standard avalon meta tags
> > 2. elimination of fortress specific context dependencies
> > 3. resolution of components using /Selector semantics
> >
> This might be a dumb question, but can you give more information
> for those tasks (or a direct pointer to the docs explaining
> the things)? That would be great!
Another way to say it is "get excalibur components to easily run in Merlin
too."
1. Use the avalon meta tags where needed:
http://avalon.apache.org/meta/tools/tags/index.html
2. Not sure. My assumption is some excalibur components might be
getting things from the Context object in a way only supported
by Fortress at the moment. Would need to generalize the use
of the Context object.
3. Merlin doesn't support ServiceSelector (for many reasons). If
any excalibur components either use or encourage this, then we'd
need to change that.
Cornerstone components were written with Phoenix in mind. Excalibur
components were written with ECM/Fortress in mind. We need to bridge those
gaps.
One problem is that addressing these three concerns dives straight into the
heart of resolving "holes" in the framework which the various containers
took advantage of. So, in another sense, resolving these issues in
Excalibur requires consensus and solutions in the framework level. That's
another reason this has stalled.
J. Aaron Farr
SONY ELECTRONICS
DDP-CIM
(724) 696-7653
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
