亚洲免费一级视频,亚洲成a人片77777老司机,亚洲人成77777在线播放网站

一步一步教你远�E�调用EJB

飞鸟 — Wed, 28 Mar 2007 12:36:00 GMT

前期准备�Q�弄清楚weblogic�Q�或jboss�Q�、tomcat、JBluder�Q�或eclipse�Q�MyEclipse�Q�的使用�Ҏ��Q�能写一个简单的��Z��struts框架的web工程�Q�然后准备两台联�|�的电脑�Q�局域网也可以）�Q�如果没有条�Ӟ��也可以在同一台电脑上分别安装两个web服务器（例如�Q�weblogic和tomcat�Q�来代替�Q�本文将采用后一�U�方法，采用weblogic作EJB容器�Q�tomcat作web容器�Q�用struts工程来调用EJB

准备好了吗？让我们开始下一�?/p>

�W�一步：写一个简单的EJB。写EJB最好用的还是JBuilder�Q�毕竟够�ȝ��化。当然作��Z��业�h士，eclipse搭配MyEclipse是最佳选择�Q�不�q�作为初学者，��采用JBuilder。以下是本文��试所用到的EJB�?/p>

remote接口�Q?/p>

package testhello;

import javax.ejb.EJBObject;

public interface SayHello extends EJBObject {
public String sayHello(String name) throws java.rmi.RemoteException;
}

home接口�Q?/p>

package testhello;

import javax.ejb.EJBHome;
import javax.ejb.CreateException;
import java.rmi.RemoteException;

public interface SayHelloHome extends EJBHome {
public SayHello create() throws CreateException, RemoteException;
}

bean�c�：

package testhello;

import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import javax.ejb.CreateException;

public class SayHelloBean implements SessionBean {
    SessionContext sessionContext;
    public void ejbCreate() throws CreateException {
    }

public void ejbRemove() {
}

public void ejbActivate() {
}

public void ejbPassivate() {
}

    public void setSessionContext(SessionContext sessionContext) {
        this.sessionContext = sessionContext;
    }

    public String sayHello(String name) {
        return "Hello "+name;
    }
}

如果你是采用上面两种工具来写的话�Q�配�|�文件就不必考虑�?/p>

�W�二步：利用JBuilder或eclipse��这个EJB工程�~�译�q�打包，会得��C��个jar(如果你的工程名叫testhello�Q�那么这个jar文�g��是testhello.jar)文�g。如果你的EJB容器�Q�weblogic或JBoss�Q�是在本��Z��Q�那么在JBuilder或eclipse中就可以直接鼠标叛_��EJB工程�Q�来部��vEJB。如果需要部�|�到�q�程服务器上�Q�只需要通过EJB容器的控制台��testhello.jar上传到远�E�端�Q�然后在EJB Modler里面按提�C�部�|�好EJB。最后，别忘了在JNDI Tree里面察看你的EJB工程的JNDI名，本例的JNDI名叫SayHello

�W�三步：��remote接口和home接口打包成jar文�g�Q�copy��C��要远�E�调用EJB的struts工程下的lib目录�Q�例如：helloapp ->WEB-INF ->lib�Q?/p>

�W�四步：��weblogic的weblogic.jar�Q�在weblogic的安装目录－>weblogic81�Q?gt;server�Q?gt;lib文�g夹中�Q�copy到tomcat安装目录下的�Q?gt;shared�Q?gt;lib文�g夹中�Q�其实这里我们需要用到的只是weblogic.jar里的几个class文�g而已�Q�不�q�对于初学者而言�Q�先不必��L��I�到底只需要那几个class�?/p>

�W�五步：�~�写一个简单的struts工程�Q�其实这些都可以用工��L��成）�Q�一下是调用EJB的HelloAction的源代码(特别要注意的是，记得要将之前�W�三步生成的jar包导入编辑器中，否则下面的代码编译通不�q�。如果你不知道导入jar包，��把那个jar包多copy一份到你的jdk安装目录 -> jre-> lib-> ext文�g夹下)

package logging.actions;
import logging.Constants;

import java.util.*;
import javax.servlet.ServletException;
import javax.servlet.RequestDispatcher;
import javax.servlet.http.HttpSession;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.rmi.PortableRemoteObject;

import org.apache.struts.action.Action;
import org.apache.struts.action.ActionForm;
import org.apache.struts.action.ActionForward;
import org.apache.struts.action.ActionMapping;
import org.apache.struts.action.ActionMessage;
import org.apache.struts.action.ActionMessages;
import org.apache.struts.util.MessageResources;
import org.apache.struts.validator.DynaValidatorForm;

public final class HelloAction extends Action{

public ActionForward execute(ActionMapping mapping,
         ActionForm form,
         HttpServletRequest request,
         HttpServletResponse response)
throws Exception{

InitialContext ctx=this.getInitialContext();

//查找JNDI名�ؓSayHello的EJB�l��g
Object obj=ctx.lookup("SayHello");

//获得�q�程EJB�l��g的home接口的引�?br /> testhello.SayHelloHome home=(testhello.SayHelloHome)PortableRemoteObject.narrow(obj,testhello.SayHelloHome.class);

  //获得�q�程EJB�l��g的remote接口的引�?br />       testhello.SayHello hello=home.create();

       String name="飘然随风";
       String sayString=hello.sayHello(name);

       request.setAttribute("userName",name);
       request.setAttribute("passWord",sayString);
       request.removeAttribute(mapping.getAttribute());

  return mapping.findForward("loginSuccess");
}

/*以下�Ҏ��是作用是�Q�通过传递环境属性选择JNDI驱动和服务器的网�l�位�|�，
�q�连接到�q�接到JNDI树�?br /> �q�是采用weblogic做EJB容器�Ӟ��q�程调用EJB的固定初始化模式�Q�初学者可以死��C��?br />*/
private InitialContext getInitialContext() throws Exception {
  //EJB容器的地址
    String url = "t3://image:7001";
    String user = null;
    String password = null;
    Properties properties;

        properties = new Properties();
        properties.put(Context.INITIAL_CONTEXT_FACTORY,
                       "weblogic.jndi.WLInitialContextFactory");
        properties.put(Context.PROVIDER_URL, url);
        if (user != null) {
            properties.put(Context.SECURITY_PRINCIPAL, user);
            properties.put(Context.SECURITY_CREDENTIALS,
                           password == null ? "" : password);
        }
        return new javax.naming.InitialContext(properties);
}
}

�W�六步：如果你严格按照上面的步骤做了�Q�那么剩下的��是同时启动weblogic和tomcat来测试了�?/p>

飞鸟 2007-03-28 20:36 发表评论

Tomcat环境下，字符�~�码的filter

飞鸟 — Mon, 26 Mar 2007 09:47:00 GMT

在web.xml中，配置"Set Character Encoding" filter�Q�可以实现客��L��传入服务器端的Request对象中的数据的正��解码�?/p>

我��用的filter是Craig McClanahan写的�Q�这位仁兄大名鼎鼎，他是Struts框架的主要体�p�设计师和开发者，Tomcat4的主设计师和Java Web Services Developer Pack实现包的主设计师�Q�领导着Sun的JavaServer Faces规范开发，同时也是Java EE�q�_��的Web Layer Archiecture。filter的代码附在文后�?/p>

web.xml中的配置如下�Q?/p>

