Mike, Dependancies? You are mounting your own classloaders inside your phoenix app? That is quite normal. EOB & Jesktop do it. JAMES (I guess) does it. FtpServer will for Ftplets another day. If yes, I think your issues is cause by the constructor for JdbcConnectionFactory not having classloader as a parameter. Is that right?
- Paul >We are having a problem with including the jdbc driver in with our sars. >Basically the classloader avaliable to JdbcConnectionFactory cannot read >the jdbc drivers' Driver class because it is in our application's lib >directory. If we put the jdbc driver's jar in the phoenix/lib dir it >will be available to all packages and the factory will be able to >Class.forName the jdbc driver. Is there a better way to get around >this? How do you make a resource included with one application >avaliable to it's dependancies? > >Thanks, >----------- >Mike Miller >Programmer >General American Corporation >[EMAIL PROTECTED] > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
