You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by David Sean Taylor <da...@b3interactive.com> on 2001/03/21 18:30:59 UTC
[services] standard naming in TR.p definition
Im writing a Turbine service.
Trying to figure out the standard for naming services in the TR.p
Is it
services.[interfaceName].classname=[full implementation classname]
such as
services.PoolBrokerService.classname=org.apache.turbine.services.db.TurbineP
oolBrokerService
................^ interface
.....................................................................^
implementing class
-- OR --
services.[className].classname=[full implementation classname]
services.TurbineGlobalCacheService.classname=org.apache.turbine.services.cac
he.TurbineGlobalCacheService
...............^ implementing class
............................................................................
....^ implementing class
In the first example, the interface has an final static, such as
public interface PoolBrokerService extends Service
{
/** the name of the service */
public static final String SERVICE_NAME = "PoolBrokerService";
.....................................................^ name of the interface
and then in the latter, its then name of the class
public interface GlobalCacheService extends Service
{
public static final String SERVICE_NAME = "TurbineGlobalCacheService";
...............................................^ implementing classname
I believe the first example is better [interfaceName], however the majority
of services use the latter
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: [services] standard naming in TR.p definition
Posted by Rafal Krzewski <Ra...@e-point.pl>.
Daniel Rall wrote:
> This is the correct pattern, but not all of the current code may
> conform. Moving any non-conformant code towards this is desired, and
> has been approved by a vote (twice actually, I believe).
Yeah, at least twice... I think it's time for major spring cleaning
throughout the codebase :-)
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:Rafal.Krzewski@e-point.pl
+48 22 8534830 http://e-point.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: [services] standard naming in TR.p definition
Posted by Daniel Rall <dl...@collab.net>.
"David Sean Taylor" <da...@b3interactive.com> writes:
> services.[interfaceName].classname=[full implementation classname]
This is the correct pattern, but not all of the current code may
conform. Moving any non-conformant code towards this is desired, and
has been approved by a vote (twice actually, I believe).
Daniel Rall
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org