Comments on: Don’t forget the drivers! http://www.acidlabs.org/2007/02/16/dont-forget-the-drivers/ Conversation. Collaboration. Community. Sat, 06 Mar 2010 02:35:30 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Matt Woodward http://www.acidlabs.org/2007/02/16/dont-forget-the-drivers/comment-page-1/#comment-1629 Matt Woodward Fri, 16 Feb 2007 13:37:28 +0000 http://dev.acidlabs.org/2007/02/16/dont-forget-the-drivers/#comment-1629 No worries--feedback is always welcome so I'll make that more clear. What I was thinking from a maintenance standpoint is if you do point DBEdit to the same place as the JRun drivers, then if you have to update the drivers you only have to do it in one place. I have the exact same problem on the Mac as you do concerning adding drivers at CF_ROOT/servers/lib. I also have to put them inside each server instance. Putting in the higher-level lib directory *does* work for me on Windows though, so I'm not sure what's up with that. I believe I had the same issue on Linux that I have on the Mac, so maybe it's a weird *nix issue. No worries–feedback is always welcome so I’ll make that more clear. What I was thinking from a maintenance standpoint is if you do point DBEdit to the same place as the JRun drivers, then if you have to update the drivers you only have to do it in one place.

I have the exact same problem on the Mac as you do concerning adding drivers at CF_ROOT/servers/lib. I also have to put them inside each server instance. Putting in the higher-level lib directory *does* work for me on Windows though, so I’m not sure what’s up with that. I believe I had the same issue on Linux that I have on the Mac, so maybe it’s a weird *nix issue.

]]> By: trib http://www.acidlabs.org/2007/02/16/dont-forget-the-drivers/comment-page-1/#comment-1631 trib Fri, 16 Feb 2007 11:37:59 +0000 http://dev.acidlabs.org/2007/02/16/dont-forget-the-drivers/#comment-1631 Hay, Matt. I wasn't having a dig at you, it's just something that I came across as I was setting this up today. It's actually a big pain. Here I am, wanting to mess with the config as little as possible and: <ul> <li>I can't point dbEdit and ColdFusion datasources at the same instance of the driver, unless I point dbEdit at the drivers inside JRun</li> <li>due to some wierdness, that may be local to me, I can't add drivers at <code>{cf_installation}/servers/lib</code> and have them recognised by all my server instances (I run a separate server instance for each client development, as I don't want mappings, custom tags, etc. all mixed in), so I have to bury them deep inside each server instance at <code>{cf_installation}/servers/{server_name}/cfusion-ear/cfusion-war/WEB-INF/lib</code>. </li></ul> So, I wasn't hassling you, but just pointing out something for the unwary, as I managed to trap myself on the same issue. Hay, Matt. I wasn’t having a dig at you, it’s just something that I came across as I was setting this up today. It’s actually a big pain. Here I am, wanting to mess with the config as little as possible and:

  • I can’t point dbEdit and ColdFusion datasources at the same instance of the driver, unless I point dbEdit at the drivers inside JRun
  • due to some wierdness, that may be local to me, I can’t add drivers at {cf_installation}/servers/lib and have them recognised by all my server instances (I run a separate server instance for each client development, as I don’t want mappings, custom tags, etc. all mixed in), so I have to bury them deep inside each server instance at {cf_installation}/servers/{server_name}/cfusion-ear/cfusion-war/WEB-INF/lib.

So, I wasn’t hassling you, but just pointing out something for the unwary, as I managed to trap myself on the same issue.

]]> By: Matt Woodward http://www.acidlabs.org/2007/02/16/dont-forget-the-drivers/comment-page-1/#comment-1630 Matt Woodward Fri, 16 Feb 2007 11:21:16 +0000 http://dev.acidlabs.org/2007/02/16/dont-forget-the-drivers/#comment-1630 Actually in the context of that guide I was describing how to set up the DBEdit plugin connections in Eclipse, not how to get CF to talk to your databases, so what I outline is correct in that limited context. That being said, it probably would be convenient to put the drivers in a place that both CF and DBEdit could use them, so I'll revise that a bit to outline that as an option. If you put the drivers somewhere other than in CF's classpath and you're on a multi-server install, you would have to log into the JRun administrator (not the CF administrator) to add the jar file to the classpath, which isn't a huge deal but isn't the most convenient thing in the world either. Thanks for the feedback--I'll get things updated and point people to this post for additional info/background. Actually in the context of that guide I was describing how to set up the DBEdit plugin connections in Eclipse, not how to get CF to talk to your databases, so what I outline is correct in that limited context. That being said, it probably would be convenient to put the drivers in a place that both CF and DBEdit could use them, so I’ll revise that a bit to outline that as an option.

If you put the drivers somewhere other than in CF’s classpath and you’re on a multi-server install, you would have to log into the JRun administrator (not the CF administrator) to add the jar file to the classpath, which isn’t a huge deal but isn’t the most convenient thing in the world either.

Thanks for the feedback–I’ll get things updated and point people to this post for additional info/background.

]]>