You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by EP...@upstate.com on 2003/06/17 18:39:54 UTC
Fragileness in PullService and VelocityService
Hi all,
I discovered something while trying to do final testing on the Configuration
stuff. I couldn't get Turbine to use pull tools when I loaded via the
ConfigurationFactory, but via the old method, everything worked. However, I
did come up with what the issue is using the old method:
Fails:
services.VelocityService.classname=org.apache.turbine.services.velocity.Turb
ineVelocityService
services.PullService.classname=org.apache.turbine.services.pull.TurbinePullS
ervice
Suceeds:
services.PullService.classname=org.apache.turbine.services.pull.TurbinePullS
ervice
services.VelocityService.classname=org.apache.turbine.services.velocity.Turb
ineVelocityService
The TurbineVelocityService REQUIRES the TurbinePullService to load up first.
However, my darn config factory doesn't have any order to the parameters as
they are returned..
Not sure what to do.. Change Configuration so that if you have paramerters:
Services.a
Services.b
Services.c
then they are always returned in that order? Ugh... Or, change something
in Turbine to force PullService to load before VelocityService?
Eric Pugh
Re: Fragileness in PullService and VelocityService
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
EPugh@upstate.com writes:
Yes. If you don't, the pull service doesn't register with velocity
service for refresh.
Yes, it sucks. However, there no really easy way around this without
major core changes.
Regards
Henning
>------_=_NextPart_001_01C334EF.14947E90
>Content-Type: text/plain;
> charset="iso-8859-1"
>Hi all,
>I discovered something while trying to do final testing on the Configuration
>stuff. I couldn't get Turbine to use pull tools when I loaded via the
>ConfigurationFactory, but via the old method, everything worked. However, I
>did come up with what the issue is using the old method:
>Fails:
>services.VelocityService.classname=org.apache.turbine.services.velocity.Turb
>ineVelocityService
>services.PullService.classname=org.apache.turbine.services.pull.TurbinePullS
>ervice
>Suceeds:
>services.PullService.classname=org.apache.turbine.services.pull.TurbinePullS
>ervice
>services.VelocityService.classname=org.apache.turbine.services.velocity.Turb
>ineVelocityService
>The TurbineVelocityService REQUIRES the TurbinePullService to load up first.
>However, my darn config factory doesn't have any order to the parameters as
>they are returned..
>Not sure what to do.. Change Configuration so that if you have paramerters:
>Services.a
>Services.b
>Services.c
>then they are always returned in that order? Ugh... Or, change something
>in Turbine to force PullService to load before VelocityService?
>Eric Pugh
>------_=_NextPart_001_01C334EF.14947E90--
--
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: Fragileness in PullService and VelocityService
Posted by Quinton McCombs <qm...@nequalsone.com>.
This is not the only case that you will find on services having a
dependency on each other. This is why the order in which the services
are listed in TR.props is important. I think that in order to support
the existing coupled services, you will need to allow for a configurable
initialization order.
--------------------------------------------
Quinton McCombs
NequalsOne - HealthCare marketing tools
mailto:qmccombs@NequalsOne.com
http://www.NequalsOne.com
> -----Original Message-----
> From: EPugh@upstate.com [mailto:EPugh@upstate.com]
> Sent: Tuesday, June 17, 2003 11:40 AM
> To: turbine-dev@jakarta.apache.org
> Subject: Fragileness in PullService and VelocityService
>
>
> Hi all,
>
> I discovered something while trying to do final testing on
> the Configuration
> stuff. I couldn't get Turbine to use pull tools when I loaded via the
> ConfigurationFactory, but via the old method, everything
> worked. However, I
> did come up with what the issue is using the old method:
>
>
> Fails:
> services.VelocityService.classname=org.apache.turbine.services
> .velocity.Turb
> ineVelocityService
> services.PullService.classname=org.apache.turbine.services.pul
> l.TurbinePullS
> ervice
>
> Suceeds:
> services.PullService.classname=org.apache.turbine.services.pul
> l.TurbinePullS
> ervice
> services.VelocityService.classname=org.apache.turbine.services
> .velocity.Turb
> ineVelocityService
>
> The TurbineVelocityService REQUIRES the TurbinePullService to
> load up first.
> However, my darn config factory doesn't have any order to the
> parameters as
> they are returned..
>
> Not sure what to do.. Change Configuration so that if you
> have paramerters:
> Services.a
> Services.b
> Services.c
>
> then they are always returned in that order? Ugh... Or,
> change something
> in Turbine to force PullService to load before VelocityService?
>
> Eric Pugh
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org