You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Peter Courcoux <pe...@courcoux.biz> on 2003/06/11 13:17:47 UTC
Avalon container for 2.3
Hi all,
In case its been missed, the avalon guys have released version 1.0 of
fortress. It occurs to me that with ECM being a deprecated container and
fortress now released and, I believe, able to handle ECM type
components, the question should be asked at what point does turbine
switch from ECM. From what I understand fortress is a good candidate for
replacing ECM.
Regards,
Peter
--
Peter Courcoux <pe...@courcoux.biz>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
RE: Avalon container for 2.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Ok, silly me. Just did grep -i ecm on the directory and as I found no
matches, I said "no ecm". But it is ExcaliburComponentManager. =:-)
Quinton: Any chance that we can switch to Fortress before we put out the
2.3 release? Is it very complicated to switch?
Regards
Henning
On Wed, 2003-06-11 at 17:07, Quinton McCombs wrote:
> public class TurbineAvalonComponentService
> extends TurbineBaseService
> implements AvalonComponentService, Initializable, Disposable
> {
> /** Logging */
> private static Log log = LogFactory.getLog(
> TurbineAvalonComponentService.class);
>
> /** Component manager */
> private ExcaliburComponentManager manager = new
> ExcaliburComponentManager();
>
> [snip]
>
> }
>
> --------------------------------------------
> Quinton McCombs
> NequalsOne - HealthCare marketing tools
> mailto:qmccombs@NequalsOne.com
> http://www.NequalsOne.com
>
> > -----Original Message-----
> > From: Henning P. Schmiedehausen [mailto:hps@intermeta.de]
> > Sent: Wednesday, June 11, 2003 10:06 AM
> > To: turbine-dev@jakarta.apache.org
> > Subject: Re: Avalon container for 2.3
> >
> >
> > "Quinton McCombs" <qm...@nequalsone.com> writes:
> >
> > >> I don't see us using any container anywhere. Am I wrong?
> >
> > >Yes. You are mistaken. ECM is used inside of the
> > >AvalonComponentService.
> >
> > Ah, cool. Where is this?
> >
> > Regards
> > Henning
> >
> > --
> > Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> > hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
> >
> > Java, perl, Solaris, Linux, xSP Consulting, Web Services
> > freelance consultant -- Jakarta Turbine Development -- hero for hire
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
> >
> >
> >
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
RE: Avalon container for 2.3
Posted by Quinton McCombs <qm...@nequalsone.com>.
public class TurbineAvalonComponentService
extends TurbineBaseService
implements AvalonComponentService, Initializable, Disposable
{
/** Logging */
private static Log log = LogFactory.getLog(
TurbineAvalonComponentService.class);
/** Component manager */
private ExcaliburComponentManager manager = new
ExcaliburComponentManager();
[snip]
}
--------------------------------------------
Quinton McCombs
NequalsOne - HealthCare marketing tools
mailto:qmccombs@NequalsOne.com
http://www.NequalsOne.com
> -----Original Message-----
> From: Henning P. Schmiedehausen [mailto:hps@intermeta.de]
> Sent: Wednesday, June 11, 2003 10:06 AM
> To: turbine-dev@jakarta.apache.org
> Subject: Re: Avalon container for 2.3
>
>
> "Quinton McCombs" <qm...@nequalsone.com> writes:
>
> >> I don't see us using any container anywhere. Am I wrong?
>
> >Yes. You are mistaken. ECM is used inside of the
> >AvalonComponentService.
>
> Ah, cool. Where is this?
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>
> Java, perl, Solaris, Linux, xSP Consulting, Web Services
> freelance consultant -- Jakarta Turbine Development -- hero for hire
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: Avalon container for 2.3
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Quinton McCombs" <qm...@nequalsone.com> writes:
>> I don't see us using any container anywhere. Am I wrong?
>Yes. You are mistaken. ECM is used inside of the
>AvalonComponentService.
Ah, cool. Where is this?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
RE: Avalon container for 2.3
Posted by Quinton McCombs <qm...@nequalsone.com>.
> -----Original Message-----
> From: Henning P. Schmiedehausen [mailto:hps@intermeta.de]
> Sent: Wednesday, June 11, 2003 9:36 AM
> To: turbine-dev@jakarta.apache.org
> Subject: Re: Avalon container for 2.3
>
>
> Peter Courcoux <pe...@courcoux.biz> writes:
>
> >components, the question should be asked at what point does turbine
> >switch from ECM. From what I understand fortress is a good candidate
> >for replacing ECM.
>
> Turbine uses ECM? The only point that we currently use any
> Avalon stuff is in the AvalonComponentService and this is, as
> far as I can see, some excalibur and some framework stuff.
>
> I don't see us using any container anywhere. Am I wrong?
Yes. You are mistaken. ECM is used inside of the
AvalonComponentService.
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>
> Java, perl, Solaris, Linux, xSP Consulting, Web Services
> freelance consultant -- Jakarta Turbine Development -- hero for hire
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: Avalon container for 2.3
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Peter Courcoux <pe...@courcoux.biz> writes:
>components, the question should be asked at what point does turbine
>switch from ECM. From what I understand fortress is a good candidate for
>replacing ECM.
Turbine uses ECM? The only point that we currently use any Avalon
stuff is in the AvalonComponentService and this is, as far as I can
see, some excalibur and some framework stuff.
I don't see us using any container anywhere. Am I wrong?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
RE: Avalon container for 2.3
Posted by Quinton McCombs <qm...@nequalsone.com>.
> -----Original Message-----
> From: Peter Courcoux [mailto:peter@courcoux.biz]
> Sent: Wednesday, June 11, 2003 6:18 AM
> To: Turbine Developers List
> Subject: Avalon container for 2.3
>
>
> Hi all,
>
> In case its been missed, the avalon guys have released
> version 1.0 of fortress. It occurs to me that with ECM being
> a deprecated container and fortress now released and, I
> believe, able to handle ECM type components, the question
> should be asked at what point does turbine switch from ECM.
> From what I understand fortress is a good candidate for replacing ECM.
Fortress is indeed a good replacement for ECM. I will try to get ECM
replaced as soon as I have free time from my work schedule. I
originally went with ECM in the AvalonComponentService because Fortress
was not released.
> Regards,
>
> Peter
> --
> Peter Courcoux <pe...@courcoux.biz>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org