Set Character Encoding
filters.SetCharacterEncodingFilter

encoding
GBK

Set Character Encoding
/*

/*
* Copyright 2004 The Apache Software Foundation
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES or CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/

package filters;

import java.io.IOException;
import javax.servlet.Filter;
import javax.servlet.FilterChain;
import javax.servlet.FilterConfig;
import javax.servlet.ServletException;
import javax.servlet.ServletRequest;
import javax.servlet.ServletResponse;

/**
*

Example filter that sets the character encoding to be used in parsing the
* incoming request, either unconditionally or only if the client did not
* specify a character encoding. Configuration of this filter is based on
* the following initialization parameters:

encoding - The character encoding to be configured
* for this request, either conditionally or unconditionally based on
* the ignore initialization parameter. This parameter
* is required, so there is no default.

ignore - If set to "true", any character encoding
* specified by the client is ignored, and the value returned by the
* selectEncoding() method is set. If set to "false,
* selectEncoding() is called only if the
* client has not already specified an encoding. By default, this
* parameter is set to "true".

*
*

Although this filter can be used unchanged, it is also easy to
* subclass it and make the selectEncoding() method more
* intelligent about what encoding to choose, based on characteristics of
* the incoming request (such as the values of the Accept-Language
* and User-Agent headers, or a value stashed in the current
* user's session.

*
* @author Craig McClanahan
* @version $Revision: 1.2 $ $Date: 2004/03/18 16:40:33 $
*/

public class SetCharacterEncodingFilter implements Filter {

// ----------------------------------------------------- Instance Variables

/**
* The default character encoding to set for requests that pass through
* this filter.
*/
protected String encoding = null;

/**
* The filter configuration object we are associated with. If this value
* is null, this filter instance is not currently configured.
*/
protected FilterConfig filterConfig = null;

/**
* Should a character encoding specified by the client be ignored?
*/
protected boolean ignore = true;

// --------------------------------------------------------- Public Methods

/**
* Take this filter out of service.
*/
public void destroy() {

this.encoding = null;
this.filterConfig = null;

}

/**
* Select and set (if specified) the character encoding to be used to
* interpret request parameters for this request.
*
* @param request The servlet request we are processing
* @param result The servlet response we are creating
* @param chain The filter chain we are processing
*
* @exception IOException if an input/output error occurs
* @exception ServletException if a servlet error occurs
*/
public void doFilter(ServletRequest request, ServletResponse response,
FilterChain chain)
throws IOException, ServletException {

// Conditionally select and set the character encoding to be used
if (ignore || (request.getCharacterEncoding() == null)) {
String encoding = selectEncoding(request);
if (encoding != null)
request.setCharacterEncoding(encoding);
}

// Pass control on to the next filter
chain.doFilter(request, response);

}

/**
* Place this filter into service.
*
* @param filterConfig The filter configuration object
*/
public void init(FilterConfig filterConfig) throws ServletException {

this.filterConfig = filterConfig;
this.encoding = filterConfig.getInitParameter("encoding");
String value = filterConfig.getInitParameter("ignore");
if (value == null)
this.ignore = true;
else if (value.equalsIgnoreCase("true"))
this.ignore = true;
else if (value.equalsIgnoreCase("yes"))
this.ignore = true;
else
this.ignore = false;

}

// ------------------------------------------------------ Protected Methods

/**
* Select an appropriate character encoding to be used, based on the
* characteristics of the current request and/or filter initialization
* parameters. If no character encoding should be set, return
* null.
*

* The default implementation unconditionally returns the value configured
* by the encoding initialization parameter for this
* filter.
*
* @param request The servlet request we are processing
*/
protected String selectEncoding(ServletRequest request) {

return (this.encoding);

}

}

飞鸟 2007-03-26 17:47 发表评论

HelloWorld EJB代码�~�写

飞鸟 — Fri, 23 Mar 2007 13:33:00 GMT

HelloWorld EJB代码�~�写

　　1.�~�写��L��口程�?/font>
　　在文本编辑器中编�?font color="#ff0000">HelloHome.java文�g�Q��ƈ保存在C:\work\hello目录下，其代码�ؓ�Q?br />　　//本接口需要引入的�c�L��接口
　　import java.rmi.RemoteException;
　　import javax.ejb.CreateException;
　　import javax.ejb.EJBHome;
　　//定义��L��口，必须�l�承EJBHome
　　public interface HelloHome extends EJBHome {
　 //定义EJB创徏�Ҏ��
　　　Hello create() throws CreateException, RemoteException;
　　}
　　2.�~�写�q�程接口�E�序
　　在文本编辑器中编�?font color="#ff0000">Hello.java文�g�Q��ƈ保存在C:\work\hello目录下。Hello.java文�g的代码�ؓ�Q?br />　　//本接口需要引入的�c�L��接口
　　import javax.ejb.EJBObject;
　　import java.rmi.RemoteException;
//定义�q�程接口�Q�必��ȝ��承EJBObject
　　public interface Hello extends EJBObject {
　　　//定义业务逻辑�Ҏ��
　　　public String sayHello()
　　　throws RemoteException;
　　}
3.�~�写Bean�c�d��现程�?/strong>
　　在文件编辑器中编�?font color="#ff0000">HelloBean.java文�g�Q��ƈ保存在C:\work\hello目录下。HellloBean.java文�g的代码�ؓ�Q?br />　　//本类需要引入的�c�L��接口
　　import javax.ejb.CreateException;
　　import javax.ejb.SessionBean;
　　import javax.ejb.SessionContext;
　　//实现业务逻辑�Q�必��d��现SessionBean接口
　　public class HelloBean implements SessionBean {
　　　//�q�是个会话EJB�Q�声明会话上下文
　　　private SessionContext ctx;
　　　//声明字符�?br />　　　private String words;
　　　//接口SessionBean中定义的�Ҏ��Q�必��d��?br />　　　public void setSessionContext(SessionContext ctx) {
　　　　this.ctx = ctx;
　　　}
　　　//接口SessionBean中定义的�Ҏ��Q�必��d��?br />　　　public void ejbActivate() {
　　　}
　　　//接口SessionBean中定义的�Ҏ��Q�必��d��?br />　　　public void ejbPassivate() {
　　　}
　　　//接口SessionBean中定义的�Ҏ��Q�必��d��?br />　　　public void ejbRemove() {
　　　}
　　　//和主接口定义对应的方法，必须实现
　　　public void ejbCreate() throws CreateException {
　　　　words = "Hello World";
　　　}
　　　//供客��L��调用的业务逻辑�Ҏ��Q�这里只��单的打印字符�Ԍ��q�把字符串返回到客户�?br />　　　public String sayHello()
　　　{
　　　　System.out.println("I am in an EJB of Server ."+words);
　　　　return words;
　　　}　　}
�Q?�Q?EJB代码�~�译
　　首先打开命��o�H�口�Q�进入C:\work\hello目录�Q�运行环境变量脚本程序：
　　　c:\work\hello>c:\work\setEnv
　　建立build目录�Q?br />　　　c:\work\hello>md build
　　执行�~�译命��o�Q?br />　　　c:\work\hello>java -d build Hello.java HelloHome.java HelloBean.java
　　其中�Q?d build 表示�~�译生成的class文�g攑֜�build目录中�?br />�Q?�Q�EJB部��v文�g�~�写
　　部��v文�g是EJB的重要组成部分。简单地��_��部��v文�g��是EJB的说明文�Ӟ��q�个文�g由服务器容器使用�Q�服务器�Ҏ��部��v文�g的说明来��理EJB�?br />　　EJB部��v文�g是标准的XML文�g�Q�必��遵守XML的语法规则。此外，�q�要遵守相关的DTD规则�?br />　　部��v文�g到少有两个文件ejb-jar.xml和weblogic-ejb-jar.xml。前者�ؓEJB自��n的一些特征，如名�U�、组成等�Q�后者是和EJB部��v相关的描�q��?br />　　�~�写部��v文�g�Q?br />　　(1)在文件编辑器中编辑ejb-jar.xml文�g�Q��ƈ保存在C:\work\hello目录下。ejb-jar.xml文�g的内容�ؓ�Q?br />

