You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Sam Joseph <ga...@yha.att.ne.jp> on 2002/12/04 04:33:53 UTC
changing the default html tags
Hi
I am trying to serve some hdml pages off turbine, however turbine
defaults to an html page. I can't seem to find there this is set in the
code, or templates. Can anyone point me to the right place.
Thanks in advance.
CHEERS> SAM
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: changing the default html tags
Posted by ramadevi <ra...@cmcltd.com>.
Dear all,
I tied writing a new service but iam not successful as it is giving
initialisation exception can anyone help me.
with regards
rama
Sam Joseph wrote:
>
> Hi
>
> I am trying to serve some hdml pages off turbine, however turbine
> defaults to an html page. I can't seem to find there this is set in the
> code, or templates. Can anyone point me to the right place.
>
> Thanks in advance.
>
> CHEERS> SAM
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: changing the default html tags
Posted by ramadevi <ra...@cmcltd.com>.
Hi,
where do the basic files for the newapp are specified i.e index.vm
,login.vm to generate the application.
where sshould i change these properties to give a different file as home
page when the application is generated using ant tool.
regards
ramadevi
"Henning P. Schmiedehausen" wrote:
>
> ramadevi <ra...@cmcltd.com> writes:
>
> >Hi,
> >Is it possible to create a new service apart from the services provided
> >by the turbine.
>
> Yes, sure. Simply extend TurbineBaseService. You must then add your
> service to the TurbineResources.properties like this:
>
> services.<xxx>.classname = <full class name of your service>
>
> and you're set.
>
> If you look at the examples of the simple services like
> db/TurbinePoolBrokerService or servlet/TurbineServletService you'll
> get on speed pretty fast.
>
> In a Nutshell:
>
> - You must not try to provide a C'tor with parameters, best is not to
> provide any C'tor at all, because nothing should be done at
> construction time (You'll get the default c'tor which is fine for us).
>
> - Your Service will be instantiated exactly once. So it must be threadsafe,
> must not use class global variables for session-dependend information.
>
> - You should provide an init() method which is called when Turbine starts
> up and should initialized your service dependent code. There is lots
> of confusion of how this init() method should look like, I personally
> prefer the parameterless variant:
>
> public void init() throws InitializationException
> {
> }
>
> You must call setInit(true) if your service initializes correctly. Else
> no user of your service can find it. Right after this, your service might
> be queried and used by other sessions, so you should not call setInit()
> prematurely.
>
> - You might provide a shutdown() method which is called when Turbine shuts
> down. You can clean up your internal data in this method. You should call
> setInit(false) as the last thing in shutdown().
>
> - It is good style, that if you build the FooService, to provide:
>
> <yourpackage>.FooService.java with an Interface definition of your
> Service which extends o.a.t.services.Service
> It should contain a constant SERVICE_NAME
> with the Turbine visible name of your service.
>
> <yourpackage>.TurbineFooService.java which extends the TurbineBaseService,
> implements FooService and provides
> the actual code
>
> <yourpackage>.TurbineFoo.java which contains static facade methods for
> your service along the following lines:
>
> public abstract class TurbineFoo
> {
> protected static FooService getService()
> {
> return (FooService) TurbineServices
> .getInstance().getService(FooService.SERVICE_NAME);
> }
>
> [...]
>
> public static void fooMethod1()
> {
> getService().fooMethod1();
> }
>
> public static int fooMethod2(int bar)
> {
> return getService().fooMethod2(bar);
> }
>
> [...]
> }
>
> to give users of your service the ability to simply write
>
> TurbineFoo.fooMethod1();
>
> in their code and not to care which actual Implementation of FooService
> is running.
>
> init() and shutdown() applies to Turbine 2.1/2.2 This might change
> with the lifecycle interfaces in a later release.
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
>
> Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
> D-91054 Buckenhof Fax.: 09131 / 50654-20
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: changing the default html tags
Posted by ramadevi <ra...@cmcltd.com>.
Thanks for the inputs to add a new service.
i have done the same thing but my service is not initialised it is
throwing an initialisation exception.
as u said in the init method without parameters i just wrote
setinit(true).
nothing is done as iam not initialising anything.
so i gave only setinit(true);
what could be the problem?
thanks and regards
rama
"Henning P. Schmiedehausen" wrote:
>
> ramadevi <ra...@cmcltd.com> writes:
>
> >Hi,
> >Is it possible to create a new service apart from the services provided
> >by the turbine.
>
> Yes, sure. Simply extend TurbineBaseService. You must then add your
> service to the TurbineResources.properties like this:
>
> services.<xxx>.classname = <full class name of your service>
>
> and you're set.
>
> If you look at the examples of the simple services like
> db/TurbinePoolBrokerService or servlet/TurbineServletService you'll
> get on speed pretty fast.
>
> In a Nutshell:
>
> - You must not try to provide a C'tor with parameters, best is not to
> provide any C'tor at all, because nothing should be done at
> construction time (You'll get the default c'tor which is fine for us).
>
> - Your Service will be instantiated exactly once. So it must be threadsafe,
> must not use class global variables for session-dependend information.
>
> - You should provide an init() method which is called when Turbine starts
> up and should initialized your service dependent code. There is lots
> of confusion of how this init() method should look like, I personally
> prefer the parameterless variant:
>
> public void init() throws InitializationException
> {
> }
>
> You must call setInit(true) if your service initializes correctly. Else
> no user of your service can find it. Right after this, your service might
> be queried and used by other sessions, so you should not call setInit()
> prematurely.
>
> - You might provide a shutdown() method which is called when Turbine shuts
> down. You can clean up your internal data in this method. You should call
> setInit(false) as the last thing in shutdown().
>
> - It is good style, that if you build the FooService, to provide:
>
> <yourpackage>.FooService.java with an Interface definition of your
> Service which extends o.a.t.services.Service
> It should contain a constant SERVICE_NAME
> with the Turbine visible name of your service.
>
> <yourpackage>.TurbineFooService.java which extends the TurbineBaseService,
> implements FooService and provides
> the actual code
>
> <yourpackage>.TurbineFoo.java which contains static facade methods for
> your service along the following lines:
>
> public abstract class TurbineFoo
> {
> protected static FooService getService()
> {
> return (FooService) TurbineServices
> .getInstance().getService(FooService.SERVICE_NAME);
> }
>
> [...]
>
> public static void fooMethod1()
> {
> getService().fooMethod1();
> }
>
> public static int fooMethod2(int bar)
> {
> return getService().fooMethod2(bar);
> }
>
> [...]
> }
>
> to give users of your service the ability to simply write
>
> TurbineFoo.fooMethod1();
>
> in their code and not to care which actual Implementation of FooService
> is running.
>
> init() and shutdown() applies to Turbine 2.1/2.2 This might change
> with the lifecycle interfaces in a later release.
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
>
> Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
> D-91054 Buckenhof Fax.: 09131 / 50654-20
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: have I got to be careful about setting instance variables in Velocity Action subclasses?
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Henning P. Schmiedehausen" <hp...@intermeta.de> writes:
>"Neil Stevens" <ne...@firstlightassociates.co.uk> writes:
>>do actions need to be thread safe? Are they pooled and reused?
[...]
>Thread safe? Hm. I'd say no without caching and yes if caching is
>activated. So make this a "yes".
"yes" as in "yes, they must be thread safe". Sorry, wasn't clear.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: have I got to be careful about setting instance variables in Velocity Action subclasses?
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Neil Stevens" <ne...@firstlightassociates.co.uk> writes:
>do actions need to be thread safe? Are they pooled and reused?
Well, "pooled" might be the wrong word.. :-)
If you put
"modules.cache = true"
in your Properties, the loaders for Action, Layout, Navigation, Screen
and Page will keep references on the objects from these classes (which
does _not_ mean, that your templates will be cached! Just the classes
that render them. This is mainly interesting for the Action objects)
and their reuse. You can take a closer look at the ActionLoader class
for an example.
These classes are just glorified Hashtables. Even the sizing
parameters don't really change anything, they just adjust the initial
size of the hashtables.
Well, another "Fettecke". :-)
If you keep "modules.cache" off, then the class objects are reinstantiated
every time an Action is requested.
ActionLoader.getInstance()
calls getAssembler() from the AssemblerBrokerService, which gets the
Assembler (the Action) from the AssemblerBrokerService
("Assembler" is everything that "pulls parts together". A Screen is
an Assembler, a Page, Layout, Navigation and also an Action is. Yes,
the name sucks. Wasn't my idea. It is also an abstract Base Class
where an interface would have been better).
AssemblerBroker has for every "kind" of Assembler classes one or
more factories registered. For the Action, this ususally is
o.a.t.services.assemblerbroker.util.java.JavaActionFactory which just
looks for action.<xxx> in all the registered module packages. If
it finds a class it does Class.forName() on it.
Thread safe? Hm. I'd say no without caching and yes if caching is
activated. So make this a "yes".
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
have I got to be careful about setting instance variables in Velocity Action subclasses?
Posted by Neil Stevens <ne...@firstlightassociates.co.uk>.
do actions need to be thread safe? Are they pooled and reused?
N
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: changing the default html tags
Posted by Matt Koranda <ma...@orkan.no>.
I'll start on it tonight :)
Matt
----- Original Message -----
From: "Henning P. Schmiedehausen" <hp...@intermeta.de>
Newsgroups: hometree.jakarta.turbine.users
To: <tu...@jakarta.apache.org>
Sent: Tuesday, December 10, 2002 12:38 PM
Subject: Re: changing the default html tags
> "Matt Koranda" <ma...@orkan.no> writes:
>
> >Would you want to add more? Should I do it?
>
> Please. That's exactly the kind of volunteering that we're looking
> for. :-) I simply don't have the time to work through all the xdocs
> rules and formatting. If you can format this, I'd be more than happy
> to proof read it. I might whip up a simple skeleton service for
> inclusion with Turbine/TDK.
>
> Regards
> Henning
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
>
> Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
> D-91054 Buckenhof Fax.: 09131 / 50654-20
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: changing the default html tags
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Matt Koranda" <ma...@orkan.no> writes:
>Would you want to add more? Should I do it?
Please. That's exactly the kind of volunteering that we're looking
for. :-) I simply don't have the time to work through all the xdocs
rules and formatting. If you can format this, I'd be more than happy
to proof read it. I might whip up a simple skeleton service for
inclusion with Turbine/TDK.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: changing the default html tags
Posted by Matt Koranda <ma...@orkan.no>.
Nice explaination....This seems to be a pretty good start to a how-to or an
extension of the services section of the documentation, can you submit it?
Would you want to add more? Should I do it?
Matt
----- Original Message -----
From: "Henning P. Schmiedehausen" <hp...@intermeta.de>
Newsgroups: hometree.jakarta.turbine.users
To: <tu...@jakarta.apache.org>
Sent: Tuesday, December 10, 2002 11:37 AM
Subject: Re: changing the default html tags
> ramadevi <ra...@cmcltd.com> writes:
>
> >Hi,
> >Is it possible to create a new service apart from the services provided
> >by the turbine.
>
> Yes, sure. Simply extend TurbineBaseService. You must then add your
> service to the TurbineResources.properties like this:
>
> services.<xxx>.classname = <full class name of your service>
>
> and you're set.
>
> If you look at the examples of the simple services like
> db/TurbinePoolBrokerService or servlet/TurbineServletService you'll
> get on speed pretty fast.
>
> In a Nutshell:
>
> - You must not try to provide a C'tor with parameters, best is not to
> provide any C'tor at all, because nothing should be done at
> construction time (You'll get the default c'tor which is fine for us).
>
> - Your Service will be instantiated exactly once. So it must be
threadsafe,
> must not use class global variables for session-dependend information.
>
> - You should provide an init() method which is called when Turbine starts
> up and should initialized your service dependent code. There is lots
> of confusion of how this init() method should look like, I personally
> prefer the parameterless variant:
>
> public void init() throws InitializationException
> {
> }
>
> You must call setInit(true) if your service initializes correctly. Else
> no user of your service can find it. Right after this, your service
might
> be queried and used by other sessions, so you should not call setInit()
> prematurely.
>
> - You might provide a shutdown() method which is called when Turbine shuts
> down. You can clean up your internal data in this method. You should
call
> setInit(false) as the last thing in shutdown().
>
> - It is good style, that if you build the FooService, to provide:
>
> <yourpackage>.FooService.java with an Interface definition of your
> Service which extends
o.a.t.services.Service
> It should contain a constant SERVICE_NAME
> with the Turbine visible name of your
service.
>
> <yourpackage>.TurbineFooService.java which extends the
TurbineBaseService,
> implements FooService and provides
> the actual code
>
> <yourpackage>.TurbineFoo.java which contains static facade methods for
> your service along the following lines:
>
> public abstract class TurbineFoo
> {
> protected static FooService getService()
> {
> return (FooService) TurbineServices
> .getInstance().getService(FooService.SERVICE_NAME);
> }
>
> [...]
>
> public static void fooMethod1()
> {
> getService().fooMethod1();
> }
>
> public static int fooMethod2(int bar)
> {
> return getService().fooMethod2(bar);
> }
>
> [...]
> }
>
> to give users of your service the ability to simply write
>
> TurbineFoo.fooMethod1();
>
> in their code and not to care which actual Implementation of FooService
> is running.
>
> init() and shutdown() applies to Turbine 2.1/2.2 This might change
> with the lifecycle interfaces in a later release.
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
>
> Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
> D-91054 Buckenhof Fax.: 09131 / 50654-20
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: changing the default html tags
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
ramadevi <ra...@cmcltd.com> writes:
>Hi,
>Is it possible to create a new service apart from the services provided
>by the turbine.
Yes, sure. Simply extend TurbineBaseService. You must then add your
service to the TurbineResources.properties like this:
services.<xxx>.classname = <full class name of your service>
and you're set.
If you look at the examples of the simple services like
db/TurbinePoolBrokerService or servlet/TurbineServletService you'll
get on speed pretty fast.
In a Nutshell:
- You must not try to provide a C'tor with parameters, best is not to
provide any C'tor at all, because nothing should be done at
construction time (You'll get the default c'tor which is fine for us).
- Your Service will be instantiated exactly once. So it must be threadsafe,
must not use class global variables for session-dependend information.
- You should provide an init() method which is called when Turbine starts
up and should initialized your service dependent code. There is lots
of confusion of how this init() method should look like, I personally
prefer the parameterless variant:
public void init() throws InitializationException
{
}
You must call setInit(true) if your service initializes correctly. Else
no user of your service can find it. Right after this, your service might
be queried and used by other sessions, so you should not call setInit()
prematurely.
- You might provide a shutdown() method which is called when Turbine shuts
down. You can clean up your internal data in this method. You should call
setInit(false) as the last thing in shutdown().
- It is good style, that if you build the FooService, to provide:
<yourpackage>.FooService.java with an Interface definition of your
Service which extends o.a.t.services.Service
It should contain a constant SERVICE_NAME
with the Turbine visible name of your service.
<yourpackage>.TurbineFooService.java which extends the TurbineBaseService,
implements FooService and provides
the actual code
<yourpackage>.TurbineFoo.java which contains static facade methods for
your service along the following lines:
public abstract class TurbineFoo
{
protected static FooService getService()
{
return (FooService) TurbineServices
.getInstance().getService(FooService.SERVICE_NAME);
}
[...]
public static void fooMethod1()
{
getService().fooMethod1();
}
public static int fooMethod2(int bar)
{
return getService().fooMethod2(bar);
}
[...]
}
to give users of your service the ability to simply write
TurbineFoo.fooMethod1();
in their code and not to care which actual Implementation of FooService
is running.
init() and shutdown() applies to Turbine 2.1/2.2 This might change
with the lifecycle interfaces in a later release.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: changing the default html tags
Posted by Rodney Schneider <ro...@actf.com.au>.
On Tue, 10 Dec 2002 17:25, you wrote:
> Hi,
> Is it possible to create a new service apart from the services
> provided by the turbine.
>
> with regrds
> rama
This was answered very recently, please search the archives for
"services".
In short... Yes!
-- Rodney
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: changing the default html tags
Posted by ramadevi <ra...@cmcltd.com>.
Hi,
Is it possible to create a new service apart from the services provided
by the turbine.
with regrds
rama
Sam Joseph wrote:
>
> Hi
>
> I am trying to serve some hdml pages off turbine, however turbine
> defaults to an html page. I can't seem to find there this is set in the
> code, or templates. Can anyone point me to the right place.
>
> Thanks in advance.
>
> CHEERS> SAM
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: changing the default html tags
Posted by Matt Koranda <ma...@orkan.no>.
If I understand correctly you need to set VelocityOnlyLayout instead of
VelocityECSLayout and add the tags yourself in the layout files. Search the
archives for VelocityOnlyLayout.
HTH,
Matt
----- Original Message -----
From: "Sam Joseph" <ga...@yha.att.ne.jp>
To: <tu...@jakarta.apache.org>
Sent: Wednesday, December 04, 2002 4:33 AM
Subject: changing the default html tags
> Hi
>
> I am trying to serve some hdml pages off turbine, however turbine
> defaults to an html page. I can't seem to find there this is set in the
> code, or templates. Can anyone point me to the right place.
>
> Thanks in advance.
>
> CHEERS> SAM
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: changing the default html tags
Posted by Chris K Chew <ch...@fenetics.com>.
It is very easy. Try searching the archives for "VelocityOnlyLayout", you
should be able to answer all of your questions by reading the threads.
Good luck,
Chris
> -----Original Message-----
> From: Sam Joseph [mailto:gaijin@yha.att.ne.jp]
> Sent: Tuesday, December 03, 2002 8:34 PM
> To: turbine-user@jakarta.apache.org
> Subject: changing the default html tags
>
>
> Hi
>
> I am trying to serve some hdml pages off turbine, however turbine
> defaults to an html page. I can't seem to find there this is set in the
> code, or templates. Can anyone point me to the right place.
>
> Thanks in advance.
>
> CHEERS> SAM
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>