You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by fmarcus <fm...@datacomm.bcit.ca> on 2001/06/21 02:35:19 UTC
Trouble with default framework settings in Turbine
I'm having problems getting started with Turbine. I'm attempting to
change the default screen that users see when first accessing the
web app by changing screen.homepage in tr.props to the name of the
screen template (Index.vm) I want loaded. However, it's still loading
the default Login. Index.vm is located in /templates/app/screens.
If I set Index.vm to be the default template for an invalid login
attempt, it loads. (Proving it can be found).
I've also attempted to change the default login action to MyLoginUser
located at /WEB-INF/classes/ca/bcit/cstwebproject/modules/actions and
Turbine is still loading the default LoginUser class.
Am I just missing something obvious here?
tdk version: 2.1 (I downloaded it from jakarta.apache.org/turbine this
morning)
- Frank.
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Trouble with default framework settings in Turbine
Posted by Scott Eade <se...@backstagetech.com.au>.
> I'm having problems getting started with Turbine. I'm attempting to
> change the default screen that users see when first accessing the
> web app by changing screen.homepage in tr.props to the name of the
> screen template (Index.vm) I want loaded. However, it's still loading
> the default Login. Index.vm is located in /templates/app/screens.
>
> If I set Index.vm to be the default template for an invalid login
> attempt, it loads. (Proving it can be found).
>
> I've also attempted to change the default login action to MyLoginUser
> located at /WEB-INF/classes/ca/bcit/cstwebproject/modules/actions and
> Turbine is still loading the default LoginUser class.
>
> Am I just missing something obvious here?
This is similar to the battle I have been fighting over the last
couple of days. I suggest you look at the code in
org.apache.newapp.modules.screens.SecureScreen.isAuthorised()
and
org.apache.turbine.modules.actions.LoginUser.doPerform()
These interact with the properties defined in TR.properties
to provide the behaviour you are interested in.
I think there may be a bug in LoginUser but I am not completely
sure - check one of my messages earlier today with the
subject "Frustrating Problem"
As you are using a different initial screen your problem may not
be exactly the same as mine, but I think this information may
be of some help to you.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Looking for Flux docs
Posted by Jason van Zyl <jv...@apache.org>.
On 6/26/01 6:08 PM, "Frank Marcus" <fm...@datacomm.bcit.ca> wrote:
> Thanks to Scott and Jason for helping with the layout stuff. The ball's
> rolling now :)
>
> I'm looking for some information on Flux. I gather from what I've been
> reading on the list that parts of Flux aren't fully implemented. Aside
> from the source code (which I'm currently reading through) is there
> another source of documentation on how to use/extend Flux? Also, am I
> correct in assuming that the FluxTool class is the main implementation
> class for Flux? Thanks!
Flux was originally written to try and stem the tide of questions
relating to security. It is fully functional, but beyond that it
doesn't provide many amenities. The searching and filtering are
still lacking and it's not terribly pleasing to the eye.
That being the case, there isn't much documentation. Flux
will probably change a little due to the fact that Martin
just checked in torque generated security classes.
Flux will eventually be documented in a book, but that's a way
off. For now I'd be glad to try and answer and questions and
any patches to Flux people want to make :-) John already has
helped flux a great deal by making a flux pull tool. So, yes
the FluxTool class is where all the logic is.
> - Frank
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Looking for Flux docs
Posted by Frank Marcus <fm...@datacomm.bcit.ca>.
Thanks to Scott and Jason for helping with the layout stuff. The ball's
rolling now :)
I'm looking for some information on Flux. I gather from what I've been
reading on the list that parts of Flux aren't fully implemented. Aside
from the source code (which I'm currently reading through) is there
another source of documentation on how to use/extend Flux? Also, am I
correct in assuming that the FluxTool class is the main implementation
class for Flux? Thanks!
- Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Trouble with default framework settings in Turbine
Posted by Frank Marcus <fm...@datacomm.bcit.ca>.
I appreciate your help. My deadline is approaching rapidly :)
Jason van Zyl wrote:
>
> When you generated the sample app you probably noticed that
>
> screen.homepage
>
> didn't have a value and that is intentional. If you want to change
> what the user sees after a successful login you change the
>
> template.homepage
>
> property. We should probably just remove the screen.homepage
> property all together.
>
I'm actually attempting to have a default screen load and make the login
screen accessible via a link. A requirement of the site is to have an
initial area that a user does not need to be logged into. I know I
could probably use a standalone jsp as the initial page, but I'd like to
stay in my template.
> > If I set Index.vm to be the default template for an invalid login
> > attempt, it loads. (Proving it can be found).
> >
> > I've also attempted to change the default login action to MyLoginUser
> > located at /WEB-INF/classes/ca/bcit/cstwebproject/modules/actions and
> > Turbine is still loading the default LoginUser class.
>
> Did you adjust the module.packages property and change the
> action.login property?
>
module.packages is assigned to ca.bcit.cstwebproject.modules. The
MyLoginUser class is located in
classes/ca/bcit/cstwebpage/modules/actions
Should I specifically reference the actions directory or the class name?
The action.login property has been set to MyLoginUser
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Trouble with default framework settings in Turbine
Posted by Jason van Zyl <jv...@apache.org>.
On 6/20/01 8:35 PM, "fmarcus" <fm...@datacomm.bcit.ca> wrote:
> I'm having problems getting started with Turbine. I'm attempting to
> change the default screen that users see when first accessing the
> web app by changing screen.homepage in tr.props to the name of the
> screen template (Index.vm) I want loaded. However, it's still loading
> the default Login. Index.vm is located in /templates/app/screens.
When you generated the sample app you probably noticed that
screen.homepage
didn't have a value and that is intentional. If you want to change
what the user sees after a successful login you change the
template.homepage
property. We should probably just remove the screen.homepage
property all together.
> If I set Index.vm to be the default template for an invalid login
> attempt, it loads. (Proving it can be found).
>
> I've also attempted to change the default login action to MyLoginUser
> located at /WEB-INF/classes/ca/bcit/cstwebproject/modules/actions and
> Turbine is still loading the default LoginUser class.
Did you adjust the module.packages property and change the
action.login property?
> Am I just missing something obvious here?
I imagine a combination of misconfiguration and misunderstanding.
I will try and simplify the configuration a bit.
> tdk version: 2.1 (I downloaded it from jakarta.apache.org/turbine this
> morning)
>
> - Frank.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
--
jvz.
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org