I am having issue with value picker of extension library. When i use java file exitlib/pickers/SimplePicker.java system shows following errors.
i) SampleDataUtil cannot be resolved
ii) The import exitlib.SampleDataUtil cannot be resolved
I have gone through a thread on internet that in application properties advanced tab i have to check following 2 options
com.ibm.xsp.extlib.library
com.ibm.xsp.extlibx.library
but these options are not available to me. Can anybody guide me where I am having issue in implementing extension library.
Thanks in advance
It sounds like things are possibly not installed correctly....
Try tell http osgi ss com.ibm.xsp.extlibx on the server console to see if it is resolved.
If not, the installation hasn't worked correctly on the server.
Another option is you haven't installed in designer?
The below is a good reference for installing on both server and client
http://www.tlcc.com/admin/tlccsite.nsf/pages/extension-lib
Related
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/
I'm trying to install Nwazet Commerce with Orchard 1.7.2.
Suddenly, nothing happens. No new menus, no errors, nothing in the logs, nothing. It is just as if I hadn't installed it.
Before you ask... yes I've enabled the modules.
I can't find even a single scrap of documentation. What is supposed to happen? I would expect to see some extra menus or something on my dashboard or perhaps some extra content types, but there's nothing.
Help please :-|
You can't. The current version in the source repository is only compatible with the 1.x branch. See https://bitbucket.org/bleroy/nwazet.commerce/issue/20/update-to-17
I have a version for 1.7.2 unfortunately I don't know what fork it was from so I don't know what bugs or issues were included.
I found it in my saved orchard files and tested quickly you will get the admin options.
Download available here
For some odd reason, I can't seem to have code completion with the "express" object in my node.js project. Here is a screen of it.
My OS is Windows 8 and I am using IntelliJ Idea 12.11. Perhaps I need to do some extra setup? Please let me know.
#CrazyCoder got it right, it is indeed a intellij bug, as of now still unpatched, guess we have to wait =( The URL is http://youtrack.jetbrains.com/issue/WEB-6667. In the meantime, I guess I will have to live with it.
if you are on IDEA 13, you will still not get the Express methods until you use the express typescript stub
go to Javascript Libraries > Downloads and switch the combobox at the top to Typescript community stubs then type express
you should see the stub, it's also here:
https://github.com/borisyankov/DefinitelyTyped/blob/master/express/express.d.ts
if you are on Java 1.7 and haven't disabled the SNI Support you will get a handshake alert and the download will fail, go to the directory where your IDEA.exe is located and add the following line to the idea.exe.vmoptions:
-Djsse.enableSNIExtension=false
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.
I'm trying to export a profile from WAS 6.1 so that I can give it to other members of my team with all of the JNDI and Shared Library configurations in place. I've flowed a few IBM tutorials on this like http://www-01.ibm.com/support/docview.wss?uid=swg21322309 (technically that is more a bug fix, but there is a similar page). I've tried to export the server using the "import" feature of the server in RAD 7. None of these options create a .car file with the resources sticking around.
Does anyone know how to do this?
Thanks,
JPD
Have you tried exporting/importing the WAS configuration using the wsadmin console as described in the following IBM TechNote?
https://www-304.ibm.com/support/docview.wss?uid=swg21207526
Unfortunately, the SIB configuration will be missing from the export -- I'm not sure if it's a bug or a feature, but it's at least mentioned by IBM in their TechNote so you don't have to pull out your hair searching for the problem.