XSP.partialRefreshPost is not working on IBM Bluemix Xpages runtime - xpages

I am trying to refresh a control (by id 'previewPane') in 'onComplete' event of an action button using:
XSP.partialRefreshPost('#{id:previewPane}').
It works fine on my test server Domino 9.0.1(not on bluemix).
On Bluemix it is throwing the error:
"CLFAD0380E: No component found with ID
$$xspsubmitid=view:_id1:previewPane to handle the submit event".
Is there a way to fix this.
Thanks

This is due to feature enhancement work in this area and associated function. It is specific to the current XPages Buildpack release on Bluemix, hence the reason that it is not effecting your test Domino 9.0.1 server.
You can suppress the validation error message handling by including the following XSP property in your application's xsp.properties file and redeploying to Bluemix:
xsp.error.disable.0380=true
An upcoming release of the XPages Buildpack will include the full enhancement and attempt to resolve the current regression you are experiencing.

Related

Referencing UI5 controls from Unix based systems fails

I'm creating a NodeJS based application with sapui5 framework but I'm facing a problem.
My app and view work well in my Windows 10 environment. Now I'm trying to continue developing it in Ubuntu but I'm facing this problem in Checkbox.js:
The resource from http://localhost:8000/resources/sap/m/Checkbox.js was blocked due to MIME type ("type/html") mismatch (X-Content-Type-Options: nosniff).
Uncaught (in promise) Error: failed to load 'sap/m/Checkbox.js' from resources/sap/m/Checkbox.js: script load error
As you can see, the control does exist:
All other controls work normally. So when I remove the checkbox, my view works without problems.
See the section Console shows Uncaught Error: failed to load 'sap/m/xxxxx.js' from the doc.
And the reply by Tobias (tobiasso85) on the same issue:
Serving the resources depends on the server and its underlying filesystem used.
While Unix based systems are case-sensitive,
Windows is not case-sensitive by default.
I.e. in your view, you must have somewhere <Checkbox> which works on Windows but not on Ubuntu.
→ Change it to <CheckBox>.
Same applies to <ComboBox>, <LightBox>, <FlexBox>, ... etc.
Bonus: there are Breadcrumbs from the sap.m lib and BreadCrumbs from the sap.uxap lib. 👍
PS: when working in an IDE or editor that supports VSCode extensions, consider installing the official UI5 Language Assistant. That extension would've notified you that something is wrong:
The "Combobox" name is neither a class name in the "sap.m" namespace nor an aggregation of the <parentControl> class.

XPage-Page Cant be displayed error after upgrading to Domino 9.0.1 from 8.5.3

I have recently started working with Xpages. The sample Xpage which i created in version 8.5.3 is not working after I upgraded the domino to 9.0.1. After the upgrade even a local test page is giving a 404 error. On the server its giving a Page not found error. I have done the below,
Checked the ACL for default
Checked and changed the http port number
Enabled the auto build
marked the Xpage as available to public access
The trace log does not display anything.
seems like I am missing something very obvious. Please enlighten me. Thank you.

I'm a little confused about install OpenNTF Domino API

I need to use FileSilo Project that require OpenNTF Domino API.
But I have some problem to install this fantastic tool.
I have follow the suggest of this blogger
So I have follow this step:
Download the last version of OpenNTF Domino API
Unzip the file
Import Database updateserver.nsf from the zip, into my UpdateSite (se the image)
Install in my Designer from my updatesite.nsf
restart HTTP task
Now I have this problems:
In my Domino Console after I restart the HTTP I see some error
In my Domino Designer I see many error
When I open FileSilo on the web I see another error
Soo am I doing wrong ?
UPDATED
After the #Paul Stephen Withers comment.. I've installed the correct library (updatedesigner.nsf) into my Domino Designer...now FileSilo app show only this two error:
The message on the Domino console about not finding a logging configuration file is fine. It's not an error, just information being logged out to the default log location. That just allows you to use a separate logging config file, outside of the API itself.
It looks like the key issue is the Designer install. Looking at the version number, I think you've installed the plugin from the server Update Site database into Designer.
The separate update site for Designer - updateDesigner.nsf - was needed in order to get typeahead but ensure the plugin for the server was as small as possible.
Because of the different packaging methods, you will need to uninstall from Application management before installing the newer version from updateDesigner.nsf. Note that a problem with DateTime class was identified which is fixed in "OpenNTF Domino API RC2.1.zip".
It looks like the errors on the web may be because it's been built in Designer.
I recently did a video on installing various plugins for your server and designer. Near the end I showed the install of the OpenNTF Domino API. That might be helpful to you.
http://www.notesin9.com/2014/10/21/notesin9-161-designer-plugins/

