You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by "Hohlfeld, Sven" <Sv...@OBIATOTTO.DE> on 2001/10/01 10:46:41 UTC

AW: JSP use in Jetspeed v1.3a2

Hello Scott,

I think the only thing you shoul do is to change

services.TemplateService.default.extension=vm to
services.TemplateService.default.extension=jsp 

in TRP. That worked with my configuration (tomcat322,
jetspeed13a2 and winnt40). There was only one
"little" problem: the customization portlet did not
work any more. I tried the same thing with the older
jetspeed 13a1 and there it worked. So something between 
the versions has changed that customize.jsp doesn't work
anymore. As you might know the jetspeed team strongly
recommends VM as standard templating mechanism.

I like jsp too but use VM as default template because
I need 13a2 (because email confirmation works there and
the customizer is much better, additionally the portlets
are more flexible - see webpageportlet for example). To
get JSP to work you should try to have a portlet that
is a JSP Portlet or a Webpageprotlet.
Now you can do whatever you want with your JSP's. Try doing
it with JSP Portlet directly within Jetspeed or do it with a link
to another servlet context withing tomcat or with JSPs handled
by tomcat but displayed within Jetspeed (webpageportlet).

I hope this helps you.

Sven Hohlfeld




-----Ursprüngliche Nachricht-----
Von: Scott A. Roehrig [mailto:saroehr@hotmail.com]
Gesendet: Samstag, 29. September 2001 16:18
An: jetspeed-user@jakarta.apache.org
Betreff: JSP use in Jetspeed v1.3a2


Has anyone had any success changing from vm templating to jsp in Jetspeed. I
have disabled the vm templating and changed the TurbineResources to the
following...

# Used to set the template homepage if you are using a template

# layout.

#

# Default: /Index.vm

template.homepage=/Home.jsp

# This is the default screen to show to people when they first access

# the system. Specify one of the template screens such as VelocityScreen

# to use a template system.

#

# Default: Login

#screen.homepage=

# This is the template that is shown on an incorrect login attempt.

# Setting this property will override any value of screen.login specfied

# below.

#

# Default: Login.vm

template.login=Login

# This is the page that is shown on an incorrect login attempt. It is

# referenced in the LoginUser action. Note that it will only be used if

# a login template has not been specified (see template.login above).

#

# Default: Login

#screen.login=Login

# This is the template that is used by the respective Template based

# ErrorScreen for displaying the error. If you are not using a Template
based

# ErrorScreen, then this is ignored.

#

# Default: /Error.vm

# for JSP templating use: Error.jsp

# for Velocity templating use: Error.vm

template.error=Error

# This is the default error screen.

#

# Default: VelocityErrorScreen

#screen.error=JspErrorScreen

# This is the screen that is displayed when the user's web page is in

# an invalid state.

#

# Default: error.InvalidState

screen.invalidstate=error.InvalidState

# Set the default Doctype. The default Doctype can be set by using

# the single strings: Html40Strict, Html40Transitional, or

# Html40Frameset. Additionally the default can be supplied as two

# strings separated by a comma giving the DTD and URI.

#

# Default: ignored if not set to some value.

default.doctype=Html40Transitional

# This is the default action to log a user in.

#dst action.login=LoginUser

action.login=JLoginUser

# This is the default action to log a user out.

action.logout=LogoutUser

# This is the default action to validate whether or not a session is

# valid. For example, if you want to make sure if a user has already

# logged in or not.

#

# Default: SessionValidator

#dst action.sessionvalidator=sessionvalidator.TemplateSessionValidator

action.sessionvalidator=JetspeedSessionValidator

# This is the timeout in seconds for sessions. If left commented out, the

# servlet container's default timeout will be left as is.

# session.timeout=1800

# This is the default action that builds up the AccessControlList for

# the individual users session.

action.accesscontroller=AccessController

When I access the initial page, it throws an exception...

/WEB-INF/templates/jsp/screens/Home.jsp Error processing ecs screen
'default'. See log for more information.

Nothing pertitent is logged. In addition, when I goto the login page, it
comes up fine, however when I log in it just returns me to the login page.
The default.psml file is being used as well.

Thoughts or suggestions welcome.

Thanks again.

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org

Re: JSP use in Jetspeed v1.3a2

Posted by "Scott A. Roehrig" <sa...@hotmail.com>.
Sven:

Yes, it is working now too. I had removed the vm templating service and
properties sections. As I mentioned, it was working with the build of the
overall pages and still is, but as you mentioned, looks like some or most of
the portlets use the vm templating.

