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 Riedl Juergen <Ju...@icn.siemens.de> on 2001/09/25 08:40:07 UTC
AW: Call Tree How To: index.jsp -> jetspeed.vm & Default.psml: ho
w does this work
Wow, this answer is perfect. One question is left:
o where is the jetspeed servlet located, and what is its name?
The only thing I found was the jetspeed.vm ( I expected someting like Jetspeed.jsp or jetspeed.class). I searched even in the sources to no avail. So the step from 3) to 4) is not clear to me.
Thanx in advance
Juergen
> -----Urspr> üngliche Nachricht-----
> Von: Paul Spencer [SMTP:paul@mikon.com]
> Gesendet am: Dienstag, 25. September 2001 03:51
> An: jetspeed-user@jakarta.apache.org
> Betreff: Re: Call Tree How To: index.jsp -> jetspeed.vm & Default.psml: how does this work
>
> Riedl,
> Note the following is based on the default configuration and the user
> requested the page http://www.myJetspeed.com/jetspeed
>
> 1) The request is redirected to index.jsp. Based on the
> <welcome-file-list> in web.xml
>
> 2) The request, index.jsp, is forwarded to /portal by index.jsp. Note
> this has nothing to do with the layout type.
>
> 3) The request, /portal, is passed to the jetspeed servlet. Based on
> the <servlet-mapping> in web.xml
>
> 4) The jetspeed servlet determines the media type and language from
> information provided by the browser in the http request.
>
> 5) Using the media type, language, and layout type (as defined in
> JetspeedResource.properties) the default.vm is located in the
> WEB-INF/templates/vm/layouts/html directory tree. See jetspeed.log,
> located in WEB-INF/log, to determine which default.vm is used
>
> 5) default.vm define the top, left, and bottom navigation bars in
> addition to $screen_placeholder. The contents for the navigation bars
> can be found in the WEB-INF/templates/vm/navigations/html tree.
> $screen_placeholder is populated using from the default.psml file
> located in WEB-INF/psml/anon/html directory tree. See jetspeed.log to
> determine which file are used.
>
> For logged in users, default.psml in step #5 is found in the
> WEB-INF/psml/user directory tree.
>
> The Velocity variables skin.*Class are translates in to a CSS class
> using appropriate skin registry entry, see skin.xreg and
> local-skin.xreg. The CSS class is defined in css/default.css.
>
> I am working on the Jetspeed documentation. Does this answer you
> questions?
>
> Paul Spencer
>
> Riedl Juergen wrote:
> >
> > Hi all,
> >
> > I really like to understand how jetspeed traverses all the VM files starting with the index.jsp. What I think to know:
> >
> > o in the web.xml file the link of index.jsp "portlet/" is redirected to "jetspeed"
> > o since the engine runs in VM mode, this shall redirect to jetspeed.vm instead of jetspeed.jsp
>
> >
> > But this is only the half story:
> > o someone calls default.psml
> >
> > Where is that specified ? I greped trough the conf directory, but this gives only little helt. Perhaps I overlooked something.
> >
> > In jetspeed.vm there is a lot of makro processing. Where can I find what is called e.g. for "$!{skin.PortletStyleClass}". First I thought that it is a class where in the path is skin or something else. But I didn't find anything.
> >
> > Maybe this is already documented, then please give me the pointer to it.
> >
> > Best Regards
> >
> > Juergen Riedl
> > >
> >
> > ---------------------------------------------------------------------
> > 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
Re: AW: Call Tree How To: index.jsp -> jetspeed.vm & Default.psml: how
does this work
Posted by Paul Spencer <pa...@mikon.com>.
Juergen,
The Jetspeed servlet is based on Turbine. In the WEB-INF/lib and
WEB-INF/classes directory trees you will find all of the entry points
used by Turbine and the other components include with Jetspeed. Steps 3
and 4 are performed inside the Jetspeed servlet, which includes
components from Turbine, Velocity, ECS, Xerces, Xalan,...
I suspect you are this does not fully answer your question. If you
really want understand how Jetspeed works, you will need to understand
how Turbine works, including how it interacts with external classes like
the ones provided by Jetspeed. Then you may want to learn Velocity.
As a side note, the Jetspeed log file may provide some clues on how, and
which, files are used.
Paul Spencer
Riedl Juergen wrote:
>
> Wow, this answer is perfect. One question is left:
>
> o where is the jetspeed servlet located, and what is its name?
>
> The only thing I found was the jetspeed.vm ( I expected someting like Jetspeed.jsp or jetspeed.class). I searched
even in the sources to no avail. So the step from 3) to 4) is not clear
to me.
>
> Thanx in advance
>
> Juergen
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: jsp screen loading
Posted by David Sean Taylor <da...@bluesunrise.com>.
----- Original Message -----
From: "Spike" <sp...@interspike.com>
To: <je...@jakarta.apache.org>
Sent: Tuesday, September 25, 2001 3:07 AM
Subject: jsp screen loading
> Greetings Jetspeed Users,
>
> This question is directed at those using a mix of velocity and jsp pages
in
> Jetspeed:
>
> Suppose you have a *.jsp portlet that contains links and/or buttons. When
a
> user clicks on one of these the action class for that portlet handles the
> submission. I understand how to call specific methods in the action
handler
> by appropriately naming the buttons but how does one load a new *.jsp
> screen?
Do you mean like, for ex., when the NewAccount screen is loaded:
http://www.bluesunrise.com/jetspeed/portal/template/NewAccount
this is a single template combined with the standard navigations
Specifically, from the action class we want to load a screen that is
> not a portlet. The *.jsp screen that loads should look similar to a
> maximized portlet but be just another *.jsp page with it's own action
class
> to handle submissions. We have been able to get a *.jsp page to load by
> setting the screen in the action class but the portlet frame is missing.
It
> seems there are a couple ways to do this but which is most appropriate
given
> the turbine/velocity template approach?
>
> One other question: How does one access RunData from inside a *.jsp page?
>
<% RunData rundata = (RunData)request.getAttribute("rundata"); %>
> Any direction, pointers to documentation or assistance is sincerely
> appreciated.
>
> Thanks all...
>
> ~spike
>
>
> ---------------------------------------------------------------------
> 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
jsp screen loading
Posted by Spike <sp...@interspike.com>.
Greetings Jetspeed Users,
This question is directed at those using a mix of velocity and jsp pages in
Jetspeed:
Suppose you have a *.jsp portlet that contains links and/or buttons. When a
user clicks on one of these the action class for that portlet handles the
submission. I understand how to call specific methods in the action handler
by appropriately naming the buttons but how does one load a new *.jsp
screen? Specifically, from the action class we want to load a screen that is
not a portlet. The *.jsp screen that loads should look similar to a
maximized portlet but be just another *.jsp page with it's own action class
to handle submissions. We have been able to get a *.jsp page to load by
setting the screen in the action class but the portlet frame is missing. It
seems there are a couple ways to do this but which is most appropriate given
the turbine/velocity template approach?
One other question: How does one access RunData from inside a *.jsp page?
Any direction, pointers to documentation or assistance is sincerely
appreciated.
Thanks all...
~spike
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org