worklight-runtime

问题 As you can see, at the bottom of my page remains a white space. Its height is the same of the old status bar that was present in ios6. Do i have to modify css? Because I never fixed an height for my app, worklight has always chosen the right size. EDIT: you have to save the image and open in a desktop with different color to see the white space at the bottom. * * Licensed Materials - Property of IBM * 5725-G92 (C) Copyright IBM Corp. 2011, 2013. All Rights Reserved. * US Government Users

问题 I have a problem when deploying my Worklight project on the server . It shows the following Error Message : FWLSE3041E: No MBean found for Worklight project 'MyProject'. Possibly the Worklight runtime web application for Worklight project 'MyProject' is not running. If it is running, use JConsole to inspect the available MBeans. and when I tried to preview my application it showed this message : SRVE0777E: Exception thrown by application class 'com.worklight.core.auth.impl

问题 I have tried using this WL.App.openURL('link','_blank') . In my app, I have some hyperlinks. Upon clicking a link, it has to load respective pages in the app itself. How do I accomplish this? 回答1: You are mis-using the API... You have 2 options: Use Cordova's InAppBrowser API This way you can display a browser window ontop of the app; when done you tap a button to close it and return to the app. This code snippet works: <a href="#" onclick="window.open('http://apache.org', '_blank', 'location

问题 In our project we are trying to figure our what the best process to connect to the server will be - especially when taking care of offline/online scenarios etc. Right now, for us, it seems that all three options to connect to the WL server are similar. Whatever option we use, we can call our Adapter Procedures perfectly and we receive Notification Messages that are set in the console. We are not sure about Direct Update - this is not working properly yet. Are there any important differences

问题 In our project we are trying to figure our what the best process to connect to the server will be - especially when taking care of offline/online scenarios etc. Right now, for us, it seems that all three options to connect to the WL server are similar. Whatever option we use, we can call our Adapter Procedures perfectly and we receive Notification Messages that are set in the console. We are not sure about Direct Update - this is not working properly yet. Are there any important differences

问题 I have done adapter based authentication and there is no problem in authentication and it works fine. I have faced some issues in getting the active users useridentity.The code may explain you a bit more adapterAuthRealmChallengeHandler.handleChallenge = function(response){ var authRequired = response.responseJSON.authRequired; if (authRequired == true){ if (response.responseJSON.errorMessage) alert(response.responseJSON.errorMessage); } else if (authRequired == false){

问题 Let's say I push new code to the Worklight server for purposes of a Direct Update. Can I allow users to still use the application for a set amount time before they actually have to accept the update or is the application essentially unavailable to them until they download the new code? 回答1: If you are developing your application using Worklight 6.2, then you as a developer can take over the entire Direct Update flow and can essentially decide how to handle a received update from the server.

问题 Using IBM Worklight version 6.1.0.02-20160314-1430 Implemented AES at adapter with reference to below link. https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/server-side-development/javascript-adapters/using-java-adapters/ Its working fine as expected in Eclipse in my local server. Generated war file and same given deployment for server. From server when I am trying to accessing getting below error response. Below things are crosschecked. Collected war file from server,

问题 I've test WL.BusyIndicator like following code: busyIndicator = new WL.BusyIndicator('content', { text : 'saving' }); busyIndicator.show(); setTimeout(function() { busyIndicator.hide(); }, 3000); The Information Center says BusyIndicator options can get 'text' in Android environment. I can see the BusyIndicator shown on my Android Emulator (v4.0.4/v4.1.2/v4.2.2) but the text is default 'Loading'... Note: the same happens in iOS as well. My Worklight Studio version is: 6.0.0.201307241843 回答1:

问题 Attached is the code for we have implemented for the busy indicator on iOS. But this does not wrap the busyText on iOS. $.r.setBusyIndicator(new WL.BusyIndicator('content', { opacity : 0.65, fullScreen : false, text : busyText })); 回答1: Wrapping is not available. You can use a different busy indicator altogether: a native busy implementation by you, or an indicator provided by a 3rd party library (jQuery Mobile, ...), etc. Otherwise, you need to use the boxLength property which controls the