Re: java.library.path - DLL - Domino ..why not use CORBA?
Hi I'm wondering why you're using the Domino DLLs to access Domino? Domino has a Corba interface which enables you to access all the Domino classes (exept the Notes UI) This whould be the normal way to do it. What makes you choose the other way? regards Jesper B. Kiaer http://www.jezzper.com -Durfee, Bernard [EMAIL PROTECTED] wrote: - To: Tomcat Users List From: Durfee, Bernard Date: 04/06/2005 22:33 Subject: java.library.path - DLL - Domino I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. I got to the point where even brute force did not work... System.setProperty(java.library.path, D:\\Lotus\\Domino); m_logger.info(Using java.library.path: + System.getProperty(java.library.path)); ...from the logger... Using java.library.path: D:\Lotus\Domino ...then the line... System.loadLibrary(nlsxbe); ...fails with the following exception... java.lang.UnsatisfiedLinkError: no nlsxbe in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) ...and indeed I do have a DLL file D:\Lotus\Domino\nlsxbe.dll. This is on a Windows 2000 machine. Any ideas? Bernard Durfee - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: java.library.path - DLL - Domino ..why not use CORBA?
Jesper, I seemed to me that there would be a performance increase in using the DLL, since the servlet is running on the same machine as Domino. Using the CORBA method to connect to the same machine seemed like extra overhead. Bernard Durfee -Original Message- From: Jesper B. Kiær [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 3:03 AM To: Tomcat Users List Subject: Re: java.library.path - DLL - Domino ..why not use CORBA? Hi I'm wondering why you're using the Domino DLLs to access Domino? Domino has a Corba interface which enables you to access all the Domino classes (exept the Notes UI) This whould be the normal way to do it. What makes you choose the other way? regards Jesper B. Kiaer http://www.jezzper.com -Durfee, Bernard [EMAIL PROTECTED] wrote: - To: Tomcat Users List From: Durfee, Bernard Date: 04/06/2005 22:33 Subject: java.library.path - DLL - Domino I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. I got to the point where even brute force did not work... System.setProperty(java.library.path, D:\\Lotus\\Domino); m_logger.info(Using java.library.path: + System.getProperty(java.library.path)); ...from the logger... Using java.library.path: D:\Lotus\Domino ...then the line... System.loadLibrary(nlsxbe); ...fails with the following exception... java.lang.UnsatisfiedLinkError: no nlsxbe in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) ...and indeed I do have a DLL file D:\Lotus\Domino\nlsxbe.dll. This is on a Windows 2000 machine. Any ideas? Bernard Durfee - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: java.library.path - DLL - Domino ..why not use CORBA?
Hi Bernard If you're running on the same machine you do not need to have a Domino session but can call the Domino classes as local. Actually it may be faster to access Domino with CORBA. Take a look at http://www.advisor.com/doc/07472 I must admit i have never heard of anyone tring to access Domino the way you do. My guess is that it is not the fastest way and proberbly unstable. regards Jesper B. Kiaer http://www.jezzper.com -Durfee, Bernard [EMAIL PROTECTED] wrote: - To: Tomcat Users List From: Durfee, Bernard Date: 04/07/2005 15:18 Subject: RE: java.library.path - DLL - Domino ..why not use CORBA? Jesper, I seemed to me that there would be a performance increase in using the DLL, since the servlet is running on the same machine as Domino. Using the CORBA method to connect to the same machine seemed like extra overhead. Bernard Durfee -Original Message- From: Jesper B. Kiær [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 3:03 AM To: Tomcat Users List Subject: Re: java.library.path - DLL - Domino ..why not use CORBA? Hi I'm wondering why you're using the Domino DLLs to access Domino? Domino has a Corba interface which enables you to access all the Domino classes (exept the Notes UI) This whould be the normal way to do it. What makes you choose the other way? regards Jesper B. Kiaer http://www.jezzper.com -Durfee, Bernard wrote: - To: Tomcat Users List From: Durfee, Bernard Date: 04/06/2005 22:33 Subject: java.library.path - DLL - Domino I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. I got to the point where even brute force did not work... System.setProperty(java.library.path, D:\\Lotus\\Domino); m_logger.info(Using java.library.path: + System.getProperty(java.library.path)); ...from the logger... Using java.library.path: D:\Lotus\Domino ...then the line... System.loadLibrary(nlsxbe); ...fails with the following exception... java.lang.UnsatisfiedLinkError: no nlsxbe in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) ...and indeed I do have a DLL file D:\Lotus\Domino\nlsxbe.dll. This is on a Windows 2000 machine. Any ideas? Bernard Durfee - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
java.library.path - DLL - Domino
I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. I got to the point where even brute force did not work... System.setProperty(java.library.path, D:\\Lotus\\Domino); m_logger.info(Using java.library.path: + System.getProperty(java.library.path)); ...from the logger... Using java.library.path: D:\Lotus\Domino ...then the line... System.loadLibrary(nlsxbe); ...fails with the following exception... java.lang.UnsatisfiedLinkError: no nlsxbe in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) ...and indeed I do have a DLL file D:\Lotus\Domino\nlsxbe.dll. This is on a Windows 2000 machine. Any ideas? Bernard Durfee - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: java.library.path - DLL - Domino
On Apr 6, 2005 3:33 PM, Durfee, Bernard [EMAIL PROTECTED] wrote: I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. Try manually registering the DLL: regsvr32 D:\Lotus\Domino\nlsxbe.dll REgards, -- Jason Bainbridge http://kde.org - [EMAIL PROTECTED] Personal Site - http://jasonbainbridge.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: java.library.path - DLL - Domino
No dice. It just seems that a call to System.loadLibrary() is not using the 'java.library.path', otherwise how could it possibly not see the DLL? Bernard Durfee -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 4:43 PM To: Tomcat Users List Subject: Re: java.library.path - DLL - Domino On Apr 6, 2005 3:33 PM, Durfee, Bernard [EMAIL PROTECTED] wrote: I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. Try manually registering the DLL: regsvr32 D:\Lotus\Domino\nlsxbe.dll REgards, -- Jason Bainbridge http://kde.org - [EMAIL PROTECTED] Personal Site - http://jasonbainbridge.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: java.library.path - DLL - Domino
On Apr 6, 2005 3:53 PM, Durfee, Bernard [EMAIL PROTECTED] wrote: No dice. It just seems that a call to System.loadLibrary() is not using the 'java.library.path', otherwise how could it possibly not see the DLL? Bernard Durfee Next try adding the Domino's executable directory to the system PATH, the problem is likely down further in the stack trace and not related to the Java side of things. Regards, -- Jason Bainbridge http://kde.org - [EMAIL PROTECTED] Personal Site - http://jasonbainbridge.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: java.library.path - DLL - Domino
Have you tried putting it into your system path via the PATH environment variable? (If you're running Tomcat as a service, you'll need to reboot to have it take effect I think.) If it's there, what happens if you run rundll32 nlsxbe SomeDummyEntryPoint? it should find the DLL, but complain about the invalid entry point. Jay Vertical Technology Group http://www.vtgroup.com/ -Original Message- From: Durfee, Bernard [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 3:34 PM To: Tomcat Users List Subject: java.library.path - DLL - Domino I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. I got to the point where even brute force did not work... System.setProperty(java.library.path, D:\\Lotus\\Domino); m_logger.info(Using java.library.path: + System.getProperty(java.library.path)); ...from the logger... Using java.library.path: D:\Lotus\Domino ...then the line... System.loadLibrary(nlsxbe); ...fails with the following exception... java.lang.UnsatisfiedLinkError: no nlsxbe in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) ...and indeed I do have a DLL file D:\Lotus\Domino\nlsxbe.dll. This is on a Windows 2000 machine. Any ideas? Bernard Durfee - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: java.library.path - DLL - Domino
Yes, I started by making sure that the DLL was in the Windows system path. I also tried running the DLL as you suggested and it did indeed find the DLL and complain about the bad entry point. I believe that Tomcat supplies a special class loader to each web application. I also believe that the class loader is expected to find libraries and such. So the question is, where do I put my DLL so that the web application class loader can find it? Apparently the answer is not java.library.path, unless there is a bug in Tomcat preventing it from properly parsing the path. Bernard Durfee -Original Message- From: Jay Burgess [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 5:01 PM To: tomcat-user@jakarta.apache.org Subject: RE: java.library.path - DLL - Domino Have you tried putting it into your system path via the PATH environment variable? (If you're running Tomcat as a service, you'll need to reboot to have it take effect I think.) If it's there, what happens if you run rundll32 nlsxbe SomeDummyEntryPoint? it should find the DLL, but complain about the invalid entry point. Jay Vertical Technology Group http://www.vtgroup.com/ -Original Message- From: Durfee, Bernard [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 3:34 PM To: Tomcat Users List Subject: java.library.path - DLL - Domino I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. I got to the point where even brute force did not work... System.setProperty(java.library.path, D:\\Lotus\\Domino); m_logger.info(Using java.library.path: + System.getProperty(java.library.path)); ...from the logger... Using java.library.path: D:\Lotus\Domino ...then the line... System.loadLibrary(nlsxbe); ...fails with the following exception... java.lang.UnsatisfiedLinkError: no nlsxbe in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) ...and indeed I do have a DLL file D:\Lotus\Domino\nlsxbe.dll. This is on a Windows 2000 machine. Any ideas? Bernard Durfee - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: java.library.path - DLL - Domino
Having just done something similar with a different app's DLL and seen the same error, all I had to do was make sure the DLL was in my system PATH (and reboot as I had Tomcat running as a service). Sorry I don't have another idea. Jay Vertical Technology Group http://www.vtgroup.com/ -Original Message- From: Durfee, Bernard [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 4:18 PM To: Tomcat Users List Subject: RE: java.library.path - DLL - Domino Yes, I started by making sure that the DLL was in the Windows system path. I also tried running the DLL as you suggested and it did indeed find the DLL and complain about the bad entry point. I believe that Tomcat supplies a special class loader to each web application. I also believe that the class loader is expected to find libraries and such. So the question is, where do I put my DLL so that the web application class loader can find it? Apparently the answer is not java.library.path, unless there is a bug in Tomcat preventing it from properly parsing the path. Bernard Durfee -Original Message- From: Jay Burgess [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 5:01 PM To: tomcat-user@jakarta.apache.org Subject: RE: java.library.path - DLL - Domino Have you tried putting it into your system path via the PATH environment variable? (If you're running Tomcat as a service, you'll need to reboot to have it take effect I think.) If it's there, what happens if you run rundll32 nlsxbe SomeDummyEntryPoint? it should find the DLL, but complain about the invalid entry point. Jay Vertical Technology Group http://www.vtgroup.com/ -Original Message- From: Durfee, Bernard [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 3:34 PM To: Tomcat Users List Subject: java.library.path - DLL - Domino I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. I got to the point where even brute force did not work... System.setProperty(java.library.path, D:\\Lotus\\Domino); m_logger.info(Using java.library.path: + System.getProperty(java.library.path)); ...from the logger... Using java.library.path: D:\Lotus\Domino ...then the line... System.loadLibrary(nlsxbe); ...fails with the following exception... java.lang.UnsatisfiedLinkError: no nlsxbe in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) ...and indeed I do have a DLL file D:\Lotus\Domino\nlsxbe.dll. This is on a Windows 2000 machine. Any ideas? Bernard Durfee - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: java.library.path - DLL - Domino
The DLL was found when I put it in the C:\JavaTools\JRE1.5.0\bin which is in the sun.boot.library.path. Looking through the code in ClassLoader.java, it should search the paths in java.library.path after it searches sun.boot.library.path. ClassLoader parses java.library.path once at the first call to loadLibrary... usr_paths = initializePath(java.library.path); ...so why is it not finding the DLL on that path? The only possible reason would have something to do with Tomcat or Java security interfering, but I can find no evidence of this. Bernard Durfee -Original Message- From: Durfee, Bernard Sent: Wednesday, April 06, 2005 4:34 PM To: Tomcat Users List Subject: java.library.path - DLL - Domino I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. I got to the point where even brute force did not work... System.setProperty(java.library.path, D:\\Lotus\\Domino); m_logger.info(Using java.library.path: + System.getProperty(java.library.path)); ...from the logger... Using java.library.path: D:\Lotus\Domino ...then the line... System.loadLibrary(nlsxbe); ...fails with the following exception... java.lang.UnsatisfiedLinkError: no nlsxbe in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) ...and indeed I do have a DLL file D:\Lotus\Domino\nlsxbe.dll. This is on a Windows 2000 machine. Any ideas? Bernard Durfee - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: java.library.path - DLL - Domino
Problem solved, I restarted Eclipse, waved my hands a couple times and presto, the DLL is found no problem. The wonders of Java on Windows. Although it would be great if someone could explain how with a DLL in a path in the java.library.path could not be found. Bernard Durfee -Original Message- From: Durfee, Bernard Sent: Wednesday, April 06, 2005 4:34 PM To: Tomcat Users List Subject: java.library.path - DLL - Domino I am trying to use the native library for connecting to Domino from a servlet. I was under the impression that the DLL needed to be in the path specified by the java.library.path system property. However, this does not seem to work. I got to the point where even brute force did not work... System.setProperty(java.library.path, D:\\Lotus\\Domino); m_logger.info(Using java.library.path: + System.getProperty(java.library.path)); ...from the logger... Using java.library.path: D:\Lotus\Domino ...then the line... System.loadLibrary(nlsxbe); ...fails with the following exception... java.lang.UnsatisfiedLinkError: no nlsxbe in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) ...and indeed I do have a DLL file D:\Lotus\Domino\nlsxbe.dll. This is on a Windows 2000 machine. Any ideas? Bernard Durfee - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
