As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I get the above error when submitting a page. Instead of having all that horrible code which RLP produces, we've created a site-wide .css file which does all the formatting and layout. Then I've copied all the calls to the javascript files which sits before and after the form that handles a page, but I get the above error. It points to line 1241 in \ibi\webfocus52ibi_html\javaassist\ibi\html\js\ibirls.js. Has anybody else had this happen?
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004
No, but then probably no one has done what you have described.
I do not like it either, but you have to be very careful about what Resource Layout Painter code you fiddle about with.
For instance:
When you create a parameter screen for a fex, there is no action for the form. It's odd, because all parameter screens for WebFOCUS reports require a form action.
A JavaScript function SaveValues is automatically added to form onSubmit. Another JavaScript function UpdateData is automatically added to body onLoad.
The annoying thing these two functions do is to remember the selected parameters from one screen to automatically set them on another screen. I did not want this behaviour, so I removed the two functions and voila, no remembering of parameters between screens.
Except that when I submit the form, nothing happens! After spending a heck amount of time, I determined that UpdateData has another very important function - setting the form action.
I had to put the UpdateData function back into the screen - or, I could have left the function out and hard-coded the form action.
I have not seen any documentation on this behaviour.
One can only surmise that Developer Studio is NOT for programmers, it is for people that do not want or need to peek under the covers.
I believe that structure (dynamically to set ACTION of the form) is there to maintain portability -- It self-adjusts when migrated to a different server (e.g., dev to test to prod), or when wf client is reconfigured (say from CGI to Servlet).
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
thnx Pietro, you pointed me in the right direction. I changed the run button to a normal submit button and hardcoded the action for the form, and everything works like a charm.
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004
Focal Point Forums 