XPages - Can't instantiate class: 'Cannot find class <<classname>> in NSF'

I have an XPages application that has been running quite happily for the last couple of years.
The application uses some Java classes as converters that are used to convert data entry on certain fields to upper case, proper case, etc. This functionality has been present and working since the app was first deployed.
Today I was asked to make a change to one of the pages, adding a new field. The change was made in a test copy of the database, the app rebuilt and tested and all was fine.
The same change was then promoted into the live database, but after being rebuilt the error
Can't instantiate class: 'Cannot find class uk.co.xxx.beans.UpperCase in NSF'.
is being returned.
I have tried rebuilding the app and cleaning the project numerous times without success. I have also tried amending the code in the Java class and rebuilding.
If I remove all references to the UpperCase class it then complains about the ProperCase class. It appears as if the app has lost its reference to the Java classes and rebuilding isn't fixing the problem.
As an interim solution I have removed all uses of these classes so that users can at least display the page - but this is obviously not a long term solution. As soon as I reinstate one instance and rebuild, the error returns.
The only change in the app has been the addition of the new field. Removing it makes no difference.
Can you suggest anything else I can try and what may be causing the problem?
Open production db in designer and using Navigator view open WebContent/WEB-INF and delete classes folder. Then rebuild the app or refresh it from template again.
Sometimes classes are not updated correctly. I've seen it few times.
I have seen this too (domino 8.5.3). I recompile until it eventually works. With a restart of the http task thrown in for good measure. How are you deploying the classes within the db or as jar files in lib/ext?
I ran into similar issues with 8.53 FP2 with the same "can't instantiate errors" if accessed by a designer client. I even put a PRD in at IBM for it.
In order to fix this problem we had to update to the server and clients to FP5. We had a work around before we could update the FP5. We had to modify how the application was rolled out. Once the database was updated from a template we had to do a clean then a build while use our Application ID used for signing applications.
http://www-01.ibm.com/support/docview.wss?uid=swg21639571
JDAE8ZV2CX
XPage With Java Design Element Breaks When Domino Designer opens after applying 8.5.3 Fix Pack 2 interim fix of any 853 Fix Pack 2/Fix Pack 3 hotfix

Runtime error: "Cannot find the library com.ibm.xsp.extlib.library" (browser)

I just created my first Xpage application, and I now wanted to port it to a simple mobile application, using the mobile controls in the Xpages Extension Library. Notes/Domino 8.5.3 Upgrade Pack 1 are installed on both client/Designer and server.
The Xpage application works fine in both client and browser.
I created a new Xpage, called "mobileMainPage", and simply add a Single Page Application control to it, save the file and attempt to open it through a browser (Safari first, then IE 9 just to test). In both cases I get the following error message:
Unexpected runtime error
The runtime has encountered an unexpected error.
Exception
Cannot find the library com.ibm.xsp.extlib.library, required by the application /Contacts.nsf.
I am opening the database on the server (entering the URL of the .xsp file in the browser). I am not using the preview browser feature of Domino Designer, but is calling the page like a user would.
How do I fix this? I even tried to install Upgrade Pack 1 once more. Still getting the same error message.
It really sounds like the library is not installed on the server.
type tell http osgi ss com.ibm.xsp.extlib on the server console and verify that the plugin is installed, that command should return a list of the extlib plugins and fragments and if they have been correctly resolved or not.
in your Domino console type:
tell http xsp diag com.ibm.xsp.extlib
also try:
tell http xsp diag com.ibm.xsp.extlib.mobile
This will tell you whether or not the plugin is resolved. If the plugin is not found it means the plugin is not installed the to correct location (domino/data/domino/workspace/applications/eclipse/plugins).. If a plugin that extlib depends on is not resolved it will show in the console.
Chapter 3 of the XPages Portable Command Guide goes into this in great detail :-)
Let me know the results of the above command
Make sure to tell your app that it should use the extension library. Open the Application Properties and go to the Advanced tab. Here, verify that the 'com.ibm.xsp.extlib.library' is checked.
I just encountered a similar issue when firing up a new server in a virtual machine (was testing out an issue with different server version). I included notes.ini setting OSGI_HTTP_DYNAMIC_BUNDLES and pointed it to a updatesite database I hastily replicated over from another server.
I am not certain for sure, but once I added my new server to the updatesite and restarted http, it took.

Resources