× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,

I work with Michiel on this problem and we found out that the cause of
the "closing browser" prompt was in the bean that was being used. It
starts to collect data from the launch screen -> logon -> application.
When you exit application it wants to go back to application -> launch
screen, but since we didn't start the session with the launch screen the
bean doesn't have all the info hence it calls a javascript to close the
browser.
As Michiel said we used an autosubmit form on the launch screen so it
automatically goes to the Logon with the correct session info.


P.S. If someone else has a better solution we'd appreciate it, because
we feel like this solution is like handling a symptom instead of really
curing the problem.
Greetings,

Chris

-----Oorspronkelijk bericht-----
Van: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
Namens Mertens, Michiel
Verzonden: donderdag 26 mei 2005 9:57
Aan: wdsci-l@xxxxxxxxxxxx
Onderwerp: [WDSCI-L] FW: Exit problem webfacing

Thanks, for your reply

I've found another solution. I used an autosubmit on the Launchscreen,
so everytime you start up the application it gets send to the
logonscreen

Michiel 

-----Oorspronkelijk bericht-----
Van: Mertens, Michiel 
Verzonden: donderdag 26 mei 2005 9:54
Aan: 'wdsci-l@xxxxxxxxxxxx'
Onderwerp: RE: Exit problem webfacing

 

The first thing I'll say is that I have not tried this so I don't know
if it will work or not...

WF will try to go back to the referrer page when the app ends, so maybe
what you want to do is set the referrer page to point to another
invocation of the app?  That is, when you launch an app and the uid/pwd
is not predefined then it will prompt for logon.  The problem that I
could imagine with pointing it back to the invocation of the app is that
it may time out (default is 30 mins I believe)  before someone goes to
actually log in again.

Mike



Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx 





"Mertens, Michiel" <mimertens@xxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
05/25/2005 05:13 AM
Please respond to
Websphere Development Studio Client for iSeries 


To
<wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] Exit problem webfacing






Hi,

When I open a Webfacing appllication using WFInvocation.do?inv=INV1, I
get the logon window. When I logon and then try to exit the application,
the application tries to close the browser and I get the following
message popup 'the Web page you are viewing is trying to close the
window. Do you want to close the window? YES NO.

When I open the same application without using WFInvocation.do?inv=INV1,
I get the Launch button and then when I exit it returns to the Launch
button.

Is it possible that the application returns to the logonscreen when I
try to exit the application, without returning to the launch button?

Thanks,
Michiel 
******************************************************************
Deze e-mail is gecontroleerd op virussen.
Aan de inhoud van dit bericht kunnen geen rechten ontleend worden.
******************************************************************
Thanks,
Michiel 
******************************************************************
Deze e-mail is gecontroleerd op virussen.
Aan de inhoud van dit bericht kunnen geen rechten ontleend worden.
******************************************************************


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.