I hope that I am not contributing to an existing background problem. I am interested in the reasons why someone makes an architectural choice. Although speed is not my top concern, I would still like to hear what the experienced people have to say on the matter as long as it is accurate and not said just to put someone down. I would not be surprised if there is a speed penalty but then again my first programming language was assembler and I have no doubt that writting software in assembler will result in fast execution. I am not about to go back to that. You almost always pay for productivity with speed but that trade-off has been going on for the last 35 years of my life and one has to make choices when setting architectural directions. I am pretty numb to speed issues since hardware is the cheapest solution and often the top level design of algorithm has more impact than the lower level processes. (I lived through the opening days of RDBMS and can see the same potential for bad strategies in XSL. They both offer many ways to get the same result and some of them will be more efficient than others.)
I certainly agree that a flame war will not be much help but since this is a Jetspeed User forum, I expect that everyone here has an interest in the success of this venture. I appreciate the time that people are taking to deal with my questions. I am excited about the possibilities for our company of this architecture and have lots of questions. Many of them will be a bit basic but I will try to do my research. I have read all of the text on the Jetspeed site, tutorial and have read most of the Velocity stuff but until we get the first portal done, I am afraid that many of my questions will be pretty unsophisticated compared to the other discussions here. Thanks for everyone's patience and great advice. Ron -----Original Message----- From: Weaver, Scott [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 11:01 AM To: 'Jetspeed Users List' Subject: RE: master detail records displayed in a portlet > I tried to do a few things with JetSlow, and then I went Struts. Okay, that comment was uncalled for. Please try and refrain from mud slinging as it does no one any good and is fodder for a flame war, which is not conducive to the goals of this list. Regards, *===================================* * Scott T Weaver������������������� * * Jakarta Jetspeed Portal Project�� * * [EMAIL PROTECTED] * *===================================* � > -----Original Message----- > From: Vic Cekvenich [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 07, 2003 9:29 AM > To: [EMAIL PROTECTED] > 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" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > 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: [EMAIL PROTECTED] > > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > 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## > > > > <[EMAIL PROTECTED] 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
