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]

Reply via email to