Simpler is better!

1. CREATE - to create objects in the database
2. ALTER - alters the structure of the database
3. DROP - delete objects from the database
4. TRUNCATE - remove all records from a table, including all spaces allocated for the records are removed
5. COMMENT - add comments to the data dictionary
6. RENAME - rename an object

DML

1. SELECT - retrieve data from the a database
2. INSERT - insert data into a table
3. UPDATE - updates existing data within a table
4. DELETE - deletes all records from a table, the space for the records remain
5. MERGE - UPSERT operation (insert or update)
6. CALL - call a PL/SQL or Java subprogram
7. EXPLAIN PLAN - explain access path to data
8. LOCK TABLE - control concurrency

DCL

1. GRANT - gives user's access privileges to database
2. REVOKE - withdraw access privileges given with the GRANT command

TCL

1. COMMIT - save work done
2. SAVEPOINT - identify a point in a transaction to which you can later roll back
3. ROLLBACK - restore database to original since the last COMMIT
4. SET TRANSACTION - Change transaction options like isolation level and what rollback segment to use

웹로직8.1에서 스프링 프레임워크를 사용한 war 형태의 웹어플리케이션을 배포할 때
아래와 같은 오류가 발생한 다면..

weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: start() failed.
 Module: batman Error: weblogic.management.DeploymentException: Cannot set web app root system property when WAR file is not expanded - with nested exception:
[java.lang.IllegalStateException: Cannot set web app root system property when WAR file is not expanded]

 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2423)
 at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2138)
 at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2237)
 at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2132)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2384)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)


아마도 log4j 설정과 관련이 있을 것입니다.
web.xml 에서 log4j listener 설정 부분을 제거하라.

 <!--
 <listener>
  <listener-class>
   org.springframework.web.util.Log4jConfigListener
  </listener-class>
 </listener>
 -->
 

1. 모든 문서는 UTF-8 인코딩으로 저장되어야 함.
   이클립스의 경우 Properties->Info->Text file encoding->Other 을 UTF-8 로 설정함.

2. JSP 파일 상단에 다음과 같이 인코딩 설정.

    <%@ page contentType="text/html;charset=UTF-8" %>
 
3. 서블릿인 경우 아래와 같은 코드로 인코딩 처리.

    response.setContentType("text/html;charset=UTF-8");

4. 자바스크립트에서 GET 방식으로 URL에 파라미터를 넘길 경우 아래처럼 인코딩 처리.

    encodeURIComponent("Get방식한글");

5. Tomcat 서버일 경우 server.xml에서 Connector 요소에 URIEncoding="UTF-8" 속성을 추가.
 
    <Connector port="8080" maxHttpHeaderSize="8192"
        maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
        enableLookups="false" redirectPort="8443" acceptCount="100"
        connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="UTF-8" />
 
6. HttpURLConnection 을 통하여 UTF-8로 된 URL을 읽을 경우.

    BufferedReader reader = new BufferedReader(
        new InputStreamReader(conn.getInputStream(), "UTF-8"));

7. JSP -> Bean 데이터 전송은 문제 없지만 JSP -> JSP 에서 한글이 깨진다면 받는 부분에서 아래처럼 처리.

    String test = request.getParameter("test");
    test = new String(test .getBytes("8859_1"), "UTF-8");

8. MySQL 등 DBMS 역시 기본으로 UTF-8 세팅이 되어있어야 함.

9. UTF-8으로 인코딩 된 파일을 자바로 읽을 경우.

    BufferedReader reader = new BufferedReader(new InputStreamReader(in, "UTF-8"));