> -----Original Message-----
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
>
> In addition, what I meant with my above statement is that you
> should make sure that components in a component library not only
> use all the latest available features of the latest container
> version. They should also be runnable in older containers. For
> example, if a component uses meta-info then it's not usable with
> ECM. If a component uses meta-info that only Merlin supports,
> than it's not useable with Fortress and so on.

It's possible to write completely container-neutral code, but it's not
always easy.  It means a "lowest common denominator" approach.  For most
things, that's fine, but where it gets rough is in the ServiceManager lookup
schemes and in Context values.  The meta-info and configuration isn't as bad
since we can offer several configuration files with each component.

> The more I think about it, the more I come to the conclusion that
> the current situation is bad. People, currently using ECM can
> choose between Fortress and Merlin, but if they choose Fortress
> they already know that they have to migrate sooner or later
> to Merlin anyway.
> People writing components have to choose for which container they
> write components - obviously the container they are using.
> So, perhaps it would really be better to forget Fortress and move
> everything into Merlin but of course maintain the simplicity of
> Fortress. Embedding Fortress into an own application is four or
> five lines of Java code and some simple configuration file. That's
> it.

Yep.  That's exactly the problem and the whole point of this discussion.  We
want a solid direction forward.  I love Fortress and I'm partial to
approaches like Pico and Spring, but I also think Merlin rocks too and if we
can exorcise the complexity ghosts that have haunted its reputation, we
could have a really good solution to this problem.

Personally, I still like the idea of A4 vs A5 since I think it frames the
problem well, but maybe that's just me.

Also, I would like to look into the Cocoon base again (it's been a _long_
time) and see exactly where and how you're using ECM/Fortress.  Is Fortress
being used in the latest release(s)?

J. Aaron Farr
  SONY ELECTRONICS
  DDP-CIM
  (724) 696-7653

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

Reply via email to