Re: turbine 2.4M1

Hi Thomas,

Thanks a lot for answering. Well I do agree with you with
the release number (and it is something that I ve already
try) but when I did it, I ve got much more errors when
building turbine, almost all junit failed. So I just wonder
if I should put the latest stable release or just the one
indicated in the build file, but most of them are out of
date. Thanks for indicating the right release.

I am going to try again and let you know.

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.

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.

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?

Many thanks,
Thomas

commons-io 0.2-dev.20020717.100545 => 1.3 (there is a big
gap?)
commons-lang 2.0 => 2.2 
commons-logging 1.0.3 => 1.1 
commons-pool 1.1 => 1.3
javamail 1.3.1 => 1.4 
torque 3.1 => 3.3-RC1.

> java.lang.NoClassDefFoundError:
org/apache/commons/digester/substitution/VariableExpander
This is part of commons-digester, which is needed by
commons-configuration AFAIK.

>>>>>>  what should I do to fix this test
case ?  <<<<<<<

Are you sure that you want to use the Merlin container?
Maybe you should
give YAAFI a try?

>>>>>>> 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)

Many thanks!
Thomas

--------------------- ALICE SECURITE ENFANTS
---------------------
Protégez vos enfants des dangers d'Internet en installant
Sécurité Enfants, le contrôle parental d'Alice.
h
ttp://www.aliceadsl.fr/securitepc/default_copa.asp



------------------------------------------------------------
---------
To unsubscribe, e-mail: turbine-user-unsubscribejakarta.apache.org
For additional commands, e-mail: turbine-user-helpjakarta.apache.org

thomas.ungfreesbee.fr 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: turbine-user-unsubscribejakarta.apache.org
For additional commands, e-mail: turbine-user-helpjakarta.apache.org

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:
> thomas.ungfreesbee.fr 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: turbine-user-unsubscribejakarta.apache.org
> For additional commands, e-mail: turbine-user-helpjakarta.apache.org
> 


------------------------------------------------------------
---------
To unsubscribe, e-mail: turbine-user-unsubscribejakarta.apache.org
For additional commands, e-mail: turbine-user-helpjakarta.apache.org

Hi folks,

- ad YAAFI

it is small Avalon container for embedding into applications
or other
containers. Therefore limited functionality and no
dependencies apart
from the avalon framework.

- there have been discussions here about the integration of
other component models/containers but I don't know about the
status.

there are always discussions about embracing Spring or osgi
based
frameworks but at the end of the day it is your personal
choice. If you
would like to use Spring framework that's fine since you can
still run
YAAFI within Spring or the other way round.


If you have problems migrating services in any direction I
can help ... 

Cheers

Siegfried Goeschl


Thomas Vandahl wrote:
> thomas.ungfreesbee.fr 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: turbine-user-unsubscribejakarta.apache.org
> For additional commands, e-mail: turbine-user-helpjakarta.apache.org
> 
> 
> 


------------------------------------------------------------
---------
To unsubscribe, e-mail: turbine-user-unsubscribejakarta.apache.org
For additional commands, e-mail: turbine-user-helpjakarta.apache.org