images/green-cube.gif

images/orange-cube.gif

HelloHome

HelloBean

Stateless
Container

MyFirstEJB
Remote
*

Required

　　(2)在文件编辑器中编辑weblogic-ejb-jar.xml文�g�Q��ƈ保存在C:\work\hello目录下。weblogic-ejb-jar.xml文�g的内容�ؓ�Q?br />

100

HelloHome

�Q?�Q?打包
　　把上面开发的所有文件打成jar文�g包。这些文件包括一三个�c�L��Ӟ��Hello.class、HelloHome.class、HelloBean.class和部�|�文�Ӟ��ejb-jar.xml,weblogic-ejb-jar.xml。打包时�Q�文件放�|�的位置是严��D��求的。具体�ؓ�Q?.class文�g攑֜�当前目录(即C:\work\hello\build目录�?�Q�部�|�文件必��d��在下一�U�目录Meta-inf�?即C:\work\hello\build\Meta-inf目录�?。如果EJB包含囑փ�文�g�Q�则囑փ�文�g必须在build目录的下一�U�目录images�?即C:\work\hello\build\images目录�?�?br />　　具体操作步骤为：
　　(1)在build目录中创建Meta-inf目录�Q�当前�\径�ؓC:\work\hello�Q�执行：
　　　c:\work\hello>md build\Meta-inf
　　(2)把部�|�文件拷贝到hello\Meta-inf目录下：
　　　c:\work\hello>copy *.xml build\Meta-inf
　　(3)执行�Q?br />　　　c:\work\hello>md build\images
　　　c:\work\hello>copy *.gif build\images
　　当然�Q�本例中没有使用囑փ�文�g�Q�所以可以免��L��步骤�?br />　　(4)用jar命��o在build目录下打包。当前�\径是c:\work\hello�Q�运行：
　　　c:\work\hello>cd build
　　　c:\work\hello\bulid>jar cv0f std_myfirstejb_hello.jar META-INF *.class images
　　　c:\work\hello\build>cd..
　　其中�Q�jar是Jdk中的打包命��o�Q�cv0f是命令参敎ͼ�std_myfirstejb_hello.jar是生成的文�g名，��q��h��定�?br />　　命��o执行完后�Q�在目录build中应该生成文件std_myfirstejb_hello.jar�?br />　　��x��Q�打包完成�?
�Q?�Q�编译生成窗口代�?/strong>
　　Weblogic Server提供了编译生成容器代码的工具�Q�它是一个java�E�序weblogic.ejbc。在命��o行窗口中执行�Q?br />　　c:\work\hello>java weblogic.ejbc -compiler javac build\std_myfirstejb_hello.jar build\myfirstejb_hello.jar
　　可以看出ejbc把std_myfirstejb_hello.jar文�g�~�译成myfirstejb_hello.jar�Q�它包括了Weblogic Server�q�_��可以识别的ejb容器代码�?br />　　如果�q�行成功�Q�则在build目录下��生myfirstejb_hello.jar文�g�?/p>

飞鸟 2007-03-23 21:33 发表评论

飞鸟 — Thu, 22 Mar 2007 14:34:00 GMT
     摘要: JSP Struts �? HTML 标签库详�? Stru...  阅读全文

飞鸟 2007-03-22 22:34 发表评论

飞鸟 — Thu, 22 Mar 2007 14:05:00 GMT

�W�一步徏立Weblogic Server的project�Q?/font>

(1)安装破解Weblogic 8.3.1�? www.9iv.com )�Q�运行Configuration Wizard�Q?/font>

(2)选择Create a new Weblogic configuraion�Q?/font>

(3)Select a Configuration Template中选择Basic Weblogic Server Domain�Q?/font>

(4)Chose Express or Custom Configuration中我选择的是Express(如果寚w��|�很熟悉�q�是选择Custom比较好些)�Q?/font>

(5)在Configure Administrative Username and Password中设�|�用户名和密码；

(6)在Configure Server Start Mode and Java SDK中我选择了Development Mode�Q�在JDK中选择了BEA默认安装的Sun JDK 1.4.2_04�Q?/font>

(7)在下一步部�|�中输入需要的Congfiguration Name��可以Create了�?/font>

�W�二步在MyEclipse配置Weblogic�Q?/font>

(1)选择菜单Window->Preferences->MyEclipse->Application Servers->Weblogic 8�Q�配�|�项目如下：

BEA home directory: 选择Bea的安装目�?/font>

Weblogic installation directory:现在BEA下面的weblogic81目录

Admin username:输入上面在配�|�过�E�中讄��用户�?/font>

Admin password:输入刚才讄��密码

Execution domain root:选择BEA下user_projects\domains目录下上面第一步创建的目录

Execution domain name:输入上面那个目录的名�U?/font>

Execution server name:输入上一步的那个Congfiguration Name

Hostname:PortNumber:输入IP地址和监听的端口

Security policy file:输入BEA安装目录下的\weblogic81\server\lib\weblogic.policy

(2)在Weblogic 8下面配置JDK�Q�在WLS JDK name那里选择新徏�Q�弹出的对话框中选择BEA下面的JDK安装路径�Q�输入一个名字确定就可以�Q�在Optional Java VM arguments对话框里面输�?ms64m -mx64m -Djava.library.path="D:/BEA/weblogic81/server/bin" -Dweblogic.management.discover=false -Dweblogic.ProductionModeEnabled=false

