77777午夜亚洲,亚洲欧洲日产国产综合网,午夜影视日本亚洲欧洲精品一区

WebWork 2.2 学习�W�记(�?

oxl — Wed, 03 May 2006 17:02:00 GMT

逐个讲解WebWork中的一些配�|�文件的基本用法:
----------------------------------------------------------------------------
web.xml

<filter>
    <filter-name>webworkfilter-name>
    <filter-class>com.opensymphony.webwork.dispatcher.FilterDispatcherfilter-class>
filter>
<filter-mapping>
    <filter-name>webworkfilter-name>
    <url-pattern>/*url-pattern>
filter-mapping>
<listener>
    <listener-class>org.springframework.web.context.ContextLoaderListenerlistener-class>
listener>

�q�里使用了一个Filter来对所有的url�q�行�q��o,而只有在webwork.properties中的讑֮�的webwork.action.extension作�ؓ扩展名才会被解悉��Z��个action.
而定义了一个监听器主要是用Spring的监听Web容器里的变化,�q�里主要是用于Spring作�ؓWebWork的IoC.如果惌��Spring有多个context配置文�g,那就可加入下面的代码:

<context-param>
<param-name>contextConfigLocationparam-name>
<param-value>/WEB-INF/applicationContext-*.xml,classpath*:applicationContext-*.xmlparam-value>
context-param>

*param-value是用逗号隔开的配�|�文件列�?��C��是用相对于Web应用的�\�?

�q�里如果惛_��义一个WebWork tag,那么��可加入以下的代�?

<taglib>
<taglib-uri>webworktaglib-uri>
<taglib-location>/WEB-INF/lib/webworkxx.jartaglib-location>
taglib>

�q�样,在视图jsp文�g中引用WebWork tag�?只须要把uri="webwork"��p��?而不用写成这样uri="/webwork".

--------------------------------------------------------------------------------
在说xwork.xml之前,我们先了解webwork-default.xml文�g,�q�个文�g是由webwork.jar文�g里有�?存放在classpath�?所以我们不用创��个文�?因�ؓ每次�q�行webwork应用�?webwork都会自动去classpath查找�q�个文�g.�q�个文�g预先讄��好了一些默认的参数,比如result type, interceptors�{?可以说是我们xwork.xml中的默认�?同时也�ؓ我们的xwork.xml提供好了很多工具,比如params拦截器就是最典型的一�?

在编写xwork.xml�?我们一般都要导入这个webwork-default.xml文�g,代码如下:

具体的xwork.xml配置,�׃��后的学习中给�?..(�?...我也�q�不清楚,没有实践�q�呢..)
xwork.xml文�g必须攑֜�/WEB-INF/classes/�?

--------------------------------------------------------------------------------

下面说一下webwork.properties文�g,�q�个文�g是配�|�webwork行�ؓ�Ҏ��的文�g,他可以改变webwork的扩展名,以及�~�码�{?�q�个文�g的详�l�说明可以参考官方的文档:

### Webwork default properties
###(can be overridden by a webwork.properties file in the root of the classpath)
###

### Specifies the Configuration used to configure webwork
### one could extend com.opensymphony.webwork.config.Configuration
### to build one's customize way of getting the configurations parameters into webwork
# webwork.configuration=com.opensymphony.webwork.config.DefaultConfiguration

### This can be used to set your default locale and encoding scheme
# webwork.locale=en_US
webwork.i18n.encoding=UTF-8

### if specified, the default object factory can be overridden here
### Note: short-hand notation is supported in some cases, such as "spring"
###       Alternatively, you can provide a com.opensymphony.xwork.ObjectFactory subclass name here
# webwork.objectFactory = spring

### specifies the autoWiring logic when using the SpringObjectFactory.
### valid values are: name, type, auto, and constructor (name is the default)
webwork.objectFactory.spring.autoWire = name

### Parser to handle HTTP POST requests, encoded using the MIME-type multipart/form-data
# webwork.multipart.parser=cos
# webwork.multipart.parser=pell
webwork.multipart.parser=jakarta
# uses javax.servlet.context.tempdir by default
webwork.multipart.saveDir=
webwork.multipart.maxSize=2097152

### Load custom property files (does not override webwork.properties!)
# webwork.custom.properties=application,com/webwork/extension/custom

### How request URLs are mapped to and from actions
webwork.mapper.class=com.opensymphony.webwork.dispatcher.mapper.DefaultActionMapper

### Used by the DefaultActionMapper
webwork.action.extension=action

### use alternative syntax that requires %{} in most places
### to evaluate expressions for String attributes for tags
webwork.tag.altSyntax=true

### when set to true, WebWork will act much more friendly for developers. This
### includes:
### - webwork.i18n.reload = true
### - webwork.configuration.xml.reload = true
### - raising various debug or ignorable problems to errors
###   For example: normally a request to foo.action?someUnknownField=true should
###                be ignored (given that any value can come from the web and it
###                should not be trusted). However, during development, it may be
###                useful to know when these errors are happening and be told of
###                them right away.
webwork.devMode = false

### when set to true, resource bundles will be reloaded on _every_ request.
### this is good during development, but should never be used in production
webwork.i18n.reload=false

### Standard UI theme
### Change this to reflect which path should be used for JSP control tag templates by default
webwork.ui.theme=xhtml
webwork.ui.templateDir=template
#sets the default template type. Either ftl, vm, or jsp
webwork.ui.templateSuffix=ftl

### Configuration reloading
### This will cause the configuration to reload xwork.xml when it is changed
webwork.configuration.xml.reload=false

### Location of velocity.properties file.  defaults to velocity.properties
# webwork.velocity.configfile = velocity.properties

### Comma separated list of VelocityContext classnames to chain to the WebWorkVelocityContext
# webwork.velocity.contexts =

### used to build URLs, such as the UrlTag
webwork.url.http.port = 80
webwork.url.https.port = 443

### Load custom default resource bundles
# webwork.custom.i18n.resources=testmessages,testmessages2

### workaround for some app servers that don't handle HttpServletRequest.getParameterMap()
### often used for WebLogic, Orion, and OC4J
webwork.dispatcher.parametersWorkaround = false

### configure the Freemarker Manager class to be used
### Allows user to plug-in customised Freemarker Manager if necessary
### MUST extends off com.opensymphony.webwork.views.freemarker.FreemarkerManager
#webwork.freemarker.manager.classname=com.opensymphony.webwork.views.freemarker.FreemarkerManager

### See the WebWorkBeanWrapper javadocs for more information
webwork.freemarker.wrapper.altMap=true

�?大至上已�l�清楚了�q�些文�g的大至用�?下一�?弄清xwork的配�|?

oxl 2006-05-04 01:02 发表评论

WebWork 2.2 学习�W�记(一)

oxl — Mon, 01 May 2006 06:33:00 GMT

今天开始学习WebWork�Q�呵……结合《WebWork教程�Q?.90版》和Webwork官方的教�E�来学习�?br />
WebWork2.2和WebWork2.1在配�|�上有一些区别，现在把WebWork2.2的一些配�|�放�q�来�?br />
web.xml

xml version="1.0" encoding="UTF-8"?>
<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
    http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">

    <filter>
        <filter-name>webworkfilter-name>
        <filter-class>com.opensymphony.webwork.dispatcher.FilterDispatcherfilter-class>
    filter>

    <filter-mapping>
        <filter-name>webworkfilter-name>
        <url-pattern>/*url-pattern>
    filter-mapping>

    <listener>
        <listener-class>org.springframework.web.context.ContextLoaderListenerlistener-class>
    listener>
web-app>

xwork.xml

xml version="1.0" encoding="UTF-8"?>
DOCTYPE xwork PUBLIC "-//OpenSymphony Group//XWork 1.1.1//EN"
"http://www.opensymphony.com/xwork/xwork-1.1.1.dtd">

<xwork>

    <include file="webwork-default.xml" />


   <package name="default" extends="webwork-default">

     <default-interceptor-ref name="completeStack"/>

      <action name="helloWorld"
         class="org.javadream.webwork.ch01.HelloWorld">
         <result name="success">hello.jspresult>
      action>
   package>

xwork>

webwork.properties

webwork.locale=zh_CN
webwork.i18n.encoding=GB2312

webwork.objectFactory=spring

�q�里中文有问题，必须要在webwork.properties中进入设�|?webwork.objectFactory=spring是用spring作�ؓ默认的IoC容器�?br />

�~�写一个Action:

package org.javadream.webwork.ch01;

import com.opensymphony.xwork.Action;

import java.text.DateFormat;
import java.util.*;

public class HelloWorld implements Action {
private String message;

public String execute() {
   message = "Hello, WebWorld!,你好,Web世界\n";
   message += "The time is:\n";
   message += DateFormat.getDateInstance().format(new Date());;

   //message = message.replaceAll("\n", "
");

   return SUCCESS;
}

public String getMessage() {
   return message;
}

}

�~�写一个视图jsp文�g:

<%@ page language="java" contentType="text/html; charset=gb2312" pageEncoding="gb2312"%>
<%@ taglib prefix="ww" uri="/webwork"%>
<html>
    <head>
        <title>Hello Pagetitle>
    head>
    <body>
        The message generated by my first action is:
        <br>
        <font color="red"><ww:property value="message" />font>
    body>
html>

�q�里要注意，<%@ taglib prefix="ww" uri="/webwork"%>必须要用uri="/webwork"�Q�因��让他在webwork.jar中查找webwork.tld�Q�因为我们在web.xml�q�没有定义这�?webwork"�q�个uri�?br />

oxl 2006-05-01 14:33 发表评论

关于文�g上传的问�?利用适配器模式统一调用接口.

oxl — Thu, 27 Apr 2006 14:41:00 GMT

关于文�g上传的问�?
Java Servlet没有从根本上支持�|�络文�g上传,�q�是一个极不好的也极不爽的事情.
从而就延生了commonsUpload和cos�q�些东东�c�d��,�?....�q�算�?也好�?不过没仔�l�去研究他们的实��C��?用�v来��L��心大心小�?

也正因�ؓ�q�样多的�W�三方类�?大家的接口都不同,从而也��出��C��让Service层无所适从的感�?因�ؓ不论是从Struts�q�是从WebWork或者从最��单的cos�q�些�c�d��得到的接口都是一�U�具体实�?没有�l�一的接�?如果Service层与某一�U�具体实现相兌��,则必然与�q�种具体实现的框架或者类库硬�~�码�l�定,以后��׃��好用其它�c�d��?�q�是不好的设�?真的,一点灵�z�d��都没�?

能不能这样呢?在Service定义一个UploadFile接口,所有Service层接受的只是UploadFile的实现类的实�?从而统一了所有Service的调�?而且也��Service可以在各�U�MVC或者第三方�c�d��中迁�U?

�q�里用到了一个设计模�?适配器模�?

代码如下:

package org.springstudy.ch03;

import java.io.InputStream;
import java.io.File;

public interface UploadFile {
     public byte [] getBytes();
     public String getContentType();
     public InputStream getInputStream();
     public String getName();
     public String getOriginalFilename();
     public long getSize();
     public boolean isEmpty();
     public void transferTo(File dest);
}

比如�q�里有一个具体实�?

package org.springstudy.ch03.uploadimpl;

import java.io.InputStream;
import java.io.File;

import org.springframework.web.multipart.MultipartFile;
import org.springstudy.ch03.UploadFile;

public classUploadFileSpringImpl implements UploadFile {
     private MultipartFile multipartFile;

     public UploadFileSpringImpl(MultipartFile multipartFile) {
         this .multipartFile = multipartFile;
    }

     public byte [] getBytes() {
         return this .multipartFile.getBytes();
    }

     public String getContentType() {
         return this .multipartFile.getContentType();
    }

     public InputStream getInputStream() {
         return this .multipartFile.getInputStream();
    }

     public String getName() {
         return this .multipartFile.getName();
    }

     public String getOriginalFilename() {
         return this .multipartFile.getOriginalFilename();
    }

     public long getSize() {
         return this .multipartFile.getSize();
    }

     public boolean isEmpty() {
         return this .multipartFile.isEmpty();
    }

     public void transferTo(File dest) {
         this .multipartFile.transferTo(dest);
    }
}

你也可以写commonsupload或者cos的实�?Service接受的参数是UploadFile接口�?所以你必须实现UploadFile接口才能使用Service层的功能.

(后话:看来学习设计模式�q�是很有用处�?

oxl 2006-04-27 22:41 发表评论

�W�一个筹划要做的Java��目.<�|�上电子分类信息>�pȝ��.

oxl — Wed, 12 Apr 2006 15:48:00 GMT

在银沙里现在��是负责�q�方面的开�?�l�过�q�段旉��的对�pȝ��的了�?我想�q�是一个很有趣的项�?于是��想到写一个对应的Java的Web�E�序.

当也要抛弃那些原来php�pȝ��里不好的设计和方�?

新的Java实现会用��C��么技术呢?

Spring + Hibernate + WW + Ajax

开发时�?1�q?�?006�q?�?0号开�?

注意的地�?
不要急着写代�?要先做好需求分析和设计
注意扩展性和对编�E�模式的更好应用.

打算开源该��目.

oxl 2006-04-12 23:48 发表评论

oxl — Sun, 02 Apr 2006 08:23:00 GMT

��L��没法子弄清楚业务逻辑层和控制层的关系�Q�控制层仅仅只是控制��吗�Q�那么业务逻辑��没有控制流了吗�Q?br />
我现在分析得出：
1、控制层调用业务层得到要昄��的数据，然后把数据返回给视图层�?br />2、业务层则是�׃��务接口和业务操作�l�成。比如：

/**
* A Service
*/

public class UserService {
    public UserView login(String name, String password) {
        //.
        //.
        //.
        //.
        //.
    }
}

业务操作则是业务接口调用相关的数据持久层和一些其它相��x��作组成�?br />
3、实体：实体��是一个对象，对象拥有数据�Q�可以把对象攑ֈ�Dao�q�行保存�Q�也可以通过Dao得到对象�Q�然后对象对自己的数据来�q�行操作�Q�比如说改变静态页面，保存囄��或删除图片等。其实实体就是两�U�角�Ԍ��一个是持久对象PO�Q�一个是实体对象EO

oxl 2006-04-02 16:23 发表评论