Hi all,
I think that merlin is maintained at dpml.net.
A lot of the current component framework activity seems to be around
osgi environments. See the apache Felix project, knopplerfish.org,
eclipse equinox for example. The fulcrum components work with yaafi and
turbine so I would look at yaafi, unless I wanted to move to an osgi
based framework, which does have some benefits.
Regards,
Peter
Thomas Vandahl wrote:
[EMAIL PROTECTED] wrote:
About merlin, I know that it is going to be replaced by
Yaafi on 2.4M2 but I wanted to migrate first to 2.4M1 then
2.4M2. I ve made diff between 2.3.2/2.4M1 and 2.4M1/2.4M2,
and it seems that the major changes are on 2.3.2/2.4M1.
Actually, I'm not sure what the state of the 2.4M2 tag really is. I
would probably rather try to release off the trunk. I had a couple of
tests failing in the trunk but not as bad as your test.
As far as I know, Merlin is now maintained by some other company and if
at all you will need to deploy YAAFI or Fortress to have a decent Avalon
container. There have been discussions here about the integration of
other component models/containers but I don't know about the status.
Siegfried, Peter do you care to comment?
Because of the missing documentation indicating "how to
migrate", I need to understand first what have been changed
and what should I change. I am little bit concern about
2.4M2 because some fulcrum components are not yet released
and for other reasons.
Right you are. I've been dealing with the security components lately,
which I would like to be as compatible to the previous version as
possible to ease migration. This in part depends on the Torque 3.3
release which I would like to finish in the next few weeks.
Thomas, my question for 2.4M1 is that: should I care about
the junit tests because more of them fail when I put the
latest dependencies as you indicate below? Or should the
turbine code and these "test cases" be migrated?
The latter, definitely. I'd appreciate your help.
I do not have any opinion on merlin or yaafi.
Because yaafi is in 2.4M2, I am going to use it. Right now
It is not clear on what It does. I seems that it allows
"components" to be pluggable? (I am also little afraid about
this migration because I am not sure about what I am going
to do. I will probably going to learn a lot but I don't want
to loose time)
Components replace Turbine services. Avalon is an approach to give
generic components an environment to live in. Many similar approaches
have been made in the meantime, but still, Avalon has its advantages.
For an introduction into the concepts, see http://excalibur.apache.org.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
