|
First let me say, I'm not much of a web guy/java guy, so I'm not sure I understand exactly what your saying, but I will take a look at the podcast. That said, let me try to explain what I am shooting for. (btw, I'm just playing with this, so a lot of the details haven't been fully worked out yet) Ultimately, what I'm trying to accomplish, is a way for a user to display a list of html reports and open them up by clicking on a link. In more detail. We have a situation where our customer reps, need to pull up a copy of a bill. They want to see the actual image of the bill. So the idea is create folders somewhere(for now on my C driver(proof of concept)). When the bill is created, the spool file is converted to an html document and stored in these folders by date. Now ideally, I want the customer service rep to enter in Date/Account, and then I want to display any records for the entered date/account. The record has just 1 field. It contains the path to this html report. After the records are displayed, the user selects one(usually would only be one) and it opens up the html document. I hope that makes sense. Michael Smith iSeries.mySeries. -----Original Message----- From: albartell [mailto:albartell@xxxxxxxxx] Sent: Thursday, March 16, 2006 9:35 AM To: 'Websphere Development Studio Client for iSeries' Subject: Re: [WDSCI-L] JSF and URL's I am not completely following what you are trying to do, but note that JSF is not "restful" compliant. Basically what that means is JSF operates off of POST's instead of GET's, and without GET's you don't have URL variables, and without URL variables you don't have the parameter passing deep linking you are looking for. Check out this podcast for more info: http://timshadel.com/podcasts/Zdot-20060119-JsfPart1.mp3 Of course this is fairly easily remedied by just doing a straight up servlet or JSP, but that is obviously taking you out of the JSF framework. That's one of the reasons I am dropping JSF for Tapestry :-) HTH, Aaron Bartell -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike Sent: Thursday, March 16, 2006 7:14 AM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] JSF and URL's Thanks Pete. I actually have it like this, I just didn't grab it when I copied it to the message. I originally started this in Green Screen but for our purposes, its not practical in Green screen(using hotspots). This works currently with my sample green screen program, but when I bring it in to my JSF its treated as text not a link. Michael Smith iSeries.mySeries. -----Original Message----- From: Pete Helgren [mailto:Pete@xxxxxxxxxx] Sent: Wednesday, March 15, 2006 7:07 PM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] JSF and URL's Mike, I don't know how you are displaying the field contents but if it is in an HTML form but located on the local hard drive then your HTML would have an href tag followed by file:///and then the path. Such as <a href="file:///C:\BILLS\F111504\A0015209.HTML">File description or name here</a> I can't tell from your post just how you want to reference the file but in HTML this should work. Pete Helgren Smith, Mike wrote: >I'm trying to access a database on the Iseries that is a 1 field >record. Basically this file is made up of a URL(ie. >C:\BILLS\F111504\A0015209.HTML) >However, when I run this, it doesn't display as a URL. Its just an >output field. Is it possible to read these records and have them >display as a URL. >I'm using a 'Relational Record List' currently. > >The idea is that these are locations of specific spool files converted >to HTML and I want to give a user the ability to open the HTML page. > >Thanks > > >Michael Smith >iSeries.mySeries. > > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.