Labels

.net (1) *nix (1) administration (1) Android (2) Axis2 (2) best practice (5) big-data (1) business-analysis (1) code re-use (1) continuous-integration (1) Cordova-PhoneGap (1) database (2) defect (1) design (3) Eclipse (7) education (1) groovy (2) https (2) Hudson (4) Java (1) JAX-RS (2) Jersey (3) Jetty (1) localization (1) m2eclipse (2) MapForce (1) Maven (12) MySQL (1) Nexus (4) notes (4) OO (1) Oracle (4) performance (1) Perl (1) PL/SQL (1) podcast (1) PostgreSQL (1) requirement (1) scripting (1) serialization (1) shell (1) SoapUI (1) SQL (1) SSH (2) stored procedure (1) STS (2) Subclipse (1) Subversion (3) TOAD (3) Tomcat (4) UML (2) unit-testing (2) WAMP (1) WAS (3) Windows (3) WP8 (2) WTP (2) XML (4) XSLT (1)

Friday, November 26, 2010

Tomcat installation changed, problems launching Tomcat in Eclipse

  • Install location of Tomcat has changed.  Get message "The archive: [...]/apache-tomcat-6.0.20/bin/bootstrap.jar which is referenced by the classpath, does not exist." when attempting to launch Tomcat in Eclipse
  • Fix: 
    1. In Servers view, double-click on Tomcat server.  Overview of Tomcat settings appears.  
    2. Click on "Open launch configuration"
    3. Go to Classpath tab
    4. Edit User Entries as appropriate
  • If you haven't already, specify your Tomcat installation under Preferences > Server > Runtime Environments

Tuesday, November 2, 2010

Compiling PL/SQL and using TOAD to write stored procedures

  • PL/SQL compiler (version?) is quite stupid:  Missing a semi-colon flags a line several lines below where the actual semi-colon is missing.  Likewise for a missing single quote character
  • To escape the single quote character, double it.  Therefore four consecutive single quotes is a string consisting of a single quote
  • When the compiler reports a compiler error at a certain line, that line # is relative to the start of the Body of stored procedure (assuming you are editing the Body and not the Spec)
  • To compile and "save" your stored procedure to the Oracle server in TOAD, be sure to use the "Execute As Script" button () in the Editor.  Do NOT use the "Execute/compile statement at caret" button.
  • In order to see debug output (i.e. from DBMS_OUTPUT.PUT_LINE function):  Where does DBMS_OUTPUT.PUT_LINE() output go (in Toad) ?