You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Samuel Le Berrigaud <sa...@gmail.com> on 2005/03/31 10:29:05 UTC
Avalon component and avalon framework Startable interface
Hi all,
I moved from using Turbine 2.2 to Turbine 2.3.1 recently. I wanted to
make use of the avalon component service for my own components.
One of my components needs to be started after configuring and stopped
when the webapp application is undeployed. I so wanted to use the
org.apache.avalon.framework.activity.Startable interface.
The problem I have is that it seems that my component is stopped right
after it is looked up by the avalon component service of Turbine...
As anyone any idea of what I did wrong ? I tryed with the Disposable
interface as well, but "dispose" is called a the exact same moment,
right after "look up".
Thanks for your help,
SaM
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Avalon component and avalon framework Startable interface
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Samuel,
I plainly don't know what's going on - I suggest that you fire up the
debugger to see why the whole lifecycle is run ... :-)
Cheers,
Siegfried Goeschl
Samuel Le Berrigaud wrote:
>Hi Siegfried,
>
>I notice that too. And I used the code of the Torque Avalon Component
>to build my own. The only difference I see is that Torque avalon
>component also implements
>org.apache.avalon.framework.context.Contextualizable and
>org.apache.avalon.framework.thread.ThreadSafe
>
>I think everything else is quite the same... and be sure I looked
>twice (even more) !
>
>SaM
>
>On Thu, 31 Mar 2005 15:49:40 +0200, Siegfried Goeschl
><si...@it20one.at> wrote:
>
>
>>Hi Samuel,
>>
>>what makes me wonder is that your service runs through the complete
>>lifecycle while you are still within the early initialization of
>>TurbineAvalonComponentService. You are also using the
>>TorqueAvalonService which does not show the same behaviour but
>>TorqueComponent also dumps debug messages when running through the
>>Avalon Lifecycle. So what is the difference in configuring/accessing
>>your service versus Torque?
>>
>>Cheers,
>>
>>Siegfried Goeschl
>>
>>Samuel Le Berrigaud wrote:
>>
>>
>>
>>>Here is an extract of my logs. I have a log for each configure,
>>>initialize, start and stop methods...
>>>
>>>Tell me if you want more precision...
>>>
>>>SaM
>>>
>>>2005-03-31 09:38:39,780 [main] INFO
>>>apache.turbine.services.BaseServiceBroker - Start Initializing service
>>>(early): AvalonComponentService
>>>2005-03-31 09:38:40,618 [main] INFO
>>>turbine.services.avaloncomponent.TurbineAvalonComponentService -
>>>Lookup for Component org.apache.torque.avalon.Torque successful
>>>2005-03-31 09:38:41,014 [main] DEBUG
>>>engine.dialer.avalon.DialerComponent - configure()
>>>2005-03-31 09:38:41,049 [main] DEBUG
>>>engine.dialer.avalon.DialerComponent - initialize()
>>>2005-03-31 09:38:41,049 [main] DEBUG
>>>engine.dialer.avalon.DialerComponent - start()
>>>2005-03-31 09:38:41,049 [main] INFO
>>>notifier.engine.dialer.DialerManager - Starting the dialer manager...
>>>2005-03-31 09:38:41,052 [main] INFO
>>>notifier.engine.dialer.DialerManager - Started !
>>>2005-03-31 09:38:41,052 [main] INFO
>>>turbine.services.avaloncomponent.TurbineAvalonComponentService -
>>>Lookup for Component com.dexem.notifier.engine.dialer.avalon.Dialer
>>>successful
>>>2005-03-31 09:38:41,053 [main] DEBUG
>>>engine.dialer.avalon.DialerComponent - stop()
>>>2005-03-31 09:38:41,053 [main] INFO
>>>notifier.engine.dialer.DialerManager - Stopping the dialer manager ...
>>>2005-03-31 09:38:41,053 [main] INFO
>>>notifier.engine.dialer.DialerManager - Stopped !
>>>2005-03-31 09:38:41,053 [main] INFO
>>>apache.turbine.services.BaseServiceBroker - Finish Initializing
>>>service (early): AvalonComponentService
>>>
>>>On Thu, 31 Mar 2005 10:57:15 +0200, Siegfried Goeschl
>>><si...@it20one.at> wrote:
>>>
>>>
>>>
>>>
>>>>Hi Samuel,
>>>>
>>>>could you attach the debug output?!
>>>>
>>>>Cheers,
>>>>
>>>>Siegfried Goeschl
>>>>
>>>>Samuel Le Berrigaud wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Hi all,
>>>>>
>>>>>I moved from using Turbine 2.2 to Turbine 2.3.1 recently. I wanted to
>>>>>make use of the avalon component service for my own components.
>>>>>
>>>>>One of my components needs to be started after configuring and stopped
>>>>>when the webapp application is undeployed. I so wanted to use the
>>>>>org.apache.avalon.framework.activity.Startable interface.
>>>>>
>>>>>The problem I have is that it seems that my component is stopped right
>>>>>after it is looked up by the avalon component service of Turbine...
>>>>>
>>>>>As anyone any idea of what I did wrong ? I tryed with the Disposable
>>>>>interface as well, but "dispose" is called a the exact same moment,
>>>>>right after "look up".
>>>>>
>>>>>Thanks for your help,
>>>>>
>>>>>SaM
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>>>>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>>>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
>
Re: Avalon component and avalon framework Startable interface
Posted by Samuel Le Berrigaud <sa...@gmail.com>.
Hi Siegfried,
I notice that too. And I used the code of the Torque Avalon Component
to build my own. The only difference I see is that Torque avalon
component also implements
org.apache.avalon.framework.context.Contextualizable and
org.apache.avalon.framework.thread.ThreadSafe
I think everything else is quite the same... and be sure I looked
twice (even more) !
SaM
On Thu, 31 Mar 2005 15:49:40 +0200, Siegfried Goeschl
<si...@it20one.at> wrote:
> Hi Samuel,
>
> what makes me wonder is that your service runs through the complete
> lifecycle while you are still within the early initialization of
> TurbineAvalonComponentService. You are also using the
> TorqueAvalonService which does not show the same behaviour but
> TorqueComponent also dumps debug messages when running through the
> Avalon Lifecycle. So what is the difference in configuring/accessing
> your service versus Torque?
>
> Cheers,
>
> Siegfried Goeschl
>
> Samuel Le Berrigaud wrote:
>
> >Here is an extract of my logs. I have a log for each configure,
> >initialize, start and stop methods...
> >
> >Tell me if you want more precision...
> >
> >SaM
> >
> >2005-03-31 09:38:39,780 [main] INFO
> >apache.turbine.services.BaseServiceBroker - Start Initializing service
> >(early): AvalonComponentService
> >2005-03-31 09:38:40,618 [main] INFO
> >turbine.services.avaloncomponent.TurbineAvalonComponentService -
> >Lookup for Component org.apache.torque.avalon.Torque successful
> >2005-03-31 09:38:41,014 [main] DEBUG
> >engine.dialer.avalon.DialerComponent - configure()
> >2005-03-31 09:38:41,049 [main] DEBUG
> >engine.dialer.avalon.DialerComponent - initialize()
> >2005-03-31 09:38:41,049 [main] DEBUG
> >engine.dialer.avalon.DialerComponent - start()
> >2005-03-31 09:38:41,049 [main] INFO
> >notifier.engine.dialer.DialerManager - Starting the dialer manager...
> >2005-03-31 09:38:41,052 [main] INFO
> >notifier.engine.dialer.DialerManager - Started !
> >2005-03-31 09:38:41,052 [main] INFO
> >turbine.services.avaloncomponent.TurbineAvalonComponentService -
> >Lookup for Component com.dexem.notifier.engine.dialer.avalon.Dialer
> >successful
> >2005-03-31 09:38:41,053 [main] DEBUG
> >engine.dialer.avalon.DialerComponent - stop()
> >2005-03-31 09:38:41,053 [main] INFO
> >notifier.engine.dialer.DialerManager - Stopping the dialer manager ...
> >2005-03-31 09:38:41,053 [main] INFO
> >notifier.engine.dialer.DialerManager - Stopped !
> >2005-03-31 09:38:41,053 [main] INFO
> >apache.turbine.services.BaseServiceBroker - Finish Initializing
> >service (early): AvalonComponentService
> >
> >On Thu, 31 Mar 2005 10:57:15 +0200, Siegfried Goeschl
> ><si...@it20one.at> wrote:
> >
> >
> >>Hi Samuel,
> >>
> >>could you attach the debug output?!
> >>
> >>Cheers,
> >>
> >>Siegfried Goeschl
> >>
> >>Samuel Le Berrigaud wrote:
> >>
> >>
> >>
> >>>Hi all,
> >>>
> >>>I moved from using Turbine 2.2 to Turbine 2.3.1 recently. I wanted to
> >>>make use of the avalon component service for my own components.
> >>>
> >>>One of my components needs to be started after configuring and stopped
> >>>when the webapp application is undeployed. I so wanted to use the
> >>>org.apache.avalon.framework.activity.Startable interface.
> >>>
> >>>The problem I have is that it seems that my component is stopped right
> >>>after it is looked up by the avalon component service of Turbine...
> >>>
> >>>As anyone any idea of what I did wrong ? I tryed with the Disposable
> >>>interface as well, but "dispose" is called a the exact same moment,
> >>>right after "look up".
> >>>
> >>>Thanks for your help,
> >>>
> >>>SaM
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> >>>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >>
> >>
> >>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
> >
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Avalon component and avalon framework Startable interface
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Samuel,
what makes me wonder is that your service runs through the complete
lifecycle while you are still within the early initialization of
TurbineAvalonComponentService. You are also using the
TorqueAvalonService which does not show the same behaviour but
TorqueComponent also dumps debug messages when running through the
Avalon Lifecycle. So what is the difference in configuring/accessing
your service versus Torque?
Cheers,
Siegfried Goeschl
Samuel Le Berrigaud wrote:
>Here is an extract of my logs. I have a log for each configure,
>initialize, start and stop methods...
>
>Tell me if you want more precision...
>
>SaM
>
>2005-03-31 09:38:39,780 [main] INFO
>apache.turbine.services.BaseServiceBroker - Start Initializing service
>(early): AvalonComponentService
>2005-03-31 09:38:40,618 [main] INFO
>turbine.services.avaloncomponent.TurbineAvalonComponentService -
>Lookup for Component org.apache.torque.avalon.Torque successful
>2005-03-31 09:38:41,014 [main] DEBUG
>engine.dialer.avalon.DialerComponent - configure()
>2005-03-31 09:38:41,049 [main] DEBUG
>engine.dialer.avalon.DialerComponent - initialize()
>2005-03-31 09:38:41,049 [main] DEBUG
>engine.dialer.avalon.DialerComponent - start()
>2005-03-31 09:38:41,049 [main] INFO
>notifier.engine.dialer.DialerManager - Starting the dialer manager...
>2005-03-31 09:38:41,052 [main] INFO
>notifier.engine.dialer.DialerManager - Started !
>2005-03-31 09:38:41,052 [main] INFO
>turbine.services.avaloncomponent.TurbineAvalonComponentService -
>Lookup for Component com.dexem.notifier.engine.dialer.avalon.Dialer
>successful
>2005-03-31 09:38:41,053 [main] DEBUG
>engine.dialer.avalon.DialerComponent - stop()
>2005-03-31 09:38:41,053 [main] INFO
>notifier.engine.dialer.DialerManager - Stopping the dialer manager ...
>2005-03-31 09:38:41,053 [main] INFO
>notifier.engine.dialer.DialerManager - Stopped !
>2005-03-31 09:38:41,053 [main] INFO
>apache.turbine.services.BaseServiceBroker - Finish Initializing
>service (early): AvalonComponentService
>
>On Thu, 31 Mar 2005 10:57:15 +0200, Siegfried Goeschl
><si...@it20one.at> wrote:
>
>
>>Hi Samuel,
>>
>>could you attach the debug output?!
>>
>>Cheers,
>>
>>Siegfried Goeschl
>>
>>Samuel Le Berrigaud wrote:
>>
>>
>>
>>>Hi all,
>>>
>>>I moved from using Turbine 2.2 to Turbine 2.3.1 recently. I wanted to
>>>make use of the avalon component service for my own components.
>>>
>>>One of my components needs to be started after configuring and stopped
>>>when the webapp application is undeployed. I so wanted to use the
>>>org.apache.avalon.framework.activity.Startable interface.
>>>
>>>The problem I have is that it seems that my component is stopped right
>>>after it is looked up by the avalon component service of Turbine...
>>>
>>>As anyone any idea of what I did wrong ? I tryed with the Disposable
>>>interface as well, but "dispose" is called a the exact same moment,
>>>right after "look up".
>>>
>>>Thanks for your help,
>>>
>>>SaM
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>
>>
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
>
Re: Avalon component and avalon framework Startable interface
Posted by Samuel Le Berrigaud <sa...@gmail.com>.
Here is an extract of my logs. I have a log for each configure,
initialize, start and stop methods...
Tell me if you want more precision...
SaM
2005-03-31 09:38:39,780 [main] INFO
apache.turbine.services.BaseServiceBroker - Start Initializing service
(early): AvalonComponentService
2005-03-31 09:38:40,618 [main] INFO
turbine.services.avaloncomponent.TurbineAvalonComponentService -
Lookup for Component org.apache.torque.avalon.Torque successful
2005-03-31 09:38:41,014 [main] DEBUG
engine.dialer.avalon.DialerComponent - configure()
2005-03-31 09:38:41,049 [main] DEBUG
engine.dialer.avalon.DialerComponent - initialize()
2005-03-31 09:38:41,049 [main] DEBUG
engine.dialer.avalon.DialerComponent - start()
2005-03-31 09:38:41,049 [main] INFO
notifier.engine.dialer.DialerManager - Starting the dialer manager...
2005-03-31 09:38:41,052 [main] INFO
notifier.engine.dialer.DialerManager - Started !
2005-03-31 09:38:41,052 [main] INFO
turbine.services.avaloncomponent.TurbineAvalonComponentService -
Lookup for Component com.dexem.notifier.engine.dialer.avalon.Dialer
successful
2005-03-31 09:38:41,053 [main] DEBUG
engine.dialer.avalon.DialerComponent - stop()
2005-03-31 09:38:41,053 [main] INFO
notifier.engine.dialer.DialerManager - Stopping the dialer manager ...
2005-03-31 09:38:41,053 [main] INFO
notifier.engine.dialer.DialerManager - Stopped !
2005-03-31 09:38:41,053 [main] INFO
apache.turbine.services.BaseServiceBroker - Finish Initializing
service (early): AvalonComponentService
On Thu, 31 Mar 2005 10:57:15 +0200, Siegfried Goeschl
<si...@it20one.at> wrote:
> Hi Samuel,
>
> could you attach the debug output?!
>
> Cheers,
>
> Siegfried Goeschl
>
> Samuel Le Berrigaud wrote:
>
> >Hi all,
> >
> >I moved from using Turbine 2.2 to Turbine 2.3.1 recently. I wanted to
> >make use of the avalon component service for my own components.
> >
> >One of my components needs to be started after configuring and stopped
> >when the webapp application is undeployed. I so wanted to use the
> >org.apache.avalon.framework.activity.Startable interface.
> >
> >The problem I have is that it seems that my component is stopped right
> >after it is looked up by the avalon component service of Turbine...
> >
> >As anyone any idea of what I did wrong ? I tryed with the Disposable
> >interface as well, but "dispose" is called a the exact same moment,
> >right after "look up".
> >
> >Thanks for your help,
> >
> >SaM
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Avalon component and avalon framework Startable interface
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Samuel,
could you attach the debug output?!
Cheers,
Siegfried Goeschl
Samuel Le Berrigaud wrote:
>Hi all,
>
>I moved from using Turbine 2.2 to Turbine 2.3.1 recently. I wanted to
>make use of the avalon component service for my own components.
>
>One of my components needs to be started after configuring and stopped
>when the webapp application is undeployed. I so wanted to use the
>org.apache.avalon.framework.activity.Startable interface.
>
>The problem I have is that it seems that my component is stopped right
>after it is looked up by the avalon component service of Turbine...
>
>As anyone any idea of what I did wrong ? I tryed with the Disposable
>interface as well, but "dispose" is called a the exact same moment,
>right after "look up".
>
>Thanks for your help,
>
>SaM
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: Using frames in turbine
Posted by Tanveer Dhillon <ta...@secf.com>.
yeah thanks!
It works.
Tanveer
-----Original Message-----
From: Paulo Schlup Santos [mailto:paulo@isnet.com.br]
Sent: Thursday, March 31, 2005 7:09 PM
To: Turbine Users List
Subject: Re: Using frames in turbine
Hi Tanveer,
In a frames page, you can't have the <BODY> tags. It should look like this:
<html>
<head>
<title>Put a title here</title>
</head>
<frameset rows="20%,*">
<frame src="http://www.google.com" />
<frame src="http://www.yahoo.com" />
</frameset>
</html>
You should change your Velocity page so that it uses a different Layout,
without the "body" tag and probably add a title, because the title in
your sub-pages will not show anywhere.
I hope it helps...
Paulo Schlup Santos
Wiaxis.com mobile solutions
Tanveer Dhillon wrote:
>hi
>I have been able to use frames in velocity bt when i use them with turbine
>the same page stops working.
>I have a try.vm page havin the following code
>
><frameset rows="20%,*">
> <frame src="http://www.yahoo.com/" />
> <frame src="http://www.google.com/" />
></frameset>
>
>when i place it in my project directory helloworld it works if accessed
from
>the browser as
>http://localhost:8080/helloworld/try.vm
>
>but if i place it in the templates/screens directory and in the turbine
>resource properties file i add the following statement
>layout.default=VelocityOnlyLayout
>and change home page as template.homepage=Try.vm
>the frames dont appear in the browser
>If i view source fron the browser i get the following code
><html>
><head>
> <title></title>
> </head>
><body >
>
>
><frameset rows="20%,*">
> <frame src="http://www.google.com" />
> <frame src="http://www.yahoo.com" />
></frameset>
>
>
></body>
></html>
>can someone help?
>Am i missing to add something in the turbine resource properties file.
>thanks
>Tanveer
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Using frames in turbine
Posted by Paulo Schlup Santos <pa...@isnet.com.br>.
Hi Tanveer,
In a frames page, you can't have the <BODY> tags. It should look like this:
<html>
<head>
<title>Put a title here</title>
</head>
<frameset rows="20%,*">
<frame src="http://www.google.com" />
<frame src="http://www.yahoo.com" />
</frameset>
</html>
You should change your Velocity page so that it uses a different Layout,
without the "body" tag and probably add a title, because the title in
your sub-pages will not show anywhere.
I hope it helps...
Paulo Schlup Santos
Wiaxis.com mobile solutions
Tanveer Dhillon wrote:
>hi
>I have been able to use frames in velocity bt when i use them with turbine
>the same page stops working.
>I have a try.vm page havin the following code
>
><frameset rows="20%,*">
> <frame src="http://www.yahoo.com/" />
> <frame src="http://www.google.com/" />
></frameset>
>
>when i place it in my project directory helloworld it works if accessed from
>the browser as
>http://localhost:8080/helloworld/try.vm
>
>but if i place it in the templates/screens directory and in the turbine
>resource properties file i add the following statement
>layout.default=VelocityOnlyLayout
>and change home page as template.homepage=Try.vm
>the frames dont appear in the browser
>If i view source fron the browser i get the following code
><html>
><head>
> <title></title>
> </head>
><body >
>
>
><frameset rows="20%,*">
> <frame src="http://www.google.com" />
> <frame src="http://www.yahoo.com" />
></frameset>
>
>
></body>
></html>
>can someone help?
>Am i missing to add something in the turbine resource properties file.
>thanks
>Tanveer
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Using frames in turbine
Posted by Tanveer Dhillon <ta...@secf.com>.
hi
I have been able to use frames in velocity bt when i use them with turbine
the same page stops working.
I have a try.vm page havin the following code
<frameset rows="20%,*">
<frame src="http://www.yahoo.com/" />
<frame src="http://www.google.com/" />
</frameset>
when i place it in my project directory helloworld it works if accessed from
the browser as
http://localhost:8080/helloworld/try.vm
but if i place it in the templates/screens directory and in the turbine
resource properties file i add the following statement
layout.default=VelocityOnlyLayout
and change home page as template.homepage=Try.vm
the frames dont appear in the browser
If i view source fron the browser i get the following code
<html>
<head>
<title></title>
</head>
<body >
<frameset rows="20%,*">
<frame src="http://www.google.com" />
<frame src="http://www.yahoo.com" />
</frameset>
</body>
</html>
can someone help?
Am i missing to add something in the turbine resource properties file.
thanks
Tanveer
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org