David,

 

In the designer client, open up the package explorer by navigating to  Window\Show Eclipse Views and in the resulting dialog pick Package Explorer in the Java section. Once Package Explorer is open, navigate to your nsf and open that up and navigate to the WebContent\WEB-INF folder. Create a new folder here called lib, then place your jar file here. This will make it available to the server and your application. I don't remember off the top of my head if I had to include that in the build path, so if it's still not available to your application you may want to look there.

 

You can also check out the article I did on connecting to MySQL with an XPage application here Sharing Data between MySQL and Lotus Domino

 

HTH 

Keith 

 Ah, I see. OK, I would attempt to set this up in a sessionScope bean and then it should be available everywhere for that particular user. However, I'm not sure how you would ensure the connection got closed when the session had expired. Or even better would be a viewScope bean and then close the connection via an RPC call in the onWindowUnload event or something to that effect as long as the viewScope was still available at that time.  

 

Of course I haven't tested either one of those scenarios so I'm not sure of their feasibility. Personally, I've just always started a new connection for each request. I'm sure in a heavily used application that probably isn't the best way to do things, but it does work pretty reliably. 

 

HTH 

Keith 

Domino 8.5.3 will (as far as I know) support connection pooling out of the box (incl. JNDI support). I know this is in 8.5.3 and you don't have that one yet, but it is good to know.

 

I'm afraid that there's no way you can share the connection. The scope variables (applicationScope) might work, but don't know about the timesouts and closing / reopening the connection. Is it 100% safe? I think someone from IBM could know this for sure.

 

If you find out something usefull, keep the forum posted.