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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
