|
Thanks Vadim, I will look at that as a solution as well. -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Vadim Berestetsky Sent: Tuesday, November 16, 2004 11:11 AM To: Websphere Development Studio Client for iSeries Subject: RE: [WDSCI-L] FW: JSF parm passing to another JSP In the J2EE world there also exists URL encode function, and JSF applications can certainly take advantage of it. However, JSF framework tries to enforce View/Model separation. From that standpoint it maybe best to follow Mike's suggestion below. It is typical to have your JSF UI components being backed up by a property in a backing bean. Something like <h:inputText id="myText" value="myBackingBean.myTextProperty" /> You can have JSP1 and JSP2 reference the same backing bean. That would be another way to pass the data between the two. Note: it is JSF framwork's responsibility to manage those backing beans as long as they are declared in the appropriate scope (request, session, application) in your faces-config.xml. Hope this helps, Vadim. "Fasnacht, Mike J" <MJFasnacht@carls To oncraft.com> "'Websphere Development Studio Sent by: Client for iSeries'" wdsci-l-bounces@m <wdsci-l@xxxxxxxxxxxx> idrange.com cc Subject 11/16/2004 11:48 RE: [WDSCI-L] FW: JSF parm passing AM to another JSP Please respond to Websphere Development Studio Client for iSeries Mike, Your suggestion to use a record number may solve my issue. I am new to JSF as well and I'm not sure how to get or use a record number using a relational record list. To answer your question regarding parameters. Using JSF, you can drag a link component on to the page you are designing (JSP1) and name the page to go to (JSP2) as well as the parameters to be passed. The URL below is an example of what is generated when the link is clicked from JSP 1 http://localhost:9080/ProgramDocumentationWAR/faces/jsp2.jsp?pdlib=TTTOOLS%2 0%20%20&pdunique=1&pdname=PGM2 As for the browser doing the conversion, I have tried Mozilla FireFox, I.E. 6.0, and the WDSc web browser. In each case, the transformation of special characters failed. I talked with a .NET person and in their world they have a URL encode function. I am researching that as well. -----Original Message----- From: wdsci-l-bounces+mjfasnacht=carlsoncraft.com@xxxxxxxxxxxx [mailto:wdsci-l-bounces+mjfasnacht=carlsoncraft.com@xxxxxxxxxxxx] On Behalf Of Mike Hockings Sent: Monday, November 15, 2004 4:12 PM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] FW: JSF parm passing to another JSP In reading the following keep in mind that I really don't know much, and even less about JSF... What exactly do you mean that JSP2 recives parms from JSP1 ? Do you mean that in JSP1 you do a submit with JSP 2 as the target? If so, then I would imagine that it is the browser doing the conversion. Would it not be better to just submit the record number from JSP1 and have JSP2 work with the true record data directly? Mike "Fasnacht, Mike J" <MJFasnacht@xxxxxxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 2004-11-15 13:51 Please respond to Websphere Development Studio Client for iSeries To "'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx> cc Subject [WDSCI-L] FW: JSF parm passing to another JSP > Hello all, > I am using Java Server Faces in WDSc 5.1.2. > > I have JSP 2 which receives parms from JSP 1. One of the parms passed to > JSP 2 usually has trailing blanks when included on the URL. Each trailing > blank in this parm is automatically converted to %20 when passed to > JSP 2. > This parm coming from JSP 1 is taken from a database field displayed > in a > relational record list. Sometimes the contents of this field in JSP 1 has > other special characters. Why aren't other special characters > (specifically #) converted just like the space (%20) is converted? > > Is there a setting to get these other special characters converted as > well? > > Michael J. Fasnacht > Wedding and Greeting Entrepreneurial Business > mjfasnacht@xxxxxxxxxxxxxxxx <mailto:mjfasnacht@xxxxxxxxxxxxxxxx> > Ph. (507) 625-0893 > Fax (507) 386-2307 > _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
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.
midrange.com
