going outside of portal

[Scott W <sa...@yahoo.com>]

I am trying to call a jsp when the user clicks a
button.  The button is in a form and the
ACTION="test.jsp".  The jsp file is coming up
correctly, however the header, footer, and left nav
disappear and only the html from the jsp file is being
displayed.  I want the header, footer, and left nav to
remain and the html from the jsp be displayed in the
middle.  What do you think I am doing wrong?  Should I
be calling a psml from the ACTION instead of a jsp
file?

Thanks in advance,

Scott

__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

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

Re: going outside of portal

[Kimmo Eklund <ki...@profes.fi>]

Scott,

> I am trying to call a jsp when the user clicks a
> button.  The button is in a form and the
> ACTION="test.jsp".  The jsp file is coming up
> correctly, however the header, footer, and left nav
> disappear and only the html from the jsp file is being
> displayed.  I want the header, footer, and left nav to
> remain and the html from the jsp be displayed in the
> middle.  What do you think I am doing wrong?  Should I
> be calling a psml from the ACTION instead of a jsp
> file?

I'm quite newbie myself, but maybe I can give you a hint.. (This 
involves version 1.3a2)

You shouldn't try to forward request directly to JSP. Jetspeed is built 
on Turbine and you should get familiar with Turbine basic functions. One 
of them is the way Turbine constructs screen displayed to user.

First, there's RunData. Form data is automatically parsed to RunData. 
Secondly, When Turbine gets request, it is forwarded to an action which 
is given as parameter in request. RunData also includes methods to tell 
Turbine where to forward response. Unfortunately I don't have Turbine 
API at hand at the moment, so I can't give you accurate method names.

If you look at the Turbine, view is constructed from following elements:

page
layout
screen
navigation

Page has an layout which determines where different parts of screen is.
Navigations are elements that re.occur on many pages, the ones you are 
currently missing for example. Screen is the content.

Jetspeed comes with one layoyt, default.jsp. It's located in 
/WEB-INF/templates/jsp/layouts/html/default.jsp. Under 
/WEB-INF/templates/jsp are also all other Jetspeed 'screenparts'
Page is handled my Jetspeed in Jetspeed.. What a stupid sentence.. :) 
(it's Java-class, not JSP-file).

In your case you should set screen (RunData.set..) to JSP you wanted and 
turbine should do the rest.

There's more information about Turbine at http://jakarta.apache.org/turbine
http://jakarta.apache.org/turbine/fsd.html

It all may seem quite complicated when you are just trying to get 
something simple to work, but keep digging! In the end it's allways good 
to understand truly what's happening, rather than just get something to 
work somehow.. (I know, that's this job quite often is .. but still :))

Have a nice day!

/kimmo


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

1.3a2 vs 1.3a1

[Sony Joseph <so...@eself.com>]

Hi,

	When is the planned release for 1.3a2 ( I see only 1.3a1 in the download
site). Also, what the state of the project in CVS. Is it nearing any release
? What are the major feature enhancements/differences between 1.3a1 and
1.3a2 and the current one in CVS.

Thanks,
Sony


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