I have no real preference between the two. Mostly my job required Java
skills and those I have. I was hoping to not learn another language per se.
In addition, I work extensively with the IBM portal and this leverages Java
at the core, so it works for me. I was using Jetspeed in the base sense to
learn more about the core engine.

I started with 1.3a1 on the learning curve and Jetspeed is really a great
product!

Scott
----- Original Message -----
From: "Hohlfeld, Sven" <Sv...@OBIATOTTO.DE>
To: <je...@jakarta.apache.org>
Sent: Monday, October 01, 2001 4:46 AM
Subject: AW: JSP use in Jetspeed v1.3a2



Hello Scott,

I think the only thing you shoul do is to change

services.TemplateService.default.extension=vm to
services.TemplateService.default.extension=jsp

in TRP. That worked with my configuration (tomcat322,
jetspeed13a2 and winnt40). There was only one
"little" problem: the customization portlet did not
work any more. I tried the same thing with the older
jetspeed 13a1 and there it worked. So something between
the versions has changed that customize.jsp doesn't work
anymore. As you might know the jetspeed team strongly
recommends VM as standard templating mechanism.

I like jsp too but use VM as default template because
I need 13a2 (because email confirmation works there and
the customizer is much better, additionally the portlets
are more flexible - see webpageportlet for example). To
get JSP to work you should try to have a portlet that
is a JSP Portlet or a Webpageprotlet.
Now you can do whatever you want with your JSP's. Try doing
it with JSP Portlet directly within Jetspeed or do it with a link
to another servlet context withing tomcat or with JSPs handled
by tomcat but displayed within Jetspeed (webpageportlet).

I hope this helps you.

Sven Hohlfeld




-----Ursprüngliche Nachricht-----
Von: Scott A. Roehrig [mailto:saroehr@hotmail.com]
Gesendet: Samstag, 29. September 2001 16:18
An: jetspeed-user@jakarta.apache.org
Betreff: JSP use in Jetspeed v1.3a2


Has anyone had any success changing from vm templating to jsp in Jetspeed. I
have disabled the vm templating and changed the TurbineResources to the
following...

# Used to set the template homepage if you are using a template

# layout.

#

# Default: /Index.vm

template.homepage=/Home.jsp

# This is the default screen to show to people when they first access

# the system. Specify one of the template screens such as VelocityScreen

# to use a template system.

#

# Default: Login

#screen.homepage=

# This is the template that is shown on an incorrect login attempt.

# Setting this property will override any value of screen.login specfied

# below.

#

# Default: Login.vm

template.login=Login

# This is the page that is shown on an incorrect login attempt. It is

# referenced in the LoginUser action. Note that it will only be used if

# a login template has not been specified (see template.login above).

#

# Default: Login

#screen.login=Login

# This is the template that is used by the respective Template based

# ErrorScreen for displaying the error. If you are not using a Template
based

# ErrorScreen, then this is ignored.

#

# Default: /Error.vm

# for JSP templating use: Error.jsp

# for Velocity templating use: Error.vm

template.error=Error

# This is the default error screen.

#

# Default: VelocityErrorScreen

#screen.error=JspErrorScreen

# This is the screen that is displayed when the user's web page is in

# an invalid state.

#

# Default: error.InvalidState

screen.invalidstate=error.InvalidState

# Set the default Doctype. The default Doctype can be set by using

# the single strings: Html40Strict, Html40Transitional, or

# Html40Frameset. Additionally the default can be supplied as two

# strings separated by a comma giving the DTD and URI.

#

# Default: ignored if not set to some value.

default.doctype=Html40Transitional

# This is the default action to log a user in.

#dst action.login=LoginUser

action.login=JLoginUser

# This is the default action to log a user out.

action.logout=LogoutUser

# This is the default action to validate whether or not a session is

# valid. For example, if you want to make sure if a user has already

# logged in or not.

#

# Default: SessionValidator

#dst action.sessionvalidator=sessionvalidator.TemplateSessionValidator

action.sessionvalidator=JetspeedSessionValidator

# This is the timeout in seconds for sessions. If left commented out, the

# servlet container's default timeout will be left as is.

# session.timeout=1800

# This is the default action that builds up the AccessControlList for

# the individual users session.

action.accesscontroller=AccessController

When I access the initial page, it throws an exception...

/WEB-INF/templates/jsp/screens/Home.jsp Error processing ecs screen
'default'. See log for more information.

Nothing pertitent is logged. In addition, when I goto the login page, it
comes up fine, however when I log in it just returns me to the login page.
The default.psml file is being used as well.

Thoughts or suggestions welcome.

Thanks again.

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org