Dan Diephouse wrote:
>
> I'm working on integrating flux into my turbine application, but
> I running into a little bit of a snag. The context is populated by
> "FluxScreen" class. The "Default" screen extends the "FluxScreen"
> class. My problem happens when I try to use flux and flux pulls the
> "Default" class from my application instead of flux's. That is, there
> are two default classes:
Yes, this is a problem that James found the other day too. I will fix
this
ASAP as soon as I get home. The easiest thing to do is probably make
Default
classes in each of the flux packages. This is what John did originally
when
he converted flux to a pull tool and I broke it. This will be fixed on
Friday when I get home. Sorry about that.
>
> org.apache.turbine.flux.modules.screens.Default
> org.compassarts.basecamp.modules.screens.Default
>
> and my apps "Default" class is always pulled. So I guess my question
> is: is it possible to set a different module package for a different
> template directory? I want /templates/flux to pull from
> org.apache.turbine.flux.modules and /templates/app to pull from
> org.compassarts.basecamp.modules. OR do I need to modify flux so it
> doesn't pull the "Default" class from my app?
>
> Thanks,
>
> Dan Diephouse
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://jakarta.apache.org/velocity
http://jakarta.apache.org/turbine
http://jakarta.apache.org/commons
http://tambora.zenplex.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
