on 9/4/2000 9:45 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> Is this a mistake in WebMacroSiteScreen ?
>
> protected ConcreteElement doBuild(RunData data) throws Exception
> {
> return super.doBuild(data);
> }
>
> it has same signature as parent and just calls it's parent ?
read the code more closely. it is more complex than that. This is how I read
things working...I could be wrong in a couple places though as the code is
exceptionally difficult to follow. :-(
You write a class that extends WMSiteScreen and implements the
doBuildTemplate(data,context) method. Lets call that class "FooPage".
WMSiteScreen.doBuild(data) -> TemplateScreen.doBuild(data) ->
WMSiteScreen.doBuildTemplate(data) -> FooPage.doBuildTemplate(data, context)
When FooPage is done executing:
TemplateScreen.doBuild(data) executes WMSiteScreen.buildTemplate(data) and
returns the results.
Yes, it is complicated, but gives a HUGE amount of flexibility for FooPage
to override WMSiteScreen and TemplateScreen functionality while still
allowing code to auto-call itself. If you have a suggestion for how to make
this cleaner with the same amount of functionality, please suggest it.
thanks,
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
