This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hello All, I want to write a web start application that presents a view into a database I've already built a similar app as an applet to access the database from the applet I had to send messages from the applet back to scripts on the web server, which did the database access and forwarded the data to the applet. this is because the applets sandbox won't let it talk directly to the database. this was really a cludge and I'm hoping that by moving to a web start application I can connect directly to the database with jdbc. Is this going to work or will I have the same problems?? this brings me to second question I'm building little test app to test this myself I built the test app with Netbeans, it has a couple of classes each of which generate a class file. I go to command line and zip it all up into a jar file, my question is what do I do with the jdbc drivers, they are in hteir own jar file. can I just include them in my application jar file? I tried that and it didn't seem to work. I also tried just setting the classpath to the jdbc driver when I ran my app but failed there too any advice?? Thanx Dave oh, BTW, am I correct in thinking that trying to get around this problem by signing the applet/application would require every client machine to have a properties file loaded on it??
Hi Dave Look at the JavaWebStart developer's guide and in the JNLP file syntax you can find "jar" element that can solve the CLASSPATH issue for us here for JDBC driver. And I don't think you need to sign the jar files if there is no local system access violating the security sandbox for JavaWebStart. Thanks! Maulin
Joined: Sep 16, 2003
Maulin, I've got a little test ap up and running now and I did have to sign the app to get it to work. I think the deal with applets is that they can only do network IO with the web server they came from. In the past when I was using an applet I had to make scripts on the web server that the applet called to do database stuff for it because the database was on a different machine. It was a real pain. The web start application seems to have the same rules, but I broke down and figured out how to make a test certificate and sign it and now it can talk directly to the database which makes like MUCH easier Thanx for the reply Dave