Tim Holloway wrote:You cannot execute a JAR without a Java runtime program (JVM). An "executable" JAR is one where you can say:
Terrance Samson wrote:How do I decompress/extract the files from that? Or should I do it in Windows and then just take those extracted files and put them in Java? Or can I even do it in Windows?
The name deque is short for "double ended queue" and is usually pronounced "deck".
Andrew Spiteri wrote:You say var like a pirate saying arrrrrr, and then args, like the beginning of [arg]ument, with an s sound at the end.
Dave Tolls wrote:Looks like '\' hasn't been encoded.
Mike Simmons wrote:But I don't see a new certification coming out of this release.
Tim Holloway wrote:What I would expect to see is that there should be no DLL code in the Java application at all. Because a well-designed JDBC Type 2 Driver should be managing the DLL itself. It's in a far better position to know if/when the DLL should be loaded/unloaded and by keeping the OS-dependent code within itself, helps keep the actual application code more in the ideal Java mode of "write-once/run-anywhere".
Ron McLeod wrote:For example, on my Windows workstation:
Sam Gho wrote:httpd.exe: Syntax error on line 583 of D:/Program Files (x86)/Apache Software Foundation/Apache24/conf/httpd.conf: Cannot load D:/Program Files (x86)/PHP/php5apache2_2.dll into server: %1 is not a valid Win32 application
Tim Holloway wrote:The one thing that I really wonder about is that you're using a path with forward slashes to point to your PHP module. While I definitely recommend doing that for Java apps, I'm not sure if Apache will handle that properly. Unless instructions explicitly say not to, I'd try the traditional backslash path style.
Tim Holloway wrote:Overall, I don't recommend using Windows Authenitcation on Java database applications. It removes a critical part of database security from the DBA and hands it over to the ActiveDirectory team. And in the case of internal subsystems, requires, I think, that an actual Windows logon ID be constructed for internal functions that might not actually belong to a human being. Not generally a good idea for production servers, since they're expected to run unattended outside of occasional maintenance and control by sysadmins - who should be logging in under personal IDs, not a shared ID if you want happy auditors.
Frank Mi wrote:Oh, I totally misunderstood it. Because I always see an "OP" asks questions, and a "STAFF" answers them. So I thought "OP" means a new user or non-staff.
Stephan van Hulst wrote:The problem is caused because you are accessing the database as you are rending the view. After you have rendered each row you close the connection. By the time you press a button, the connection is already closed.