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 Ron Wheeler <rw...@artifact-software.com> on 2003/08/07 06:23:26 UTC
master detail records displayed in a portlet
We are fairly new to Jetspeed and have made pretty good progress dispite the
documentation.
We are wondering how to create the following fairly common web page
structure.
We have three identical problems. List of case studies, list of white
papers, list of training courses.
In each case, we want to present the user with the list and when they click
on one of them, show them the details of that item.
The information is in one or more XML files. (list of items in one XML that
links to the many individual XML files containing the details of te item.)
The first problem is that we do not see how we can use separate portlets
since we only want either the list or one of the items on the screen at once
and we do not the menu to change while the user navigates within the topic.
If we use a single portlet, then we need to be able to respond to selection
of one item (a Case Study for example) by clearing the list and displaying
the selected document (the Case Study).
We have the xsl stylesheets to display the initial list and the details of
the idividual item.
1) Are we on the right track and understanding the problem in a reasonable
way?
2) Which portlet type would be the best way to handle this?
3) Does anyone have a model that we could see/use for this type of
application?
4) Should we be looking at Velocity/DVSL rather than XSLT if we are going to
work with Jetspeed?
Thanks for the help.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
AW: master detail records displayed in a portlet
Posted by Joachim Müller <jo...@wemove.com>.
maybe this would be a nice chapter for the docs:
tweaking jetspeed
...
joachim
> -----Ursprüngliche Nachricht-----
> Von: Carlos Orrego [mailto:orrego@inflexa.com]
> Gesendet: Donnerstag, 7. August 2003 17:24
> An: Jetspeed Users List; joachim@wemove.com
> Betreff: RE: master detail records displayed in a portlet
>
>
> i did a posting a couple of weeks back on how to configure jvm on win2k to get the most out of tomcat and jetspeed. Plus
> someone did
> a posting long back on jetspeed performance tips. With these tips, you can deploy a very powerful jetspeed implementation.
> if you can not find these posting, i will look them for you, but i have to run now
>
> c
>
> -----Original Message-----
> From: Joachim Müller [mailto:joachim@wemove.com]
> Sent: Thursday, August 07, 2003 11:12 AM
> To: Jetspeed Users List
> Subject: AW: master detail records displayed in a portlet
>
>
>
> Hi Carlos.
>
> Can you point out some of your server speed up
> configurations?
>
> thx, joachim
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Carlos Orrego [mailto:orrego@inflexa.com]
> > Gesendet: Donnerstag, 7. August 2003 17:07
> > An: Jetspeed Users List
> > Betreff: RE: master detail records displayed in a portlet
> >
> >
> > I use Jetspeed and Struts together all the time. I think both are inclrdible solutions, there is no problem in using both
> > together.
> > as for speed, my jetspeed implementations fly, you just need to be smart enough to configure our servers properly
> >
> > c
> >
> > -----Original Message-----
> > From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> > Sent: Thursday, August 07, 2003 10:53 AM
> > To: Jetspeed Users List
> > Subject: RE: master detail records displayed in a portlet
> >
> >
> >
> > Thanks
> > Was speed the main reason that you went Struts? We use Struts in our current
> > portal technology but I like the looks of Jetspeed.
> >
> > Ron
> >
> > -----Original Message-----
> > From: news [mailto:news@main.gmane.org]On Behalf Of Vic Cekvenich
> > Sent: Thursday, August 07, 2003 9:29 AM
> > To: jetspeed-user@jakarta.apache.org
> > Subject: Re: master detail records displayed in a portlet
> >
> >
> > I tried to do a few things with JetSlow, and then I went Struts. This is
> > using JSTL, not Velocity, but same concept, Struts supports Velocity.
> > Master detail processing is done all the time, and several working samples
> > are in there:
> > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> > /portlets/newsBlg/NewsBlgCmntsLst.jsp
> > Note that it using the core master tag and then iterating a list. This is
> > usnig nested beans. I think that is the key conecpt I recommend, nest beans
> > and then use dot notation to get to each of the 3 iterating
> > collections/beans.
> > So you can have one bean, that nests your 3 beans.
> > You can download and look at sample (or CVS source).
> >
> > Here is an example of how to click in, and get detail:
> > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> > /portlets/cms/ContentAdminLst.jsp
> >
> > KISS,
> >
> > .V
> >
> > ps:
> > And here is a navigation, but I do not think you asked for that:
> > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> > /config/navigation.xml
> >
> >
> >
> >
> > "D.S. Johnson" <ds...@insightbb.com> wrote in message
> > news:3F32424E.5060701@insightbb.com...
> > > Ron Wheeler wrote:
> > >
> > > >We are fairly new to Jetspeed and have made pretty good progress dispite
> > the
> > > >documentation.
> > > >
> > > >We are wondering how to create the following fairly common web page
> > > >structure.
> > > >We have three identical problems. List of case studies, list of white
> > > >papers, list of training courses.
> > > >In each case, we want to present the user with the list and when they
> > click
> > > >on one of them, show them the details of that item.
> > > >
> > > >The information is in one or more XML files. (list of items in one XML
> > that
> > > >links to the many individual XML files containing the details of te
> > item.)
> > > >
> > > >The first problem is that we do not see how we can use separate portlets
> > > >since we only want either the list or one of the items on the screen at
> > once
> > > >and we do not the menu to change while the user navigates within the
> > topic.
> > > >
> > > >If we use a single portlet, then we need to be able to respond to
> > selection
> > > >of one item (a Case Study for example) by clearing the list and
> > displaying
> > > >the selected document (the Case Study).
> > > >We have the xsl stylesheets to display the initial list and the details
> > of
> > > >the idividual item.
> > > >
> > > >1) Are we on the right track and understanding the problem in a
> > reasonable
> > > >way?
> > > >2) Which portlet type would be the best way to handle this?
> > > >3) Does anyone have a model that we could see/use for this type of
> > > >application?
> > > >4) Should we be looking at Velocity/DVSL rather than XSLT if we are going
> > to
> > > >work with Jetspeed?
> > > >
> > > >Thanks for the help.
> > > >
> > > >Ron
> > > >
> > > >
> > > >
> > > >
> > > >---------------------------------------------------------------------
> > > >To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> > > >For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> > > >
> > > >
> > > >
> > > >
> > > I don't use Velocity very much so I don't know if this will work for
> > > you. But, I have used java server pages and servlets to switch between
> > > pages in the same portlet. Usually, I create a menu and then based on
> > > the users choice I switch to that page in the portlet. Using links I
> > > can then switch between different pages in the same portlet, I believe
> > > this is what you want to do.
> > >
> > > What I do is create the initial jsp page which will have the logic for
> > > jumping to other pages. So the switch file would look something like this;
> > > I don't know if this is the best way but, it is a way to solve your
> > > problem, it has worked me.
> > >
> > >
> > > ## switch.jsp##
> > >
> > > <%@page language="java" import="java.sql.*"%>
> > > <%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
> > > prefix='jetspeed' %>
> > >
> > > <%
> > > // Create and get the switch val, this will be a val to decide on what
> > > page to load.
> > >
> > > String var_switchval =request.getParameter("switchval");
> > >
> > > // If switchval is null ( on first pass ) then load the main menu page
> > >
> > > if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
> > > == 0 ) {
> > >
> > > %>
> > >
> > > <%
> > >
> > > // Include the file with the menu code, this file will have HTML code
> > > and a parameter called switchval.
> > > // So in this included file you will need to create a parameter
> > > (switchval), setting this val will cause the other pages to be included
> > > // into switch.jsp
> > >
> > > // Example: <a href="?switchval=val_casestudies">
> > > // When this link is executed then the case studies page would be
> > > included and loaded.
> > > // You would want to add code for each page you want to switch to
> > >
> > > @ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
> > >
> > > %>
> > >
> > > <%
> > > }
> > > %>
> > >
> > > <%
> > > if ( var_switchval != null )
> > > if ( var_switchval.compareTo("val_casestudies") == 0 ) {
> > >
> > > %>
> > > <%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
> > >
> > > <%
> > > }
> > > %>
> > >
> > > <%
> > > if ( var_switchval != null )
> > > if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
> > >
> > > %>
> > > <%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
> > >
> > > <%
> > > }
> > > %>
> > >
> > >
> > > <%
> > > if ( var_switchval != null )
> > > if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
> > >
> > > %>
> > > <%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
> > >
> > > <%
> > > }
> > > %>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
>
RE: master detail records displayed in a portlet
Posted by Carlos Orrego <or...@inflexa.com>.
i did a posting a couple of weeks back on how to configure jvm on win2k to get the most out of tomcat and jetspeed. Plus someone did
a posting long back on jetspeed performance tips. With these tips, you can deploy a very powerful jetspeed implementation.
if you can not find these posting, i will look them for you, but i have to run now
c
-----Original Message-----
From: Joachim Müller [mailto:joachim@wemove.com]
Sent: Thursday, August 07, 2003 11:12 AM
To: Jetspeed Users List
Subject: AW: master detail records displayed in a portlet
Hi Carlos.
Can you point out some of your server speed up
configurations?
thx, joachim
> -----Ursprüngliche Nachricht-----
> Von: Carlos Orrego [mailto:orrego@inflexa.com]
> Gesendet: Donnerstag, 7. August 2003 17:07
> An: Jetspeed Users List
> Betreff: RE: master detail records displayed in a portlet
>
>
> I use Jetspeed and Struts together all the time. I think both are inclrdible solutions, there is no problem in using both
> together.
> as for speed, my jetspeed implementations fly, you just need to be smart enough to configure our servers properly
>
> c
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Thursday, August 07, 2003 10:53 AM
> To: Jetspeed Users List
> Subject: RE: master detail records displayed in a portlet
>
>
>
> Thanks
> Was speed the main reason that you went Struts? We use Struts in our current
> portal technology but I like the looks of Jetspeed.
>
> Ron
>
> -----Original Message-----
> From: news [mailto:news@main.gmane.org]On Behalf Of Vic Cekvenich
> Sent: Thursday, August 07, 2003 9:29 AM
> To: jetspeed-user@jakarta.apache.org
> Subject: Re: master detail records displayed in a portlet
>
>
> I tried to do a few things with JetSlow, and then I went Struts. This is
> using JSTL, not Velocity, but same concept, Struts supports Velocity.
> Master detail processing is done all the time, and several working samples
> are in there:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> /portlets/newsBlg/NewsBlgCmntsLst.jsp
> Note that it using the core master tag and then iterating a list. This is
> usnig nested beans. I think that is the key conecpt I recommend, nest beans
> and then use dot notation to get to each of the 3 iterating
> collections/beans.
> So you can have one bean, that nests your 3 beans.
> You can download and look at sample (or CVS source).
>
> Here is an example of how to click in, and get detail:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> /portlets/cms/ContentAdminLst.jsp
>
> KISS,
>
> .V
>
> ps:
> And here is a navigation, but I do not think you asked for that:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> /config/navigation.xml
>
>
>
>
> "D.S. Johnson" <ds...@insightbb.com> wrote in message
> news:3F32424E.5060701@insightbb.com...
> > Ron Wheeler wrote:
> >
> > >We are fairly new to Jetspeed and have made pretty good progress dispite
> the
> > >documentation.
> > >
> > >We are wondering how to create the following fairly common web page
> > >structure.
> > >We have three identical problems. List of case studies, list of white
> > >papers, list of training courses.
> > >In each case, we want to present the user with the list and when they
> click
> > >on one of them, show them the details of that item.
> > >
> > >The information is in one or more XML files. (list of items in one XML
> that
> > >links to the many individual XML files containing the details of te
> item.)
> > >
> > >The first problem is that we do not see how we can use separate portlets
> > >since we only want either the list or one of the items on the screen at
> once
> > >and we do not the menu to change while the user navigates within the
> topic.
> > >
> > >If we use a single portlet, then we need to be able to respond to
> selection
> > >of one item (a Case Study for example) by clearing the list and
> displaying
> > >the selected document (the Case Study).
> > >We have the xsl stylesheets to display the initial list and the details
> of
> > >the idividual item.
> > >
> > >1) Are we on the right track and understanding the problem in a
> reasonable
> > >way?
> > >2) Which portlet type would be the best way to handle this?
> > >3) Does anyone have a model that we could see/use for this type of
> > >application?
> > >4) Should we be looking at Velocity/DVSL rather than XSLT if we are going
> to
> > >work with Jetspeed?
> > >
> > >Thanks for the help.
> > >
> > >Ron
> > >
> > >
> > >
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> > >For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> > >
> > >
> > >
> > >
> > I don't use Velocity very much so I don't know if this will work for
> > you. But, I have used java server pages and servlets to switch between
> > pages in the same portlet. Usually, I create a menu and then based on
> > the users choice I switch to that page in the portlet. Using links I
> > can then switch between different pages in the same portlet, I believe
> > this is what you want to do.
> >
> > What I do is create the initial jsp page which will have the logic for
> > jumping to other pages. So the switch file would look something like this;
> > I don't know if this is the best way but, it is a way to solve your
> > problem, it has worked me.
> >
> >
> > ## switch.jsp##
> >
> > <%@page language="java" import="java.sql.*"%>
> > <%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
> > prefix='jetspeed' %>
> >
> > <%
> > // Create and get the switch val, this will be a val to decide on what
> > page to load.
> >
> > String var_switchval =request.getParameter("switchval");
> >
> > // If switchval is null ( on first pass ) then load the main menu page
> >
> > if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
> > == 0 ) {
> >
> > %>
> >
> > <%
> >
> > // Include the file with the menu code, this file will have HTML code
> > and a parameter called switchval.
> > // So in this included file you will need to create a parameter
> > (switchval), setting this val will cause the other pages to be included
> > // into switch.jsp
> >
> > // Example: <a href="?switchval=val_casestudies">
> > // When this link is executed then the case studies page would be
> > included and loaded.
> > // You would want to add code for each page you want to switch to
> >
> > @ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
> >
> > %>
> >
> > <%
> > }
> > %>
> >
> > <%
> > if ( var_switchval != null )
> > if ( var_switchval.compareTo("val_casestudies") == 0 ) {
> >
> > %>
> > <%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
> >
> > <%
> > }
> > %>
> >
> > <%
> > if ( var_switchval != null )
> > if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
> >
> > %>
> > <%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
> >
> > <%
> > }
> > %>
> >
> >
> > <%
> > if ( var_switchval != null )
> > if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
> >
> > %>
> > <%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
> >
> > <%
> > }
> > %>
>
>
>
>
> ---------------------------------------------------------------------
> 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
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
RE: master detail records displayed in a portlet
Posted by Carlos Orrego <or...@inflexa.com>.
i did a posting a couple of weeks back on how to configure jvm on win2k to get the most out of tomcat and jetspeed. Plus someone did
a posting long back on jetspeed performance tips. With these tips, you can deploy a very powerful jetspeed implementation.
if you can not find these posting, i will look them for you, but i have to run now
c
-----Original Message-----
From: Joachim Müller [mailto:joachim@wemove.com]
Sent: Thursday, August 07, 2003 11:12 AM
To: Jetspeed Users List
Subject: AW: master detail records displayed in a portlet
Hi Carlos.
Can you point out some of your server speed up
configurations?
thx, joachim
> -----Ursprüngliche Nachricht-----
> Von: Carlos Orrego [mailto:orrego@inflexa.com]
> Gesendet: Donnerstag, 7. August 2003 17:07
> An: Jetspeed Users List
> Betreff: RE: master detail records displayed in a portlet
>
>
> I use Jetspeed and Struts together all the time. I think both are inclrdible solutions, there is no problem in using both
> together.
> as for speed, my jetspeed implementations fly, you just need to be smart enough to configure our servers properly
>
> c
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Thursday, August 07, 2003 10:53 AM
> To: Jetspeed Users List
> Subject: RE: master detail records displayed in a portlet
>
>
>
> Thanks
> Was speed the main reason that you went Struts? We use Struts in our current
> portal technology but I like the looks of Jetspeed.
>
> Ron
>
> -----Original Message-----
> From: news [mailto:news@main.gmane.org]On Behalf Of Vic Cekvenich
> Sent: Thursday, August 07, 2003 9:29 AM
> To: jetspeed-user@jakarta.apache.org
> Subject: Re: master detail records displayed in a portlet
>
>
> I tried to do a few things with JetSlow, and then I went Struts. This is
> using JSTL, not Velocity, but same concept, Struts supports Velocity.
> Master detail processing is done all the time, and several working samples
> are in there:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> /portlets/newsBlg/NewsBlgCmntsLst.jsp
> Note that it using the core master tag and then iterating a list. This is
> usnig nested beans. I think that is the key conecpt I recommend, nest beans
> and then use dot notation to get to each of the 3 iterating
> collections/beans.
> So you can have one bean, that nests your 3 beans.
> You can download and look at sample (or CVS source).
>
> Here is an example of how to click in, and get detail:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> /portlets/cms/ContentAdminLst.jsp
>
> KISS,
>
> .V
>
> ps:
> And here is a navigation, but I do not think you asked for that:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> /config/navigation.xml
>
>
>
>
> "D.S. Johnson" <ds...@insightbb.com> wrote in message
> news:3F32424E.5060701@insightbb.com...
> > Ron Wheeler wrote:
> >
> > >We are fairly new to Jetspeed and have made pretty good progress dispite
> the
> > >documentation.
> > >
> > >We are wondering how to create the following fairly common web page
> > >structure.
> > >We have three identical problems. List of case studies, list of white
> > >papers, list of training courses.
> > >In each case, we want to present the user with the list and when they
> click
> > >on one of them, show them the details of that item.
> > >
> > >The information is in one or more XML files. (list of items in one XML
> that
> > >links to the many individual XML files containing the details of te
> item.)
> > >
> > >The first problem is that we do not see how we can use separate portlets
> > >since we only want either the list or one of the items on the screen at
> once
> > >and we do not the menu to change while the user navigates within the
> topic.
> > >
> > >If we use a single portlet, then we need to be able to respond to
> selection
> > >of one item (a Case Study for example) by clearing the list and
> displaying
> > >the selected document (the Case Study).
> > >We have the xsl stylesheets to display the initial list and the details
> of
> > >the idividual item.
> > >
> > >1) Are we on the right track and understanding the problem in a
> reasonable
> > >way?
> > >2) Which portlet type would be the best way to handle this?
> > >3) Does anyone have a model that we could see/use for this type of
> > >application?
> > >4) Should we be looking at Velocity/DVSL rather than XSLT if we are going
> to
> > >work with Jetspeed?
> > >
> > >Thanks for the help.
> > >
> > >Ron
> > >
> > >
> > >
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> > >For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> > >
> > >
> > >
> > >
> > I don't use Velocity very much so I don't know if this will work for
> > you. But, I have used java server pages and servlets to switch between
> > pages in the same portlet. Usually, I create a menu and then based on
> > the users choice I switch to that page in the portlet. Using links I
> > can then switch between different pages in the same portlet, I believe
> > this is what you want to do.
> >
> > What I do is create the initial jsp page which will have the logic for
> > jumping to other pages. So the switch file would look something like this;
> > I don't know if this is the best way but, it is a way to solve your
> > problem, it has worked me.
> >
> >
> > ## switch.jsp##
> >
> > <%@page language="java" import="java.sql.*"%>
> > <%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
> > prefix='jetspeed' %>
> >
> > <%
> > // Create and get the switch val, this will be a val to decide on what
> > page to load.
> >
> > String var_switchval =request.getParameter("switchval");
> >
> > // If switchval is null ( on first pass ) then load the main menu page
> >
> > if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
> > == 0 ) {
> >
> > %>
> >
> > <%
> >
> > // Include the file with the menu code, this file will have HTML code
> > and a parameter called switchval.
> > // So in this included file you will need to create a parameter
> > (switchval), setting this val will cause the other pages to be included
> > // into switch.jsp
> >
> > // Example: <a href="?switchval=val_casestudies">
> > // When this link is executed then the case studies page would be
> > included and loaded.
> > // You would want to add code for each page you want to switch to
> >
> > @ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
> >
> > %>
> >
> > <%
> > }
> > %>
> >
> > <%
> > if ( var_switchval != null )
> > if ( var_switchval.compareTo("val_casestudies") == 0 ) {
> >
> > %>
> > <%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
> >
> > <%
> > }
> > %>
> >
> > <%
> > if ( var_switchval != null )
> > if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
> >
> > %>
> > <%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
> >
> > <%
> > }
> > %>
> >
> >
> > <%
> > if ( var_switchval != null )
> > if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
> >
> > %>
> > <%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
> >
> > <%
> > }
> > %>
>
>
>
>
> ---------------------------------------------------------------------
> 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
>
>
>
AW: master detail records displayed in a portlet
Posted by Joachim Müller <jo...@wemove.com>.
Hi Carlos.
Can you point out some of your server speed up
configurations?
thx, joachim
> -----Ursprüngliche Nachricht-----
> Von: Carlos Orrego [mailto:orrego@inflexa.com]
> Gesendet: Donnerstag, 7. August 2003 17:07
> An: Jetspeed Users List
> Betreff: RE: master detail records displayed in a portlet
>
>
> I use Jetspeed and Struts together all the time. I think both are inclrdible solutions, there is no problem in using both
> together.
> as for speed, my jetspeed implementations fly, you just need to be smart enough to configure our servers properly
>
> c
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Thursday, August 07, 2003 10:53 AM
> To: Jetspeed Users List
> Subject: RE: master detail records displayed in a portlet
>
>
>
> Thanks
> Was speed the main reason that you went Struts? We use Struts in our current
> portal technology but I like the looks of Jetspeed.
>
> Ron
>
> -----Original Message-----
> From: news [mailto:news@main.gmane.org]On Behalf Of Vic Cekvenich
> Sent: Thursday, August 07, 2003 9:29 AM
> To: jetspeed-user@jakarta.apache.org
> Subject: Re: master detail records displayed in a portlet
>
>
> I tried to do a few things with JetSlow, and then I went Struts. This is
> using JSTL, not Velocity, but same concept, Struts supports Velocity.
> Master detail processing is done all the time, and several working samples
> are in there:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> /portlets/newsBlg/NewsBlgCmntsLst.jsp
> Note that it using the core master tag and then iterating a list. This is
> usnig nested beans. I think that is the key conecpt I recommend, nest beans
> and then use dot notation to get to each of the 3 iterating
> collections/beans.
> So you can have one bean, that nests your 3 beans.
> You can download and look at sample (or CVS source).
>
> Here is an example of how to click in, and get detail:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> /portlets/cms/ContentAdminLst.jsp
>
> KISS,
>
> .V
>
> ps:
> And here is a navigation, but I do not think you asked for that:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
> /config/navigation.xml
>
>
>
>
> "D.S. Johnson" <ds...@insightbb.com> wrote in message
> news:3F32424E.5060701@insightbb.com...
> > Ron Wheeler wrote:
> >
> > >We are fairly new to Jetspeed and have made pretty good progress dispite
> the
> > >documentation.
> > >
> > >We are wondering how to create the following fairly common web page
> > >structure.
> > >We have three identical problems. List of case studies, list of white
> > >papers, list of training courses.
> > >In each case, we want to present the user with the list and when they
> click
> > >on one of them, show them the details of that item.
> > >
> > >The information is in one or more XML files. (list of items in one XML
> that
> > >links to the many individual XML files containing the details of te
> item.)
> > >
> > >The first problem is that we do not see how we can use separate portlets
> > >since we only want either the list or one of the items on the screen at
> once
> > >and we do not the menu to change while the user navigates within the
> topic.
> > >
> > >If we use a single portlet, then we need to be able to respond to
> selection
> > >of one item (a Case Study for example) by clearing the list and
> displaying
> > >the selected document (the Case Study).
> > >We have the xsl stylesheets to display the initial list and the details
> of
> > >the idividual item.
> > >
> > >1) Are we on the right track and understanding the problem in a
> reasonable
> > >way?
> > >2) Which portlet type would be the best way to handle this?
> > >3) Does anyone have a model that we could see/use for this type of
> > >application?
> > >4) Should we be looking at Velocity/DVSL rather than XSLT if we are going
> to
> > >work with Jetspeed?
> > >
> > >Thanks for the help.
> > >
> > >Ron
> > >
> > >
> > >
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> > >For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> > >
> > >
> > >
> > >
> > I don't use Velocity very much so I don't know if this will work for
> > you. But, I have used java server pages and servlets to switch between
> > pages in the same portlet. Usually, I create a menu and then based on
> > the users choice I switch to that page in the portlet. Using links I
> > can then switch between different pages in the same portlet, I believe
> > this is what you want to do.
> >
> > What I do is create the initial jsp page which will have the logic for
> > jumping to other pages. So the switch file would look something like this;
> > I don't know if this is the best way but, it is a way to solve your
> > problem, it has worked me.
> >
> >
> > ## switch.jsp##
> >
> > <%@page language="java" import="java.sql.*"%>
> > <%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
> > prefix='jetspeed' %>
> >
> > <%
> > // Create and get the switch val, this will be a val to decide on what
> > page to load.
> >
> > String var_switchval =request.getParameter("switchval");
> >
> > // If switchval is null ( on first pass ) then load the main menu page
> >
> > if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
> > == 0 ) {
> >
> > %>
> >
> > <%
> >
> > // Include the file with the menu code, this file will have HTML code
> > and a parameter called switchval.
> > // So in this included file you will need to create a parameter
> > (switchval), setting this val will cause the other pages to be included
> > // into switch.jsp
> >
> > // Example: <a href="?switchval=val_casestudies">
> > // When this link is executed then the case studies page would be
> > included and loaded.
> > // You would want to add code for each page you want to switch to
> >
> > @ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
> >
> > %>
> >
> > <%
> > }
> > %>
> >
> > <%
> > if ( var_switchval != null )
> > if ( var_switchval.compareTo("val_casestudies") == 0 ) {
> >
> > %>
> > <%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
> >
> > <%
> > }
> > %>
> >
> > <%
> > if ( var_switchval != null )
> > if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
> >
> > %>
> > <%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
> >
> > <%
> > }
> > %>
> >
> >
> > <%
> > if ( var_switchval != null )
> > if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
> >
> > %>
> > <%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
> >
> > <%
> > }
> > %>
>
>
>
>
> ---------------------------------------------------------------------
> 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: master detail records displayed in a portlet
Posted by Carlos Orrego <or...@inflexa.com>.
I use Jetspeed and Struts together all the time. I think both are inclrdible solutions, there is no problem in using both together.
as for speed, my jetspeed implementations fly, you just need to be smart enough to configure our servers properly
c
-----Original Message-----
From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
Sent: Thursday, August 07, 2003 10:53 AM
To: Jetspeed Users List
Subject: RE: master detail records displayed in a portlet
Thanks
Was speed the main reason that you went Struts? We use Struts in our current
portal technology but I like the looks of Jetspeed.
Ron
-----Original Message-----
From: news [mailto:news@main.gmane.org]On Behalf Of Vic Cekvenich
Sent: Thursday, August 07, 2003 9:29 AM
To: jetspeed-user@jakarta.apache.org
Subject: Re: master detail records displayed in a portlet
I tried to do a few things with JetSlow, and then I went Struts. This is
using JSTL, not Velocity, but same concept, Struts supports Velocity.
Master detail processing is done all the time, and several working samples
are in there:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/portlets/newsBlg/NewsBlgCmntsLst.jsp
Note that it using the core master tag and then iterating a list. This is
usnig nested beans. I think that is the key conecpt I recommend, nest beans
and then use dot notation to get to each of the 3 iterating
collections/beans.
So you can have one bean, that nests your 3 beans.
You can download and look at sample (or CVS source).
Here is an example of how to click in, and get detail:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/portlets/cms/ContentAdminLst.jsp
KISS,
.V
ps:
And here is a navigation, but I do not think you asked for that:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/config/navigation.xml
"D.S. Johnson" <ds...@insightbb.com> wrote in message
news:3F32424E.5060701@insightbb.com...
> Ron Wheeler wrote:
>
> >We are fairly new to Jetspeed and have made pretty good progress dispite
the
> >documentation.
> >
> >We are wondering how to create the following fairly common web page
> >structure.
> >We have three identical problems. List of case studies, list of white
> >papers, list of training courses.
> >In each case, we want to present the user with the list and when they
click
> >on one of them, show them the details of that item.
> >
> >The information is in one or more XML files. (list of items in one XML
that
> >links to the many individual XML files containing the details of te
item.)
> >
> >The first problem is that we do not see how we can use separate portlets
> >since we only want either the list or one of the items on the screen at
once
> >and we do not the menu to change while the user navigates within the
topic.
> >
> >If we use a single portlet, then we need to be able to respond to
selection
> >of one item (a Case Study for example) by clearing the list and
displaying
> >the selected document (the Case Study).
> >We have the xsl stylesheets to display the initial list and the details
of
> >the idividual item.
> >
> >1) Are we on the right track and understanding the problem in a
reasonable
> >way?
> >2) Which portlet type would be the best way to handle this?
> >3) Does anyone have a model that we could see/use for this type of
> >application?
> >4) Should we be looking at Velocity/DVSL rather than XSLT if we are going
to
> >work with Jetspeed?
> >
> >Thanks for the help.
> >
> >Ron
> >
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> >
> >
> >
> >
> I don't use Velocity very much so I don't know if this will work for
> you. But, I have used java server pages and servlets to switch between
> pages in the same portlet. Usually, I create a menu and then based on
> the users choice I switch to that page in the portlet. Using links I
> can then switch between different pages in the same portlet, I believe
> this is what you want to do.
>
> What I do is create the initial jsp page which will have the logic for
> jumping to other pages. So the switch file would look something like this;
> I don't know if this is the best way but, it is a way to solve your
> problem, it has worked me.
>
>
> ## switch.jsp##
>
> <%@page language="java" import="java.sql.*"%>
> <%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
> prefix='jetspeed' %>
>
> <%
> // Create and get the switch val, this will be a val to decide on what
> page to load.
>
> String var_switchval =request.getParameter("switchval");
>
> // If switchval is null ( on first pass ) then load the main menu page
>
> if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
> == 0 ) {
>
> %>
>
> <%
>
> // Include the file with the menu code, this file will have HTML code
> and a parameter called switchval.
> // So in this included file you will need to create a parameter
> (switchval), setting this val will cause the other pages to be included
> // into switch.jsp
>
> // Example: <a href="?switchval=val_casestudies">
> // When this link is executed then the case studies page would be
> included and loaded.
> // You would want to add code for each page you want to switch to
>
> @ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
>
> %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_casestudies") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
>
> <%
> }
> %>
>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
>
> <%
> }
> %>
---------------------------------------------------------------------
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: master detail records displayed in a portlet
Posted by Carlos Orrego <or...@inflexa.com>.
I use Jetspeed and Struts together all the time. I think both are inclrdible solutions, there is no problem in using both together.
as for speed, my jetspeed implementations fly, you just need to be smart enough to configure our servers properly
c
-----Original Message-----
From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
Sent: Thursday, August 07, 2003 10:53 AM
To: Jetspeed Users List
Subject: RE: master detail records displayed in a portlet
Thanks
Was speed the main reason that you went Struts? We use Struts in our current
portal technology but I like the looks of Jetspeed.
Ron
-----Original Message-----
From: news [mailto:news@main.gmane.org]On Behalf Of Vic Cekvenich
Sent: Thursday, August 07, 2003 9:29 AM
To: jetspeed-user@jakarta.apache.org
Subject: Re: master detail records displayed in a portlet
I tried to do a few things with JetSlow, and then I went Struts. This is
using JSTL, not Velocity, but same concept, Struts supports Velocity.
Master detail processing is done all the time, and several working samples
are in there:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/portlets/newsBlg/NewsBlgCmntsLst.jsp
Note that it using the core master tag and then iterating a list. This is
usnig nested beans. I think that is the key conecpt I recommend, nest beans
and then use dot notation to get to each of the 3 iterating
collections/beans.
So you can have one bean, that nests your 3 beans.
You can download and look at sample (or CVS source).
Here is an example of how to click in, and get detail:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/portlets/cms/ContentAdminLst.jsp
KISS,
.V
ps:
And here is a navigation, but I do not think you asked for that:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/config/navigation.xml
"D.S. Johnson" <ds...@insightbb.com> wrote in message
news:3F32424E.5060701@insightbb.com...
> Ron Wheeler wrote:
>
> >We are fairly new to Jetspeed and have made pretty good progress dispite
the
> >documentation.
> >
> >We are wondering how to create the following fairly common web page
> >structure.
> >We have three identical problems. List of case studies, list of white
> >papers, list of training courses.
> >In each case, we want to present the user with the list and when they
click
> >on one of them, show them the details of that item.
> >
> >The information is in one or more XML files. (list of items in one XML
that
> >links to the many individual XML files containing the details of te
item.)
> >
> >The first problem is that we do not see how we can use separate portlets
> >since we only want either the list or one of the items on the screen at
once
> >and we do not the menu to change while the user navigates within the
topic.
> >
> >If we use a single portlet, then we need to be able to respond to
selection
> >of one item (a Case Study for example) by clearing the list and
displaying
> >the selected document (the Case Study).
> >We have the xsl stylesheets to display the initial list and the details
of
> >the idividual item.
> >
> >1) Are we on the right track and understanding the problem in a
reasonable
> >way?
> >2) Which portlet type would be the best way to handle this?
> >3) Does anyone have a model that we could see/use for this type of
> >application?
> >4) Should we be looking at Velocity/DVSL rather than XSLT if we are going
to
> >work with Jetspeed?
> >
> >Thanks for the help.
> >
> >Ron
> >
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> >
> >
> >
> >
> I don't use Velocity very much so I don't know if this will work for
> you. But, I have used java server pages and servlets to switch between
> pages in the same portlet. Usually, I create a menu and then based on
> the users choice I switch to that page in the portlet. Using links I
> can then switch between different pages in the same portlet, I believe
> this is what you want to do.
>
> What I do is create the initial jsp page which will have the logic for
> jumping to other pages. So the switch file would look something like this;
> I don't know if this is the best way but, it is a way to solve your
> problem, it has worked me.
>
>
> ## switch.jsp##
>
> <%@page language="java" import="java.sql.*"%>
> <%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
> prefix='jetspeed' %>
>
> <%
> // Create and get the switch val, this will be a val to decide on what
> page to load.
>
> String var_switchval =request.getParameter("switchval");
>
> // If switchval is null ( on first pass ) then load the main menu page
>
> if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
> == 0 ) {
>
> %>
>
> <%
>
> // Include the file with the menu code, this file will have HTML code
> and a parameter called switchval.
> // So in this included file you will need to create a parameter
> (switchval), setting this val will cause the other pages to be included
> // into switch.jsp
>
> // Example: <a href="?switchval=val_casestudies">
> // When this link is executed then the case studies page would be
> included and loaded.
> // You would want to add code for each page you want to switch to
>
> @ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
>
> %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_casestudies") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
>
> <%
> }
> %>
>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
>
> <%
> }
> %>
---------------------------------------------------------------------
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: master detail records displayed in a portlet
Posted by Ron Wheeler <rw...@artifact-software.com>.
Thanks
Was speed the main reason that you went Struts? We use Struts in our current
portal technology but I like the looks of Jetspeed.
Ron
-----Original Message-----
From: news [mailto:news@main.gmane.org]On Behalf Of Vic Cekvenich
Sent: Thursday, August 07, 2003 9:29 AM
To: jetspeed-user@jakarta.apache.org
Subject: Re: master detail records displayed in a portlet
I tried to do a few things with JetSlow, and then I went Struts. This is
using JSTL, not Velocity, but same concept, Struts supports Velocity.
Master detail processing is done all the time, and several working samples
are in there:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/portlets/newsBlg/NewsBlgCmntsLst.jsp
Note that it using the core master tag and then iterating a list. This is
usnig nested beans. I think that is the key conecpt I recommend, nest beans
and then use dot notation to get to each of the 3 iterating
collections/beans.
So you can have one bean, that nests your 3 beans.
You can download and look at sample (or CVS source).
Here is an example of how to click in, and get detail:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/portlets/cms/ContentAdminLst.jsp
KISS,
.V
ps:
And here is a navigation, but I do not think you asked for that:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/config/navigation.xml
"D.S. Johnson" <ds...@insightbb.com> wrote in message
news:3F32424E.5060701@insightbb.com...
> Ron Wheeler wrote:
>
> >We are fairly new to Jetspeed and have made pretty good progress dispite
the
> >documentation.
> >
> >We are wondering how to create the following fairly common web page
> >structure.
> >We have three identical problems. List of case studies, list of white
> >papers, list of training courses.
> >In each case, we want to present the user with the list and when they
click
> >on one of them, show them the details of that item.
> >
> >The information is in one or more XML files. (list of items in one XML
that
> >links to the many individual XML files containing the details of te
item.)
> >
> >The first problem is that we do not see how we can use separate portlets
> >since we only want either the list or one of the items on the screen at
once
> >and we do not the menu to change while the user navigates within the
topic.
> >
> >If we use a single portlet, then we need to be able to respond to
selection
> >of one item (a Case Study for example) by clearing the list and
displaying
> >the selected document (the Case Study).
> >We have the xsl stylesheets to display the initial list and the details
of
> >the idividual item.
> >
> >1) Are we on the right track and understanding the problem in a
reasonable
> >way?
> >2) Which portlet type would be the best way to handle this?
> >3) Does anyone have a model that we could see/use for this type of
> >application?
> >4) Should we be looking at Velocity/DVSL rather than XSLT if we are going
to
> >work with Jetspeed?
> >
> >Thanks for the help.
> >
> >Ron
> >
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> >
> >
> >
> >
> I don't use Velocity very much so I don't know if this will work for
> you. But, I have used java server pages and servlets to switch between
> pages in the same portlet. Usually, I create a menu and then based on
> the users choice I switch to that page in the portlet. Using links I
> can then switch between different pages in the same portlet, I believe
> this is what you want to do.
>
> What I do is create the initial jsp page which will have the logic for
> jumping to other pages. So the switch file would look something like this;
> I don't know if this is the best way but, it is a way to solve your
> problem, it has worked me.
>
>
> ## switch.jsp##
>
> <%@page language="java" import="java.sql.*"%>
> <%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
> prefix='jetspeed' %>
>
> <%
> // Create and get the switch val, this will be a val to decide on what
> page to load.
>
> String var_switchval =request.getParameter("switchval");
>
> // If switchval is null ( on first pass ) then load the main menu page
>
> if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
> == 0 ) {
>
> %>
>
> <%
>
> // Include the file with the menu code, this file will have HTML code
> and a parameter called switchval.
> // So in this included file you will need to create a parameter
> (switchval), setting this val will cause the other pages to be included
> // into switch.jsp
>
> // Example: <a href="?switchval=val_casestudies">
> // When this link is executed then the case studies page would be
> included and loaded.
> // You would want to add code for each page you want to switch to
>
> @ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
>
> %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_casestudies") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
>
> <%
> }
> %>
>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
>
> <%
> }
> %>
---------------------------------------------------------------------
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: master detail records displayed in a portlet
Posted by Ron Wheeler <rw...@artifact-software.com>.
Thanks
Was speed the main reason that you went Struts? We use Struts in our current
portal technology but I like the looks of Jetspeed.
Ron
-----Original Message-----
From: news [mailto:news@main.gmane.org]On Behalf Of Vic Cekvenich
Sent: Thursday, August 07, 2003 9:29 AM
To: jetspeed-user@jakarta.apache.org
Subject: Re: master detail records displayed in a portlet
I tried to do a few things with JetSlow, and then I went Struts. This is
using JSTL, not Velocity, but same concept, Struts supports Velocity.
Master detail processing is done all the time, and several working samples
are in there:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/portlets/newsBlg/NewsBlgCmntsLst.jsp
Note that it using the core master tag and then iterating a list. This is
usnig nested beans. I think that is the key conecpt I recommend, nest beans
and then use dot notation to get to each of the 3 iterating
collections/beans.
So you can have one bean, that nests your 3 beans.
You can download and look at sample (or CVS source).
Here is an example of how to click in, and get detail:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/portlets/cms/ContentAdminLst.jsp
KISS,
.V
ps:
And here is a navigation, but I do not think you asked for that:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF
/config/navigation.xml
"D.S. Johnson" <ds...@insightbb.com> wrote in message
news:3F32424E.5060701@insightbb.com...
> Ron Wheeler wrote:
>
> >We are fairly new to Jetspeed and have made pretty good progress dispite
the
> >documentation.
> >
> >We are wondering how to create the following fairly common web page
> >structure.
> >We have three identical problems. List of case studies, list of white
> >papers, list of training courses.
> >In each case, we want to present the user with the list and when they
click
> >on one of them, show them the details of that item.
> >
> >The information is in one or more XML files. (list of items in one XML
that
> >links to the many individual XML files containing the details of te
item.)
> >
> >The first problem is that we do not see how we can use separate portlets
> >since we only want either the list or one of the items on the screen at
once
> >and we do not the menu to change while the user navigates within the
topic.
> >
> >If we use a single portlet, then we need to be able to respond to
selection
> >of one item (a Case Study for example) by clearing the list and
displaying
> >the selected document (the Case Study).
> >We have the xsl stylesheets to display the initial list and the details
of
> >the idividual item.
> >
> >1) Are we on the right track and understanding the problem in a
reasonable
> >way?
> >2) Which portlet type would be the best way to handle this?
> >3) Does anyone have a model that we could see/use for this type of
> >application?
> >4) Should we be looking at Velocity/DVSL rather than XSLT if we are going
to
> >work with Jetspeed?
> >
> >Thanks for the help.
> >
> >Ron
> >
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> >
> >
> >
> >
> I don't use Velocity very much so I don't know if this will work for
> you. But, I have used java server pages and servlets to switch between
> pages in the same portlet. Usually, I create a menu and then based on
> the users choice I switch to that page in the portlet. Using links I
> can then switch between different pages in the same portlet, I believe
> this is what you want to do.
>
> What I do is create the initial jsp page which will have the logic for
> jumping to other pages. So the switch file would look something like this;
> I don't know if this is the best way but, it is a way to solve your
> problem, it has worked me.
>
>
> ## switch.jsp##
>
> <%@page language="java" import="java.sql.*"%>
> <%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
> prefix='jetspeed' %>
>
> <%
> // Create and get the switch val, this will be a val to decide on what
> page to load.
>
> String var_switchval =request.getParameter("switchval");
>
> // If switchval is null ( on first pass ) then load the main menu page
>
> if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
> == 0 ) {
>
> %>
>
> <%
>
> // Include the file with the menu code, this file will have HTML code
> and a parameter called switchval.
> // So in this included file you will need to create a parameter
> (switchval), setting this val will cause the other pages to be included
> // into switch.jsp
>
> // Example: <a href="?switchval=val_casestudies">
> // When this link is executed then the case studies page would be
> included and loaded.
> // You would want to add code for each page you want to switch to
>
> @ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
>
> %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_casestudies") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
>
> <%
> }
> %>
>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
>
> <%
> }
> %>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: master detail records displayed in a portlet
Posted by Vic Cekvenich <ma...@baseBeans.com>.
I tried to do a few things with JetSlow, and then I went Struts. This is
using JSTL, not Velocity, but same concept, Struts supports Velocity.
Master detail processing is done all the time, and several working samples
are in there:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF/portlets/newsBlg/NewsBlgCmntsLst.jsp
Note that it using the core master tag and then iterating a list. This is
usnig nested beans. I think that is the key conecpt I recommend, nest beans
and then use dot notation to get to each of the 3 iterating
collections/beans.
So you can have one bean, that nests your 3 beans.
You can download and look at sample (or CVS source).
Here is an example of how to click in, and get detail:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF/portlets/cms/ContentAdminLst.jsp
KISS,
.V
ps:
And here is a navigation, but I do not think you asked for that:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF/config/navigation.xml
"D.S. Johnson" <ds...@insightbb.com> wrote in message
news:3F32424E.5060701@insightbb.com...
> Ron Wheeler wrote:
>
> >We are fairly new to Jetspeed and have made pretty good progress dispite
the
> >documentation.
> >
> >We are wondering how to create the following fairly common web page
> >structure.
> >We have three identical problems. List of case studies, list of white
> >papers, list of training courses.
> >In each case, we want to present the user with the list and when they
click
> >on one of them, show them the details of that item.
> >
> >The information is in one or more XML files. (list of items in one XML
that
> >links to the many individual XML files containing the details of te
item.)
> >
> >The first problem is that we do not see how we can use separate portlets
> >since we only want either the list or one of the items on the screen at
once
> >and we do not the menu to change while the user navigates within the
topic.
> >
> >If we use a single portlet, then we need to be able to respond to
selection
> >of one item (a Case Study for example) by clearing the list and
displaying
> >the selected document (the Case Study).
> >We have the xsl stylesheets to display the initial list and the details
of
> >the idividual item.
> >
> >1) Are we on the right track and understanding the problem in a
reasonable
> >way?
> >2) Which portlet type would be the best way to handle this?
> >3) Does anyone have a model that we could see/use for this type of
> >application?
> >4) Should we be looking at Velocity/DVSL rather than XSLT if we are going
to
> >work with Jetspeed?
> >
> >Thanks for the help.
> >
> >Ron
> >
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> >
> >
> >
> >
> I don't use Velocity very much so I don't know if this will work for
> you. But, I have used java server pages and servlets to switch between
> pages in the same portlet. Usually, I create a menu and then based on
> the users choice I switch to that page in the portlet. Using links I
> can then switch between different pages in the same portlet, I believe
> this is what you want to do.
>
> What I do is create the initial jsp page which will have the logic for
> jumping to other pages. So the switch file would look something like this;
> I don't know if this is the best way but, it is a way to solve your
> problem, it has worked me.
>
>
> ## switch.jsp##
>
> <%@page language="java" import="java.sql.*"%>
> <%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
> prefix='jetspeed' %>
>
> <%
> // Create and get the switch val, this will be a val to decide on what
> page to load.
>
> String var_switchval =request.getParameter("switchval");
>
> // If switchval is null ( on first pass ) then load the main menu page
>
> if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
> == 0 ) {
>
> %>
>
> <%
>
> // Include the file with the menu code, this file will have HTML code
> and a parameter called switchval.
> // So in this included file you will need to create a parameter
> (switchval), setting this val will cause the other pages to be included
> // into switch.jsp
>
> // Example: <a href="?switchval=val_casestudies">
> // When this link is executed then the case studies page would be
> included and loaded.
> // You would want to add code for each page you want to switch to
>
> @ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
>
> %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_casestudies") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
>
> <%
> }
> %>
>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
>
> <%
> }
> %>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: master detail records displayed in a portlet
Posted by Vic Cekvenich <ma...@baseBeans.com>.
I tried to do a few things with JetSlow, and then I went Struts. This is
using JSTL, not Velocity, but same concept, Struts supports Velocity.
Master detail processing is done all the time, and several working samples
are in there:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF/portlets/newsBlg/NewsBlgCmntsLst.jsp
Note that it using the core master tag and then iterating a list. This is
usnig nested beans. I think that is the key conecpt I recommend, nest beans
and then use dot notation to get to each of the 3 iterating
collections/beans.
So you can have one bean, that nests your 3 beans.
You can download and look at sample (or CVS source).
Here is an example of how to click in, and get detail:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF/portlets/cms/ContentAdminLst.jsp
KISS,
.V
ps:
And here is a navigation, but I do not think you asked for that:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/bPproj/bP/WEB-INF/config/navigation.xml
"D.S. Johnson" <ds...@insightbb.com> wrote in message
news:3F32424E.5060701@insightbb.com...
> Ron Wheeler wrote:
>
> >We are fairly new to Jetspeed and have made pretty good progress dispite
the
> >documentation.
> >
> >We are wondering how to create the following fairly common web page
> >structure.
> >We have three identical problems. List of case studies, list of white
> >papers, list of training courses.
> >In each case, we want to present the user with the list and when they
click
> >on one of them, show them the details of that item.
> >
> >The information is in one or more XML files. (list of items in one XML
that
> >links to the many individual XML files containing the details of te
item.)
> >
> >The first problem is that we do not see how we can use separate portlets
> >since we only want either the list or one of the items on the screen at
once
> >and we do not the menu to change while the user navigates within the
topic.
> >
> >If we use a single portlet, then we need to be able to respond to
selection
> >of one item (a Case Study for example) by clearing the list and
displaying
> >the selected document (the Case Study).
> >We have the xsl stylesheets to display the initial list and the details
of
> >the idividual item.
> >
> >1) Are we on the right track and understanding the problem in a
reasonable
> >way?
> >2) Which portlet type would be the best way to handle this?
> >3) Does anyone have a model that we could see/use for this type of
> >application?
> >4) Should we be looking at Velocity/DVSL rather than XSLT if we are going
to
> >work with Jetspeed?
> >
> >Thanks for the help.
> >
> >Ron
> >
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> >
> >
> >
> >
> I don't use Velocity very much so I don't know if this will work for
> you. But, I have used java server pages and servlets to switch between
> pages in the same portlet. Usually, I create a menu and then based on
> the users choice I switch to that page in the portlet. Using links I
> can then switch between different pages in the same portlet, I believe
> this is what you want to do.
>
> What I do is create the initial jsp page which will have the logic for
> jumping to other pages. So the switch file would look something like this;
> I don't know if this is the best way but, it is a way to solve your
> problem, it has worked me.
>
>
> ## switch.jsp##
>
> <%@page language="java" import="java.sql.*"%>
> <%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
> prefix='jetspeed' %>
>
> <%
> // Create and get the switch val, this will be a val to decide on what
> page to load.
>
> String var_switchval =request.getParameter("switchval");
>
> // If switchval is null ( on first pass ) then load the main menu page
>
> if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
> == 0 ) {
>
> %>
>
> <%
>
> // Include the file with the menu code, this file will have HTML code
> and a parameter called switchval.
> // So in this included file you will need to create a parameter
> (switchval), setting this val will cause the other pages to be included
> // into switch.jsp
>
> // Example: <a href="?switchval=val_casestudies">
> // When this link is executed then the case studies page would be
> included and loaded.
> // You would want to add code for each page you want to switch to
>
> @ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
>
> %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_casestudies") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
>
> <%
> }
> %>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
>
> <%
> }
> %>
>
>
> <%
> if ( var_switchval != null )
> if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
>
> %>
> <%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
>
> <%
> }
> %>
RE: width of IFramePortlet
Posted by Mark Orciuch <ma...@ngsltd.com>.
There are 'width' and 'height' parameters defined in registry. These are
exposed in the portlet customizer if you use 1.4-b5-dev (CVS head).
Best regards,
Mark Orciuch - morciuch@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
> -----Original Message-----
> From: k r i $ h n a n [mailto:anup.krishnan@arvind.com]
> Sent: Tuesday, August 26, 2003 6:23 AM
> To: Jetspeed Users List
> Subject: width of IFramePortlet
>
>
> Hello all ,
> i have customized the IFramePortlet for my existing
> application
> to be displayed in. but the thing is how to
> set the width and height of the displayed frame as it is very
> small and even
> on maximizing it shows the same size.
> thanks in advance
> anup
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
>
>
width of IFramePortlet
Posted by k r i $ h n a n <an...@arvind.com>.
Hello all ,
i have customized the IFramePortlet for my existing application
to be displayed in. but the thing is how to
set the width and height of the displayed frame as it is very small and even
on maximizing it shows the same size.
thanks in advance
anup
RE: Velocity vs JSP
Posted by Ron Wheeler <rw...@artifact-software.com>.
Thanks for the strategy and the code fragment.
Without getting into theology, what is the current thinking about JSP versus
Velocity?
As a latecomer to the server side development wars, we have done one fairly
large and complex application in JSP and XML.
The Jetspeed framework looks like it might be easier and more productive
than continuing to develop our own portal architecture.
I was not the coder on the JSP/XML portal but I am getting more technically
involved in the investigation of Jetspeed and Velocity.
Bottom Line question
If I have to prioritize my education (which -for better or worse - drives
the corporate strategy), should I focus on learning Velocity or learn how to
use JSP?
I do not care about "working on my resumé" since I am way too old to make a
living as a programmer. I am only trying to try to keep the company at the
most productive point of the technology spectrum.
I reference to a white paper would be the best anwer to this question.
Ron
-----Original Message-----
From: D.S. Johnson [mailto:dspectra@insightbb.com]
Sent: Thursday, August 07, 2003 8:13 AM
To: Jetspeed Users List
Subject: Re: master detail records displayed in a portlet
I don't use Velocity very much so I don't know if this will work for
you. But, I have used java server pages and servlets to switch between
pages in the same portlet. Usually, I create a menu and then based on
the users choice I switch to that page in the portlet. Using links I
can then switch between different pages in the same portlet, I believe
this is what you want to do.
What I do is create the initial jsp page which will have the logic for
jumping to other pages. So the switch file would look something like this;
I don't know if this is the best way but, it is a way to solve your
problem, it has worked me.
## switch.jsp##
<%@page language="java" import="java.sql.*"%>
<%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
prefix='jetspeed' %>
<%
// Create and get the switch val, this will be a val to decide on what
page to load.
String var_switchval =request.getParameter("switchval");
// If switchval is null ( on first pass ) then load the main menu page
if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
== 0 ) {
%>
<%
// Include the file with the menu code, this file will have HTML code
and a parameter called switchval.
// So in this included file you will need to create a parameter
(switchval), setting this val will cause the other pages to be included
// into switch.jsp
// Example: <a href="?switchval=val_casestudies">
// When this link is executed then the case studies page would be
included and loaded.
// You would want to add code for each page you want to switch to
@ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
%>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_casestudies") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
<%
}
%>
---------------------------------------------------------------------
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: Velocity vs JSP
Posted by Ron Wheeler <rw...@artifact-software.com>.
Thanks for the strategy and the code fragment.
Without getting into theology, what is the current thinking about JSP versus
Velocity?
As a latecomer to the server side development wars, we have done one fairly
large and complex application in JSP and XML.
The Jetspeed framework looks like it might be easier and more productive
than continuing to develop our own portal architecture.
I was not the coder on the JSP/XML portal but I am getting more technically
involved in the investigation of Jetspeed and Velocity.
Bottom Line question
If I have to prioritize my education (which -for better or worse - drives
the corporate strategy), should I focus on learning Velocity or learn how to
use JSP?
I do not care about "working on my resumé" since I am way too old to make a
living as a programmer. I am only trying to try to keep the company at the
most productive point of the technology spectrum.
I reference to a white paper would be the best anwer to this question.
Ron
-----Original Message-----
From: D.S. Johnson [mailto:dspectra@insightbb.com]
Sent: Thursday, August 07, 2003 8:13 AM
To: Jetspeed Users List
Subject: Re: master detail records displayed in a portlet
I don't use Velocity very much so I don't know if this will work for
you. But, I have used java server pages and servlets to switch between
pages in the same portlet. Usually, I create a menu and then based on
the users choice I switch to that page in the portlet. Using links I
can then switch between different pages in the same portlet, I believe
this is what you want to do.
What I do is create the initial jsp page which will have the logic for
jumping to other pages. So the switch file would look something like this;
I don't know if this is the best way but, it is a way to solve your
problem, it has worked me.
## switch.jsp##
<%@page language="java" import="java.sql.*"%>
<%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
prefix='jetspeed' %>
<%
// Create and get the switch val, this will be a val to decide on what
page to load.
String var_switchval =request.getParameter("switchval");
// If switchval is null ( on first pass ) then load the main menu page
if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
== 0 ) {
%>
<%
// Include the file with the menu code, this file will have HTML code
and a parameter called switchval.
// So in this included file you will need to create a parameter
(switchval), setting this val will cause the other pages to be included
// into switch.jsp
// Example: <a href="?switchval=val_casestudies">
// When this link is executed then the case studies page would be
included and loaded.
// You would want to add code for each page you want to switch to
@ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
%>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_casestudies") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
<%
}
%>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: master detail records displayed in a portlet
Posted by "D.S. Johnson" <ds...@insightbb.com>.
Ron Wheeler wrote:
>We are fairly new to Jetspeed and have made pretty good progress dispite the
>documentation.
>
>We are wondering how to create the following fairly common web page
>structure.
>We have three identical problems. List of case studies, list of white
>papers, list of training courses.
>In each case, we want to present the user with the list and when they click
>on one of them, show them the details of that item.
>
>The information is in one or more XML files. (list of items in one XML that
>links to the many individual XML files containing the details of te item.)
>
>The first problem is that we do not see how we can use separate portlets
>since we only want either the list or one of the items on the screen at once
>and we do not the menu to change while the user navigates within the topic.
>
>If we use a single portlet, then we need to be able to respond to selection
>of one item (a Case Study for example) by clearing the list and displaying
>the selected document (the Case Study).
>We have the xsl stylesheets to display the initial list and the details of
>the idividual item.
>
>1) Are we on the right track and understanding the problem in a reasonable
>way?
>2) Which portlet type would be the best way to handle this?
>3) Does anyone have a model that we could see/use for this type of
>application?
>4) Should we be looking at Velocity/DVSL rather than XSLT if we are going to
>work with Jetspeed?
>
>Thanks for the help.
>
>Ron
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
>
>
I don't use Velocity very much so I don't know if this will work for
you. But, I have used java server pages and servlets to switch between
pages in the same portlet. Usually, I create a menu and then based on
the users choice I switch to that page in the portlet. Using links I
can then switch between different pages in the same portlet, I believe
this is what you want to do.
What I do is create the initial jsp page which will have the logic for
jumping to other pages. So the switch file would look something like this;
I don't know if this is the best way but, it is a way to solve your
problem, it has worked me.
## switch.jsp##
<%@page language="java" import="java.sql.*"%>
<%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
prefix='jetspeed' %>
<%
// Create and get the switch val, this will be a val to decide on what
page to load.
String var_switchval =request.getParameter("switchval");
// If switchval is null ( on first pass ) then load the main menu page
if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
== 0 ) {
%>
<%
// Include the file with the menu code, this file will have HTML code
and a parameter called switchval.
// So in this included file you will need to create a parameter
(switchval), setting this val will cause the other pages to be included
// into switch.jsp
// Example: <a href="?switchval=val_casestudies">
// When this link is executed then the case studies page would be
included and loaded.
// You would want to add code for each page you want to switch to
@ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
%>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_casestudies") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
<%
}
%>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: master detail records displayed in a portlet
Posted by "D.S. Johnson" <ds...@insightbb.com>.
Ron Wheeler wrote:
>We are fairly new to Jetspeed and have made pretty good progress dispite the
>documentation.
>
>We are wondering how to create the following fairly common web page
>structure.
>We have three identical problems. List of case studies, list of white
>papers, list of training courses.
>In each case, we want to present the user with the list and when they click
>on one of them, show them the details of that item.
>
>The information is in one or more XML files. (list of items in one XML that
>links to the many individual XML files containing the details of te item.)
>
>The first problem is that we do not see how we can use separate portlets
>since we only want either the list or one of the items on the screen at once
>and we do not the menu to change while the user navigates within the topic.
>
>If we use a single portlet, then we need to be able to respond to selection
>of one item (a Case Study for example) by clearing the list and displaying
>the selected document (the Case Study).
>We have the xsl stylesheets to display the initial list and the details of
>the idividual item.
>
>1) Are we on the right track and understanding the problem in a reasonable
>way?
>2) Which portlet type would be the best way to handle this?
>3) Does anyone have a model that we could see/use for this type of
>application?
>4) Should we be looking at Velocity/DVSL rather than XSLT if we are going to
>work with Jetspeed?
>
>Thanks for the help.
>
>Ron
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
>
>
I don't use Velocity very much so I don't know if this will work for
you. But, I have used java server pages and servlets to switch between
pages in the same portlet. Usually, I create a menu and then based on
the users choice I switch to that page in the portlet. Using links I
can then switch between different pages in the same portlet, I believe
this is what you want to do.
What I do is create the initial jsp page which will have the logic for
jumping to other pages. So the switch file would look something like this;
I don't know if this is the best way but, it is a way to solve your
problem, it has worked me.
## switch.jsp##
<%@page language="java" import="java.sql.*"%>
<%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
prefix='jetspeed' %>
<%
// Create and get the switch val, this will be a val to decide on what
page to load.
String var_switchval =request.getParameter("switchval");
// If switchval is null ( on first pass ) then load the main menu page
if ( var_switchval == null || var_switchval.compareTo("val_main_menu")
== 0 ) {
%>
<%
// Include the file with the menu code, this file will have HTML code
and a parameter called switchval.
// So in this included file you will need to create a parameter
(switchval), setting this val will cause the other pages to be included
// into switch.jsp
// Example: <a href="?switchval=val_casestudies">
// When this link is executed then the case studies page would be
included and loaded.
// You would want to add code for each page you want to switch to
@ include file="/WEB-INF/templates/jsp/portlets/html/artifact_menu.jsp"
%>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_casestudies") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/casestudies.jsp" %>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_whitepapers") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/whitepapers.jsp" %>
<%
}
%>
<%
if ( var_switchval != null )
if ( var_switchval.compareTo("val_trainingcourses") == 0 ) {
%>
<%@ include file="/WEB-INF/templates/jsp/portlets/html/training.jsp" %>
<%
}
%>
Re: master detail records displayed in a portlet
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Monday, August 11, 2003, at 02:36 PM, Ron Wheeler wrote:
> I got some very good ideas from this original question before it
> wandered
> off into a discussion of tuning.
> I would really like to hear from someone who has an example of a
> master/detail processing in Velocity before I strike off into the
> unknown
> based on JSP examples that I received. They where very helpful in
> understanding the principle.
>
Take a look at the jetspeed tutorial example, chapter 9,
DatabaseBrowser portlet
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646
+01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: master detail records displayed in a portlet
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Monday, August 11, 2003, at 02:36 PM, Ron Wheeler wrote:
> I got some very good ideas from this original question before it
> wandered
> off into a discussion of tuning.
> I would really like to hear from someone who has an example of a
> master/detail processing in Velocity before I strike off into the
> unknown
> based on JSP examples that I received. They where very helpful in
> understanding the principle.
>
Take a look at the jetspeed tutorial example, chapter 9,
DatabaseBrowser portlet
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646
+01 707 529 9194
RE: master detail records displayed in a portlet
Posted by Ron Wheeler <rw...@artifact-software.com>.
I got some very good ideas from this original question before it wandered
off into a discussion of tuning.
I would really like to hear from someone who has an example of a
master/detail processing in Velocity before I strike off into the unknown
based on JSP examples that I received. They where very helpful in
understanding the principle.
Thanks
Ron
-----Original Message-----
From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
Sent: Thursday, August 07, 2003 12:23 AM
To: jetspeed-user@jakarta.apache.org
Cc: David Dyer
Subject: master detail records displayed in a portlet
We are fairly new to Jetspeed and have made pretty good progress dispite the
documentation.
We are wondering how to create the following fairly common web page
structure.
We have three identical problems. List of case studies, list of white
papers, list of training courses.
In each case, we want to present the user with the list and when they click
on one of them, show them the details of that item.
The information is in one or more XML files. (list of items in one XML that
links to the many individual XML files containing the details of te item.)
The first problem is that we do not see how we can use separate portlets
since we only want either the list or one of the items on the screen at once
and we do not the menu to change while the user navigates within the topic.
If we use a single portlet, then we need to be able to respond to selection
of one item (a Case Study for example) by clearing the list and displaying
the selected document (the Case Study).
We have the xsl stylesheets to display the initial list and the details of
the idividual item.
1) Are we on the right track and understanding the problem in a reasonable
way?
2) Which portlet type would be the best way to handle this?
3) Does anyone have a model that we could see/use for this type of
application?
4) Should we be looking at Velocity/DVSL rather than XSLT if we are going to
work with Jetspeed?
Thanks for the help.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
RE: master detail records displayed in a portlet
Posted by Ron Wheeler <rw...@artifact-software.com>.
I got some very good ideas from this original question before it wandered
off into a discussion of tuning.
I would really like to hear from someone who has an example of a
master/detail processing in Velocity before I strike off into the unknown
based on JSP examples that I received. They where very helpful in
understanding the principle.
Thanks
Ron
-----Original Message-----
From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
Sent: Thursday, August 07, 2003 12:23 AM
To: jetspeed-user@jakarta.apache.org
Cc: David Dyer
Subject: master detail records displayed in a portlet
We are fairly new to Jetspeed and have made pretty good progress dispite the
documentation.
We are wondering how to create the following fairly common web page
structure.
We have three identical problems. List of case studies, list of white
papers, list of training courses.
In each case, we want to present the user with the list and when they click
on one of them, show them the details of that item.
The information is in one or more XML files. (list of items in one XML that
links to the many individual XML files containing the details of te item.)
The first problem is that we do not see how we can use separate portlets
since we only want either the list or one of the items on the screen at once
and we do not the menu to change while the user navigates within the topic.
If we use a single portlet, then we need to be able to respond to selection
of one item (a Case Study for example) by clearing the list and displaying
the selected document (the Case Study).
We have the xsl stylesheets to display the initial list and the details of
the idividual item.
1) Are we on the right track and understanding the problem in a reasonable
way?
2) Which portlet type would be the best way to handle this?
3) Does anyone have a model that we could see/use for this type of
application?
4) Should we be looking at Velocity/DVSL rather than XSLT if we are going to
work with Jetspeed?
Thanks for the help.
Ron
---------------------------------------------------------------------
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