(3在Weblogic 8下面配置Paths�Q�加入BEA安装路径�?weblogic81/server/lib中的webservices.jar和weblogic.jar两个包。如果需要其他的包，也在�q�里加入�?/font>

飞鸟 2007-03-22 22:05 发表评论

飞鸟 — Fri, 09 Mar 2007 08:12:00 GMT

log4j��??xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /?>

��单的�?span lang="EN-US" twffan="done">log4j��是帮助开发�h员进行日志输出管理的API�c�d��。它最重要的特点就

可以配置文�g灉|��的设�|?/span> 日志信息的优先��、日志信息的输出目的��C��及日志信息的输出格式�?span lang="EN-US" twffan="done">

Log4j除了可以记录�E�序�q�行日志信息外还有一重要的功能就是用�?/span> 昄��调试信息。程序员�l�常会遇到脱��?span lang="EN-US" twffan="done">java ide环境调试�E�序的情况，�q�时大多��C�h会选择使用System.out.println语句输出某个变量值的�Ҏ��q�行调试。这样会带来一个非帔R��烦的问题�Q�一旦哪天程序员军_��不要昄��q�些System.out.println的东西了��只能一行行的把�q�些垃圾语句注释掉。若哪天又需调试变量��|��则只能再一行行��L��q�些注释恢复System.out.println语句。��用log4j可以很好的处理类似情��c�?o:p>

log4j使用�Ҏ��

下面介绍的是log4j一些理论方面的知识�Q�读者觉得枯燥的话可以蟩�q�本节直接阅�ȝ��三节实例部分�?o:p>

　　1、定义配�|�文�?o:p>

　首先使用配置文�g��我们的应用程序更加灵�z�配�|�log日志输出方式包括输出优先�U�、输出目的地、输出格式。Log4j支持两种配置文�g格式�Q�一�U�是XML格式的文�Ӟ��一�U�是Java�Ҏ��文件log4j.properties�Q�键=��|��。下面将介绍使用log4j.properties文�g作�ؓ配置文�g的方法：

　　 �?/span> 配置根Logger�Q�其语法为：0

　　log4j.rootLogger = [ level ] , appenderName, appenderName, �?

　　其中�Q?span lang="EN-US" twffan="done">level 是日志记录的优先�U�，分�ؓOFF、FATAL、ERROR、WARN、INFO、DEBUG、ALL或者自定义的��别。Log4j��只��用四个��别，优先�U�从高到低分别是ERROR、WARN、INFO、DEBUG。通过在这里定义的�U�别�Q�您可以控制到应用程序中相应�U�别的日志信息的开兟뀂比如在�q�里定义了INFO�U�别�Q�则应用�E�序中所有DEBUG�U�别的日志信息将不被打印出来�?appenderName��是指定日志信息输出到哪个地斏V��可同时指定多个输出目的地�?

　　 �?/span> 配置日志信息输出目的地Appender�Q�其语法为：

　　 log4j.appender.appenderName = fully.qualified.name.of.appender.class
　　log4j.appender.appenderName.option1 = value1
　　�?
　　log4j.appender.appenderName.option = valueN

　　其中�Q?/font> Log4j提供的appender有以下几�U�：
　　org.apache.log4j.ConsoleAppender�Q�控制台�Q�，
　　org.apache.log4j.FileAppender�Q�文�Ӟ��Q?
　　org.apache.log4j.DailyRollingFileAppender�Q�每天��生一个日志文�Ӟ��Q?br />　　org.apache.log4j.RollingFileAppender�Q�文件大��到达指定尺寸的时候��生一个新的文�Ӟ��Q?
　　org.apache.log4j.WriterAppender�Q�将日志信息以流格式发送到��L��指定的地方）

　 �?/span> 配置日志信息的格式（布局�Q�，其语法�ؓ�Q?o:p>

　　 log4j.appender.appenderName.layout = fully.qualified.name.of.layout.class
　　log4j.appender.appenderName.layout.option1 = value1
　　�?
　　log4j.appender.appenderName.layout.option = valueN

　　其中�Q?/font> Log4j提供的layout有以下几�U�：
　　org.apache.log4j.HTMLLayout�Q�以HTML表格形式布局�Q�，
　　org.apache.log4j.PatternLayout�Q�可以灵�z�d��指定布局模式�Q�，
　　org.apache.log4j.SimpleLayout�Q�包含日志信息的�U�别和信息字�W�串�Q�，
　　org.apache.log4j.TTCCLayout�Q�包含日志��生的旉��、线�E�、类别等�{�信息）

　　Log4J采用�c�M��C语言中的printf函数的打印格式格式化日志信息�Q�打印参数如下： %m 输出代码中指定的消息

　　 %p 输出优先�U�，即DEBUG�Q�INFO�Q�WARN�Q�ERROR�Q�FATAL
　　%r 输出自应用启动到输出该log信息耗费的毫�U�数
　　%c 输出所属的�cȝ��Q�通常��是所在类的全�?
　　%t 输出产生该日志事件的�U�程�?
　　%n 输出一个回车换行符�Q�Windows�q�_��为“\r\n”，Unix�q�_��为“\n�?
　　%d 输出日志旉��点的日期或时��_��默认格式为ISO8601�Q�也可以在其后指定格式，比如�Q?d{yyy MMM dd HH:mm:ss,SSS}�Q�输出类��|�� 2002�q?0�?8�?/font> 22�Q?0�Q?8�Q?21
　　%l 输出日志事�g的发生位�|�，包括�cȝ��名、发生的�U�程�Q�以及在代码中的行数。�D例：Testlog4.main(TestLog4.java:10)

　　2、在代码中��用Log4j

　　 �?/span> 得到记录�?o:p>

　　使用Log4j�Q�第一步就是获取日志记录器�Q�这个记录器��负责控制日志信息。其语法为：

　　public static Logger getLogger( String name)

　　通过指定的名字获得记录器�Q�如果必要的话，则�ؓ�q�个名字创徏一个新的记录器�?span lang="EN-US" twffan="done">Name一般取本类的名字，比如�Q?

　　static Logger logger = Logger.getLogger ( ServerWithLog4j.class.getName () )

　　 �?/span> ��d��配置文�g

　　当获得了日志记录器之后，�W�二步将配置Log4j环境�Q�其语法为：

BasicConfigurator.configure ()�Q?自动快速地使用�~�省Log4j环境�?br />　　PropertyConfigurator.configure ( String configFilename) �Q�读取��用Java的特性文件编写的配置文�g�?o:p>

例：PropertyConfigurator.configure (".\\src\\log4j.properties")
　　DOMConfigurator.configure ( String filename ) �Q�读取XML形式的配�|�文件�?o:p>

　　 �?/span> 插入记录信息�Q�格式化日志信息�Q?o:p>

　　当上两个必要步骤执行完毕�Q�就可轻村֜�使用不同优先�U�别的日志记录语句插入到您想记录日志的�Q何地方，其语法如下：

　　 Logger.debug ( Object message ) ;
　　Logger.info ( Object message ) ;
　　Logger.warn ( Object message ) ;
　　Logger.error ( Object message ) ;

log4j范例�E�序

下面��用一个最��单的范例�E�序来进一步说�?span lang="EN-US" twffan="done">log4j的��用方法。程序代码如下：

import org.apache.log4j.*;

public class LogTest {

    static Logger logger = Logger.getLogger(LogTest.class.getName());

    public static void main(String[] args) {

        PropertyConfigurator.configure ( �?\\src\ log4j.properties �? �Q?/span>

logger.debug( "Debug ..." );

        logger.info( "Info ..." );

        logger.warn( "Warn ..." );

        logger.error( "Error ..." );

    }

}

�E�序说明�Q?span lang="EN-US" twffan="done">

�?/span> static Logger logger = Logger.getLogger(LogTest.class.getName()); ��是创徏一个属�?/span> LogTest �cȝ�� Logger 对象�Q�创建时要告�?/span> Logger 你当前的 Class 是什么�?/span>

�?/span> PropertyConfigurator.configure ( �?/span> log4j.properties �? ��是说��用当前工�E�目录下�?/span> src 文�g夹中�?/span> log4j.properties 文�g作�ؓ配置文�g。若��?/span> log4j.properties 攑֜�工程根目录下也可不写此句�Q�程序会自动扑ֈ�配置文�g�?/span>

�?/span> logger.debug ��是输出 debug 的信息， logger.info ��是输出提示信息�Q?/span> logger.warn ��是昄��警告信息�Q?/span> logger.error ��是昄��错误信息�?/span>

下面是配�|�文�?/span> log4j.properties 的内容：

log4j.rootCategory=DEBUG, stdout �Q?/span> R

log4j.appender.stdout=org.apache.log4j.ConsoleAppender

log4j.appender.stdout.layout=org.apache.log4j.PatternLayout

log4j.appender.stdout.layout.ConversionPattern=%5p (%F:%L) - %m%n

log4j.appender.R=org.apache.log4j.RollingFileAppender

log4j.appender.R.File=log.txt

log4j.appender.R.MaxFileSize=100KB

log4j.appender.R.MaxBackupIndex=1

log4j.appender.R.layout=org.apache.log4j.PatternLayout

log4j.appender.R.layout.ConversionPattern=%d { yyyy MMM dd HH:mm:ss } %-5p %c - %m%n

�E�序说明�Q?span lang="EN-US" twffan="done">

�?/span> log4j.rootCategory=DEBUG, stdout �Q?/span> R

��是说我要显�C�所有优先权�{�於和高�?/span> Debug的信息�?br />"stdout"�Q?/span> ”R�?/span> 表示我定义了两个输出�?/span> ( 随便什么名字都�?/span> ) �?/span>

�?/span> 下面的三行说 stdout 输出端其实是标准输出 Console �Q�也��是屏幕。输出的格式�?/span> Pattern Layout 。�{换方式是 %5p (%F:%L) - %m%n �Q�即前五格用来显�C�Z��先权�Q�再昄��当前的文件名�Q�加当前的行数。最后是 logger.debug() �?/span> logger.info() �?/span> logger.warn() �?/span> logger.error() 里的信息�?/span> %n 表示回�R�I��?/span>

�?/span> 再加上下面六行则 log 信息不光昄��在屏�q�上�Q�而且��被保存在一个叫 "log.txt" 的文仉��Q�文件最大�ؓ 100KB 。如果文件大��超�q?/span> 100KB �Q�文件会被备份成 "log.txt.1" �Q�新�?/span> "log.txt" �l�箋记录 log 信息�?/span>

接下来我们可以改�?/span> log4j.properties �Q�而不需重新�~�译��可以控�?/span> log 信息是否昄��?/span> log 信息的输出端�c�d��、输出方式、输出格式，�{�等。�D例如下：

�?/span> �?/span> log4j.properties 文�g里把 "log4j.rootCategory=DEBUG,stdout,R" 改写�?/span> "log4j.rootCategory=OFF, stdout,R" �Q�这��h��有的 log信息都不会显�C�Z��Q�解决了本文开始提出的问题�?br />�?/span> �?/span> log4j.properties 文�g里把 "log4j.rootCategory=DEBUG,stdout,R" 改写�?/span> "log4j.rootCategory=INFO, stdout,R" �Q�这样只昄�� INFO, WARN, ERROR �?/span> log 信息�Q��?/span> DEBUG 信息不会被显�C�；

�?span lang="EN-US" twffan="done">web�E�序中��用log4j注意问题

1�?span style="FONT: 7pt 'Times New Roman'" twffan="done">    �׃��jsp或servlet在执行状态时没有当前路径概念�Q�所有��?/span> PropertyConfigurator.configure �Q?/span> String �Q�语句找 log4j.properties 文�g时要�l�出相对于当�?/span> jsp �?/span> servlet 的�\径�{化成��Z��个绝对的文�g�pȝ��路径。方法是使用 servletcontext.getrealpath(string) 语句。例�Q?/span>

//得到当前jsp路径

String prefix = getServletContext().getRealPath( "/");

//��d�� log4j.properties

PropertyConfigurator.configure(prefix+ "\\WEB-INF\\log4j.properties");

2、相应的log4j.properties讄��某个属性时也要在程序中讄��l�对路径。例�Q?o:p>

log4j.appender.R.File属性设�|�日志文件存放位�|�。我们可以用��d��.properties配置文�g的方法进行灵�z�设�|��?/span>

飞鸟 2007-03-09 16:12 发表评论

jakarta dbcp属性说明（上）

飞鸟 — Thu, 18 May 2006 06:04:00 GMT

Parameters

Parameter Description

username The connection username to be passed to our JDBC driver to establish a connection.

password The connection password to be passed to our JDBC driver to establish a connection.

url The connection URL to be passed to our JDBC driver to establish a connection.

driverClassName The fully qualified Java class name of the JDBC driver to be used.

connectionProperties The connection properties that will be sent to our JDBC driver when establishing new connections.

Format of the string must be [propertyName=property;]*

NOTE - The "user" and "password" properties will be passed explicitly, so they do not need to be included here.

Parameter Default Description

defaultAutoCommit true The default auto-commit state of connections created by this pool.

defaultReadOnly driver default The default read-only state of connections created by this pool. If not set then the setReadOnly method will not be called. (Some drivers don't support read only mode, ex: Informix)

defaultTransactionIsolation driver default The default TransactionIsolation state of connections created by this pool. One of the following: (see javadoc)
NONE
READ_COMMITTED
READ_UNCOMMITTED
REPEATABLE_READ
SERIALIZABLE

defaultCatalog The default catalog of connections created by this pool.

Parameter Default Description

initialSize 0 The initial number of connections that are created when the pool is started.

Since: 1.2

maxActive 8 The maximum number of active connections that can be allocated from this pool at the same time, or zero for no limit.

maxIdle 8 The maximum number of active connections that can remain idle in the pool, without extra ones being released, or zero for no limit.

minIdle 0 The minimum number of active connections that can remain idle in the pool, without extra ones being created, or zero to create none.

maxWait indefinitely The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception, or -1 to wait indefinitely.

Parameter Default Description

validationQuery The SQL query that will be used to validate connections from this pool before returning them to the caller. If specified, this query MUST be an SQL SELECT statement that returns at least one row.

testOnBorrow true The indication of whether objects will be validated before being borrowed from the pool. If the object fails to validate, it will be dropped from the pool, and we will attempt to borrow another.

NOTE - for a true value to have any effect, the validationQuery parameter must be set to a non-null string.

testOnReturn false The indication of whether objects will be validated before being returned to the pool.

NOTE - for a true value to have any effect, the validationQuery parameter must be set to a non-null string.

testWhileIdle false The indication of whether objects will be validated by the idle object evictor (if any). If an object fails to validate, it will be dropped from the pool.

NOTE - for a true value to have any effect, the validationQuery parameter must be set to a non-null string.

timeBetweenEvictionRunsMillis -1 The number of milliseconds to sleep between runs of the idle object evictor thread. When non-positive, no idle object evictor thread will be run.

numTestsPerEvictionRun 3 The number of objects to examine during each run of the idle object evictor thread (if any).

minEvictableIdleTimeMillis 1000 * 60 * 30 The minimum amount of time an object may sit idle in the pool before it is eligable for eviction by the idle object evictor (if any).

Parameter Default Description

poolPreparedStatements false Enable prepared statement pooling for this pool.

maxOpenPreparedStatements unlimited The maximum number of open statements that can be allocated from the statement pool at the same time, or zero for no limit.

This component has also the ability to pool PreparedStatements. When enabled a statement pool will be created for each Connection and PreparedStatements created by one of the following methods will be pooled:

public PreparedStatement prepareStatement(String sql)

public PreparedStatement prepareStatement(String sql, int resultSetType, int resultSetConcurrency)

NOTE - Make sure your connection has some resources left for the other statements.

Parameter Default Description

accessToUnderlyingConnectionAllowed false Controls if the PoolGuard allows access to the underlying connection.

When allowed you can access the underlying connection using the following construct:

Connection conn = ds.getConnection(); Connection dconn = ((DelegatingConnection) conn).getInnermostDelegate(); ... conn.close()

Default is false, it is a potential dangerous operation and misbehaving programs can do harmfull things. (closing the underlying or continue using it when the guarded connection is already closed) Be carefull and only use when you need direct access to driver specific extentions.

NOTE: Do not close the underlying connection, only the original one.

Parameter Default Description

removeAbandoned false Flag to remove abandoned connections if they exceed the removeAbandonedTimout.

If set to true a connection is considered abandoned and eligible for removal if it has been idle longer than the removeAbandonedTimeout. Setting this to true can recover db connections from poorly written applications which fail to close a connection.

removeAbandonedTimeout 300 Timeout in seconds before an abandoned connection can be removed.

logAbandoned false Flag to log stack traces for application code which abandoned a Statement or Connection.

Logging of abandoned Statements and Connections adds overhead for every Connection open or new Statement because a stack trace has to be generated.

If you have enabled "removeAbandoned" then it is possible that a connection is reclaimed by the pool because it is considered to be abandoned. This mechanism is triggered when (getNumIdle() < 2) and (getNumActive() > getMaxActive() - 3)

For example maxActive=20 and 18 active connections and 1 idle connection would trigger the "removeAbandoned". But only the active connections that aren't used for more then "removeAbandonedTimeout" seconds are removed, default (300 sec). Traversing a resultset doesn't count as being used.

飞鸟 2006-05-18 14:04 发表评论

关闭tomcat目录列表功能

飞鸟 — Tue, 16 May 2006 05:13:00 GMT

default情况下，如果你访问Tomcat下的一个WEB应用�Q�那么如果你输入的是一个目录名�Q�而且该目录下没有一个default�|�页,那么Tomcat ��会列出该目录下所有的文�g或是文�g夹，�q�样�l�我们带了很大的不安全，可能一些有用的资料�Q�被其他人很�Ҏ��获取.如果你想屏蔽�q�个�~�省行�ؓ�Q�那么可以修攏V�?/p>

conf/web.xml文�g:

default
org.apache.catalina.servlets.DefaultServlet

debug
0

listings
false

1

飞鸟 2006-05-16 13:13 发表评论

Struts数据库连接池配置

飞鸟 — Wed, 19 Apr 2006 06:45:00 GMT
在一个其于Struts的应用系�l�的设计�q�程中，最好能在web/表示层（presentation layer�Q�和你的商务逻辑�c�（包含所有数据访问操作的层）的中��_��定义一个Action�c�，作�ؓ��型的适配器（thin adapter�Q��?br />
  所以，你可以先定义一些商务API�Q�business API�Q�，�q�些API��是��单的Java�c�R��你可以传递一些参数给�q�些对象�Q��ƈ从这些对象返回一个Java Bean或者Java Bean的集合。这个Action�c�负责调用这些对象，�q�把它们�q�回的��g��递给web/表示层�?br />
  通常�Q�你可以为每一个你需要调用的商务�Ҏ��/商务�c�API创徏一个Action�c�R��理��x��况下�Q�所有的数据库访问代码都被封装进了这些商务API�c�里�Q�所以Struts�q�不知道你正在��用的持久层（persistent layer�Q�（甚至都不知道你��用了持久层）。它只需要传递一个主键（Key�Q�或者一个查询参敎ͼ�然后处理�q�回的结果bean或者bean集合。这��P��你就可以在其他的应用环境里复用这些商务API�c�，你还可以对这些独立于Struts或HTTP环境的商务API�q�行单体��试�?br />
  开始的时候，最��单的�Ҏ��是设计一�?:1的方案，��Z��的每一个商务API入口�Q�entry-point�Q�定义一个Action�c�R��当你的�l�验丰富了以后，你也可以使用DispatchAction�l�合�q�些Action�c�R��你甚至可以定义一个简单的"框架"Action�Q�用来调用所有的�q�些商务�c�R��你可以在contrib目录里找到Scaffold设计的ProcessAction�Q�这是一�?框架"Action的完整实现。��用这�U�方案可以��用更��的Action�c�，但你必须对Struts和MVC框架的底层实现有较深的理解。不要害怕在开始的时候定义过多的Action�Q�Struts的配�|�方案可以给予你充分的自由在以后重构你的设计�Q�因��Z��可以灉|��的改变你的Action�c�，而不会对应用�E�序造成影响�?br />
  在理��x��况下�Q�商务逻辑层（business logic layer�Q�应该封装所有的数据讉K��l�节�Q�包括数据库�q�接的获得。但是，一些应用程序的设计要求调用者可以从一个DataSource对象来获得数据库�q�接。遇到这�U�情冉|��Q�Struts DataSource��理器可以��你在需要的时候配�|�这些DataSource资源�?br />
  Struts DataSource��理器在Struts配置文�g�Q�Struts-config.xml�Q�里定义。这个管理器可以用来分发和配�|��Q何实��C��javax.sql.DataSource接口的数据库�q�接池（connection pool�Q�。如果你的DBMS或者容器内�|�了�W�合�q�些要求的连接池�Q�你可以优先选用它�?br />

�Q�Jakarta的公��p��接池实现 - BasicDataSource�Q?/strong>

  如果你的手头没有�q�接池的本地�Q�native�Q�实玎ͼ�你可以��用Jakarta提供的公��p��接池实现[org.apache.commons.dbcp.BasicDataSource]�Q�它可以和DataSource��理�?合作"的很好。另外，Struts�q�在它的util包里包含了一个GenericDataSource�c�，�q�也是一个连接池实现。但是这只是一个非常简单的实现�Ҏ��Q�不推荐使用�Q�因为它可能在Struts的以后版本中被BasicDataSource或其它的数据源实现替换掉�?br />
  下面是一�D�Struts-config.xml配置文�g中的数据源配�|�（使用GenericDataSource数据源实玎ͼ��Q�你可以更改相应的设�|�以适合你自��q��pȝ��?br />


                            property="autoCommit"
                 value="false"/>
                            property="description"
                 value="Example Data Source Configuration"/>
                            property="driverClass"
                 value="org.postgresql.Driver"/>
                            property="maxCount"
                 value="4"/>
                            property="minCount"
                 value="2"/>
                            property="password"
                 value="mypassword"/>
                            property="url"
                 value="jdbc:postgresql://localhost/mydatabase"/>
                            property="user"
                 value="myusername"/>


使用BasicDataSource数据源实现的配置�Ҏ��如下�Q?/strong>



                                  property="driverClassName"
                  value="org.postgresql.Driver" />
                                  property="url"
                  value="jdbc:postgresql://localhost/mydatabase" />
                                  property="username"
                  value="me" />
                                  property="password"
                  value="test" />
                                  property="maxActive"
                  value="10" />
                                  property="maxWait"
                  value="5000" />
                                  property="defaultAutoCommit"
                  value="false" />
                                  property="defaultReadOnly"
                  value="false" />
                                  property="validationQuery"
                  value="SELECT COUNT(*) FROM market" />


  注意�Q�你可以在你的应用系�l�中定义不止一个数据源�Q�你可以�Ҏ��需要定义多个数据源�Q��ƈ为它们分别�v一个逻辑名（logical name�Q�。这样做可以�l�你的应用系�l�提供更好的安全性和可测量性（scalability�Q�，你还可以定义一个专用于��试的数据源�?br />
  配置好DataSource以后�Q�你��可以在你的应用�pȝ��中��用这些数据源了。下面这�D�代码演�C�Z��怎样在Action�cȝ��execute�Ҏ��中通过�q�些数据源来生成数据库连接�?
需要３个包�Q�别忘了数据库驱动包�Q?/p>
commons-collections-3.1.jar
commons-dbcp-1.2.1.jar
commons-pool-1.2.jar

public ActionForward execute(
        ActionMapping mapping,
        ActionForm form,
        HttpServletRequest request,
        HttpServletResponse response)
        throws Exception
{
        DataSource dataSource;
        Connection cnn;

        try
        {
                dataSource = getDataSource(request);
                cnn = dataSource.getConnection();
                // 数据�q�接已经建立了，你可以做你想做的事情�?br />        }
        catch (SQLException e)
        {
                getServlet().log("处理数据库连�?, e);
        }
        finally
        {
                // 在finally块里包含�q�些代码
                // 用以保证�q�接最后会被关�?br />                try
                {
                        cnn.close();
                }
                catch (SQLException e)
                {
                        getServlet().log("关闭数据库连�?, e);
                }
        }
}

  注意�Q�如果你使用公共的BasicDataSource�Q�你提供�l�pingQuery属性的查询语句�Q�如果你讄��了话�Q�必��至��要能返回一行记录�?br />
例子�Q�SELECT COUNT(*) FROM VALIDTABLE

你可以把VALIDTABLE替换成你的数据库中包含的��M��有效的表�?br />
数据库连接字�W�串
SQLServer2000:
  driverClassName:com.microsoft.jdbc.sqlserver.SQLServerDriver
  url: jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=databasename
MySql:
   driverClassName:com.mysql.jdbc.Driver
  url: jdbc:mysql://localhost/databasename

�Q�M��用多个数据源�Q?/strong>

如果你需要在模块�Q�Module�Q�中使用多于一个的数据源，你可以在配置文�g�?lt;data-source>元素里包含一个key属性�?br />


                …属性配�|�略, 同上�?br />

                …属性配�|�略, 同上�?br />

你代码里�Q�你可以通过�q�些key获得不同的数据源。代码如下：

�?br />try
{
        dataSourceA = getDataSource(request, "A");
        dataSourceB = getDataSource(request, "B");
�?br />
你可以根据需要�ؓ每一个模块设�|�多个数据源。但同一模块里每个数据源的key属性必��d��一�Q�因为Struts模块�pȝ��是以每一个模块�ؓ单位��理命名�I�间的�?/p>

飞鸟 2006-04-19 14:45 发表评论

LOG4J配置

飞鸟 — Wed, 19 Apr 2006 06:44:00 GMT

常用log4j配置 [转]

常用log4j配置�Q�一般可以采用两�U�方式，.properties�?xml,下面举两个简单的例子�Q?/p>
一、log4j.properties

### 讄��com.unmi域对应的�U�别INFO,DEBUG,WARN,ERROR和输出地A1�Q�A2 ##
log4j.category.com.unmi=ERROR,A1
log4j.category.com.unmi=INFO,A2

### 一般把上面两行写如下方式，�l�一控制日志输出,再用log4j.logger讄��包独立的输出�U�别 ##
log4j.rootLogger=DEBUG,A1
log4j.logger.com.unmi.special = ERROR

### 讄��输出地A1�Q��ؓConsoleAppender(控制�? ##
log4j.appender.A1=org.apache.log4j.ConsoleAppender

### 讄��A1的输出布局格式PatterLayout,(可以灉|��地指定布局模式�Q?#
log4j.appender.A1.layout=org.apache.log4j.PatternLayout

### 配置日志输出的格�?#
log4j.appender.A1.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS} [%c]-[%p] %m%n

### 讄��输出地A2到文�Ӟ��文�g大小到达指定��寸的时候��生一个新的文�Ӟ��##
log4j.appender.A2=org.apache.log4j.RollingFileAppender

### 文�g位置##
log4j.appender.A2.File=E:/study/log4j/zhuwei.html

### 文�g大小##
log4j.appender.A2.MaxFileSize=500KB

log4j.appender.A2.MaxBackupIndex=1

##指定采用html方式输出
log4j.appender.A2.layout=org.apache.log4j.HTMLLayout

二、log4j.xml






























三、配�|�文件加载方法：

对于properties文�g�Q�一般都不用手工��d��载，由Log4j�W�一�ơ初始化时自动就加蝲�?/p>
import org.apache.log4j.Logger;
import org.apache.log4j.PropertyConfigurator;
import org.apache.log4j.xml.DOMConfigurator;

public class Log4jApp {
   public static void main(String[] args) {
       DOMConfigurator.configure("E:/study/log4j/log4j.xml");//加蝲.xml文�g
       //PropertyConfigurator.configure("E:/study/log4j/log4j.properties");//加蝲.properties文�g

       Logger log=Logger.getLogger("com.unmi.test");
       log.info("��试");
   }
}

四、项目��用log4j

在web应用中，可以��配�|�文件的加蝲攑֜�一个单独的servlet中，�q�在web.xml中配�|�该servlet在应用启动时候加载。对于在多�h��目中，可以�l�每一个�h讄��一个输出通道�Q�这样在每个人在构徏Logger�Ӟ��用自��q��域名�U�ͼ�让调试信息输出到自己的log文�g中�?/p>

五、常用输出格�?/p>
# -X�?X信息输出时左寚w��Q?br /># %p:日志信息�U�别
# %d{}:日志信息产生旉��
# %c:日志信息所在地�Q�类名）
# %m:产生的日志具体信�?br /># %n:输出日志信息换行

关于Log4j比较全面的配�|?br />LOG4J的配�|�之��单��它遍及于��来��多的应用中了：Log4J配置文�g实现了输出到控制台、文件、回滚文件、发送日志邮件、输出到数据库日志表、自定义标签�{�全套功能。择其一二��用就够用了，

log4j.rootLogger=DEBUG,CONSOLE,A1,im
log4j.addivity.org.apache=true

# 应用于控制台

log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.Threshold=DEBUG
log4j.appender.CONSOLE.Target=System.out
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n
#log4j.appender.CONSOLE.layout.ConversionPattern=[start]%d{DATE}[DATE]%n%p[PRIORITY]%n%x[NDC]%n%t[THREAD] n%c[CATEGORY]%n%m[MESSAGE]%n%n

#应用于文�?

log4j.appender.FILE=org.apache.log4j.FileAppender
log4j.appender.FILE.File=file.log
log4j.appender.FILE.Append=false
log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.FILE.layout.ConversionPattern=[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n
# Use this layout for LogFactor 5 analysis

# 应用于文件回�?

log4j.appender.ROLLING_FILE=org.apache.log4j.RollingFileAppender
log4j.appender.ROLLING_FILE.Threshold=ERROR
log4j.appender.ROLLING_FILE.File=rolling.log
log4j.appender.ROLLING_FILE.Append=true
log4j.appender.ROLLING_FILE.MaxFileSize=10KB
log4j.appender.ROLLING_FILE.MaxBackupIndex=1
log4j.appender.ROLLING_FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.ROLLING_FILE.layout.ConversionPattern=[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n

#应用于socket
log4j.appender.SOCKET=org.apache.log4j.RollingFileAppender
log4j.appender.SOCKET.RemoteHost=localhost
log4j.appender.SOCKET.Port=5001
log4j.appender.SOCKET.LocationInfo=true
# Set up for Log Facter 5
log4j.appender.SOCKET.layout=org.apache.log4j.PatternLayout
log4j.appender.SOCET.layout.ConversionPattern=[start]%d{DATE}[DATE]%n%p[PRIORITY]%n%x[NDC]%n%t[THREAD]%n%c[CATEGORY]%n%m[MESSAGE]%n%n

# Log Factor 5 Appender
log4j.appender.LF5_APPENDER=org.apache.log4j.lf5.LF5Appender
log4j.appender.LF5_APPENDER.MaxNumberOfRecords=2000

# 发送日志给邮�g

log4j.appender.MAIL=org.apache.log4j.net.SMTPAppender
log4j.appender.MAIL.Threshold=FATAL
log4j.appender.MAIL.BufferSize=10
log4j.appender.MAIL.From=xxx@www.xxx.com
log4j.appender.MAIL.SMTPHost=www.wusetu.com
log4j.appender.MAIL.Subject=Log4J Message
log4j.appender.MAIL.To=xxx@www.xxx.com
log4j.appender.MAIL.layout=org.apache.log4j.PatternLayout
log4j.appender.MAIL.layout.ConversionPattern=[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n

# 用于数据�?
log4j.appender.DATABASE=org.apache.log4j.jdbc.JDBCAppender
log4j.appender.DATABASE.URL=jdbc:mysql://localhost:3306/test
log4j.appender.DATABASE.driver=com.mysql.jdbc.Driver
log4j.appender.DATABASE.user=root
log4j.appender.DATABASE.password=
log4j.appender.DATABASE.sql=INSERT INTO LOG4J (Message) VALUES ('[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n')
log4j.appender.DATABASE.layout=org.apache.log4j.PatternLayout
log4j.appender.DATABASE.layout.ConversionPattern=[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n

log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender
log4j.appender.A1.File=SampleMessages.log4j
log4j.appender.A1.DatePattern=yyyyMMdd-HH'.log4j'
log4j.appender.A1.layout=org.apache.log4j.xml.XMLLayout

输出�?000NT日志
把Log4j压羃包里的NTEventLogAppender.dll拷到WINNT\SYSTEM32目录�?/p>
log4j.logger.NTlog=FATAL, A8
# APPENDER A8
log4j.appender.A8=org.apache.log4j.nt.NTEventLogAppender
log4j.appender.A8.Source=JavaTest
log4j.appender.A8.layout=org.apache.log4j.PatternLayout
log4j.appender.A8.layout.ConversionPattern=%-4r %-5p [%t] %37c %3x - %m%n

#自定义Appender

log4j.appender.im = net.cybercorlin.util.logger.appender.IMAppender

log4j.appender.im.host = mail.cybercorlin.net
log4j.appender.im.username = username
log4j.appender.im.password = password
log4j.appender.im.recipient = xxx@xxx.net

log4j.appender.im.layout=org.apache.log4j.PatternLayout
log4j.appender.im.layout.ConversionPattern =[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n

飞鸟 2006-04-19 14:44 发表评论

Parameter	Description
username	The connection username to be passed to our JDBC driver to establish a connection.
password	The connection password to be passed to our JDBC driver to establish a connection.
url	The connection URL to be passed to our JDBC driver to establish a connection.
driverClassName	The fully qualified Java class name of the JDBC driver to be used.
connectionProperties	The connection properties that will be sent to our JDBC driver when establishing new connections. Format of the string must be [propertyName=property;]* NOTE - The "user" and "password" properties will be passed explicitly, so they do not need to be included here.

Parameter	Default	Description
defaultAutoCommit	true	The default auto-commit state of connections created by this pool.
defaultReadOnly	driver default	The default read-only state of connections created by this pool. If not set then the setReadOnly method will not be called. (Some drivers don't support read only mode, ex: Informix)
defaultTransactionIsolation	driver default	The default TransactionIsolation state of connections created by this pool. One of the following: (see javadoc) NONE READ_COMMITTED READ_UNCOMMITTED REPEATABLE_READ SERIALIZABLE
defaultCatalog		The default catalog of connections created by this pool.

Parameter	Default	Description
initialSize	0	The initial number of connections that are created when the pool is started. Since: 1.2
maxActive	8	The maximum number of active connections that can be allocated from this pool at the same time, or zero for no limit.
maxIdle	8	The maximum number of active connections that can remain idle in the pool, without extra ones being released, or zero for no limit.
minIdle	0	The minimum number of active connections that can remain idle in the pool, without extra ones being created, or zero to create none.
maxWait	indefinitely	The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception, or -1 to wait indefinitely.

Parameter	Default	Description
validationQuery		The SQL query that will be used to validate connections from this pool before returning them to the caller. If specified, this query MUST be an SQL SELECT statement that returns at least one row.
testOnBorrow	true	The indication of whether objects will be validated before being borrowed from the pool. If the object fails to validate, it will be dropped from the pool, and we will attempt to borrow another. NOTE - for a `true` value to have any effect, the `validationQuery` parameter must be set to a non-null string.
testOnReturn	false	The indication of whether objects will be validated before being returned to the pool. NOTE - for a `true` value to have any effect, the `validationQuery` parameter must be set to a non-null string.
testWhileIdle	false	The indication of whether objects will be validated by the idle object evictor (if any). If an object fails to validate, it will be dropped from the pool. NOTE - for a `true` value to have any effect, the `validationQuery` parameter must be set to a non-null string.
timeBetweenEvictionRunsMillis	-1	The number of milliseconds to sleep between runs of the idle object evictor thread. When non-positive, no idle object evictor thread will be run.
numTestsPerEvictionRun	3	The number of objects to examine during each run of the idle object evictor thread (if any).
minEvictableIdleTimeMillis	1000 * 60 * 30	The minimum amount of time an object may sit idle in the pool before it is eligable for eviction by the idle object evictor (if any).

Parameter	Default	Description
poolPreparedStatements	false	Enable prepared statement pooling for this pool.
maxOpenPreparedStatements	unlimited	The maximum number of open statements that can be allocated from the statement pool at the same time, or zero for no limit.

Parameter	Default	Description
removeAbandoned	false	Flag to remove abandoned connections if they exceed the removeAbandonedTimout. If set to true a connection is considered abandoned and eligible for removal if it has been idle longer than the removeAbandonedTimeout. Setting this to true can recover db connections from poorly written applications which fail to close a connection.
removeAbandonedTimeout	300	Timeout in seconds before an abandoned connection can be removed.
logAbandoned	false	Flag to log stack traces for application code which abandoned a Statement or Connection. Logging of abandoned Statements and Connections adds overhead for every Connection open or new Statement because a stack trace has to be generated.