| |
|
| 基 本 信 息 |  |
| 姓 名： | 李大和 | 性  别： | 男 |
| 出生日期： | 1983年02月28日 | 居 住 地： | 北京市 |
| 工作年限： | 三年以上 | 户 口： | 北京 |
| 目前年薪： | 4-5万人民币 | ||
| 地 址： | 北京市海淀区清河小营 | ||
| 邮 编： | 100031 | ||
| 电子邮件： | hellboys@tom.com | ||
| 家庭电话： | 086- 010- 68826056 | ||
| 移动电话： | 086- 13520876658 | ||
| 个人主页： | http://www.blogjava.net/hellboys | ||
| 求 职 意 向 | |
| | |
| 工作性质： | 全职 |
| 期望工资： | 面议 |
| 工 作 经 验 | | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 项 目 经 验 | | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 教 育 经 历 | | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 证 书 | | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 语 言 能 力 | | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IT 技 能 | | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 附 加 信 息 | | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
doc.simle.jsp
<%@ page contentType="text/html;charset=utf-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title> 除法运算器</title>
<script language="JavaScript" src="js/prototype.js"></script>
<script language="JavaScript" src="js/buffalo.js"></script>
<script language="JavaScript" src="js/template.js"></script>
<script language="javascript">
var endPoint="<%=request.getContextPath()%>/BUFFALO";
var buffalo = new Buffalo(endPoint);
function cmdDivide() {
var double1 = parseFloat(Buffalo.getElementById("double1").value);
var double2 = parseFloat(Buffalo.getElementById("double2").value);
var d3Handle = Buffalo.getElementById("double3");
buffalo.remoteCall("simpleService.divide",[double1,double2], function(reply) {
d3Handle.value = reply.getResult();
})
}
</script>
<input name="double1" type="text" class="input_text" id="double1" size="12">
/
<input name="double2" type="text" class="input_text" id="double2" size="12">
<input type="button" name="Submit" value=" = " onclick="cmdDivide()">
<input name="double3" type="text" class="input_text" id="double3">
</html>
web.xml
<servlet>
<servlet-name>service</servlet-name>
<servlet-class>net.buffalo.server.BuffaloServiceServlet</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>true</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>service</servlet-name>
<url-pattern>/BUFFALO</url-pattern>
</servlet-mapping>
SimpleService.java
package net.buffalo.demo.simple;
import ...;
public class SimpleService {
public double divide(double a, double b) {
System.out.println("Calling Divide...,a="+a+", b="+b);
try {
Thread.sleep(1000);
} catch (Exception e) {
e.printStackTrace();
}
return a/b;
}
}
buffalo.remoteCall("simpleService.divide",[double1,double2], function(reply) {
d3Handle.value = reply.getResult();
})
buffalo对象访问 SimpleService.java 中divide方法。 返回结果(reply.getResult();)赋值给d3Handle.
如此简单清晰的方法调用，实在是简洁。慢慢的进入buffalo,就可能清楚的明白它的原来。没什么好说的，再清楚不过的代码了。if try it first yourself again when you konw it very well.
看来 论Michael的 "Don’t Lose Your Passion"
http://michael.nona.name/archives/119
总之有些末名的冲动与思索.每次总是想说什么,可是确不知道从何说起.不知道Michael所说是对是错.不过有些地方我确实很同意.
不好说什么,有些感触,先自省吧.
呵呵.
import java.sql.CallableStatement;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Types;
import java.util.List;
import org.springframework.jdbc.core.BatchPreparedStatementSetter;
import org.springframework.jdbc.core.CallableStatementCallback;
import org.springframework.jdbc.core.JdbcTemplate;
import org.springframework.jdbc.core.RowCallbackHandler;
import org.springframework.jdbc.core.RowMapper;
import org.springframework.jdbc.core.RowMapperResultReader;
public class SpringJDBCDAO {
private class PersonRowMapper implements RowMapper {
public Object mapRow(ResultSet rs, int index) throws SQLException {
Person person = new Person();
person.setId(new Integer(rs.getInt("id")));
person.setFirstName(rs.getString("first_name"));
person.setLastName(rs.getString("last_name"));
return person;
}
}
private JdbcTemplate jdbcTemplate;
public void processStoredProcedure() {
CallableStatementCallback cb = new CallableStatementCallback() {
public Object doInCallableStatement(CallableStatement cs)
throws SQLException {
cs.execute();
return null;
}
};
jdbcTemplate.execute("{ ARCHIVE_STUDENTS }", cb);
}
public List getAllPersons() {
String sql = "select id, first_name, last_name from person";
return jdbcTemplate.query(sql, new RowMapperResultReader(
new PersonRowMapper()));
}
public String getLastNameForId(Integer id) {
String sql = "select last_name from person where id = ?";
return (String) jdbcTemplate.queryForObject(sql, new Object[] { id },
String.class);
}
public int getNumberOfPersons() {
return jdbcTemplate.queryForInt("select count(*) from person");
}
public Person getPerson1(final Integer id) {
String sql = "select id, first_name, last_name from person where id = ?";
final Person person = new Person();
final Object[] params = new Object[] { id };
jdbcTemplate.query(sql, params, new RowCallbackHandler() {
public void processRow(ResultSet rs) throws SQLException {
person.setId(new Integer(rs.getInt("id")));
person.setFirstName(rs.getString("first_name"));
person.setFirstName(rs.getString("last_name"));
}
});
return person;
}
public Person getPerson2(final Integer id) {
String sql = "select id, first_name, last_name from person where id = ?";
final Person person = new Person();
final Object[] params = new Object[] { id };
List list = jdbcTemplate.query(sql, params, new RowMapperResultReader(
new PersonRowMapper()));
return (Person) list.get(0);
}
public int insertPerson(Person person) {
String sql = "insert into person (id, firstName, lastName) values (?, ?, ?)";
Object[] params = new Object[] { person.getId(), person.getFirstName(),
person.getFirstName() };
int[] types = new int[] { Types.INTEGER, Types.VARCHAR, Types.VARCHAR };
JdbcTemplate jdbcTemplate = null;
return jdbcTemplate.update(sql, params, types);
}
public int[] updatePersons(final List persons) {
String sql = "insert into person (id, firstName, lastName) values (?, ?, ?)";
BatchPreparedStatementSetter setter = null;
setter = new BatchPreparedStatementSetter() {
public int getBatchSize() {
return persons.size();
}
public void setValues(PreparedStatement ps, int index)
throws SQLException {
Person person = (Person) persons.get(index);
ps.setInt(0, person.getId().intValue());
ps.setString(1, person.getFirstName());
ps.setString(2, person.getLastName());
}
};
return jdbcTemplate.batchUpdate(sql, setter);
}
}
============
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Types;
import javax.sql.DataSource;
import org.springframework.jdbc.core.SqlParameter;
import org.springframework.jdbc.object.MappingSqlQuery;
import org.springframework.jdbc.object.SqlUpdate;
public class SpringJDBCDAOWithObject {
class InsertPerson extends SqlUpdate {
public InsertPerson(DataSource ds) {
setDataSource(ds);
setSql("insert into person (id, firstName, lastName) values (?, ?, ?)");
declareParameter(new SqlParameter(Types.NUMERIC));
declareParameter(new SqlParameter(Types.VARCHAR));
declareParameter(new SqlParameter(Types.VARCHAR));
compile();
}
public int insert(Person person) {
Object[] params = new Object[] { person.getId(),
person.getFirstName(), person.getLastName() };
return update(params);
}
}
private class PersonByIdQuery extends MappingSqlQuery {
public PersonByIdQuery(DataSource ds) {
super(ds, "select id, first_name, last_name from person "
+ "where id = ?");
declareParameter(new SqlParameter("id", Types.INTEGER));
compile();
}
public Object mapRow(ResultSet rs, int rowNumber) throws SQLException {
Person person = new Person();
person.setId((Integer) rs.getObject("id"));
person.setFirstName(rs.getString("first_name"));
person.setLastName(rs.getString("last_name"));
return person;
}
}
private InsertPerson insertPerson;
private PersonByIdQuery personByIdQuery;
public Person getPerson(Integer id) {
Object[] params = new Object[] { id };
return (Person) personByIdQuery.execute(params).get(0);
}
public int insertPerson(Person person) {
return insertPerson.insert(person);
}
}
from
数字 32–126 分配给了能在键盘上找到的字符，当您查看或打印文档时就会出现。数字 127 代表 DELETE 命令。
十进制 字符 十进制 字符 32 space 80 P 33 ! 81 Q 34 " 82 R 35 # 83 S 36 $ 84 T 37 % 85 U 38 & 86 V 39 ' 87 w 40 ( 88 X 41 ) 89 Y 42 * 90 Z 43 + 91 [ 44 , 92 \ 45 - 93 ] 46 . 94 ^ 47 / 95 _ 48 0 96 ` 49 1 97 a 50 2 98 b 51 3 99 c 52 4 100 d 53 5 101 e 54 6 102 f 55 7 103 g 56 8 104 h 57 9 105 i 58 : 106 j 59 ; 107 k 60 < 108 l 61 = 109 m 62 > 110 n 63 ? 111 o 64 @ 112 p 65 A 113 q 66 B 114 r 67 C 115 s 68 D 116 t 69 E 117 u 70 F 118 v 71 G 119 w 72 H 120 x 73 I 121 y 74 J 122 z 75 K 123 { 76 L 124 | 77 M 125 } 78 N 126 ~ 79 O 127 DEL
扩展的 ASCII 字符满足了对更多字符的需求。扩展的 ASCII 包含 ASCII 中已有的 128 个字符（数字 0–32 显示在下图中），又增加了 128 个字符，总共是 256 个。即使有了这些更多的字符，许多语言还是包含无法压缩到 256 个字符中的符号。因此，出现了一些 ASCII 的变体来囊括地区性字符和符号。
例如，许多软件程序把 ASCII 表（又称作 ISO 8859-1）用于北美、西欧、澳大利亚和非洲的语言。
| 十进制 | 字符 | 十进制 | 字符 | |
|---|---|---|---|---|
| 128 | Ç | 192 | └ | |
| 129 | ü | 193 | ┴ | |
| 130 | é | 194 | ┬ | |
| 131 | â | 195 | ├ | |
| 132 | ä | 196 | ─ | |
| 133 | à | 197 | ┼ | |
| 134 | å | 198 | ╞ | |
| 135 | ç | 199 | ╟ | |
| 136 | ê | 200 | ╚ | |
| 137 | ë | 201 | ╔ | |
| 138 | è | 202 | ╩ | |
| 139 | ï | 203 | ╦ | |
| 140 | î | 204 | ╠ | |
| 141 | ì | 205 | ═ | |
| 142 | Ä | 206 | ╬ | |
| 143 | Å | 207 | ╧ | |
| 144 | É | 208 | ╨ | |
| 145 | æ | 209 | ╤ | |
| 146 | Æ | 210 | ╥ | |
| 147 | ô | 211 | ╙ | |
| 148 | ö | 212 | Ô | |
| 149 | ò | 213 | ╒ | |
| 150 | û | 214 | ╓ | |
| 151 | ù | 215 | ╫ | |
| 152 | ÿ | 216 | ╪ | |
| 153 | Ö | 217 | ┘ | |
| 154 | Ü | 218 | ┌ | |
| 155 | ¢ | 219 | █ | |
| 156 | £ | 220 | ▄ | |
| 157 | ¥ | 221 | ▌ | |
| 158 | ₧ | 222 | ▐ | |
| 159 | ƒ | 223 | ▀ | |
| 160 | á | 224 | α | |
| 161 | í | 225 | ß | |
| 162 | ó | 226 | Γ | |
| 163 | ú | 227 | π | |
| 164 | ñ | 228 | Σ | |
| 165 | Ñ | 229 | σ | |
| 166 | ª | 230 | µ | |
| 167 | º | 231 | τ | |
| 168 | ¿ | 232 | Φ | |
| 169 | ⌐ | 233 | Θ | |
| 170 | ¬ | 234 | Ω | |
| 171 | ½ | 235 | δ | |
| 172 | ¼ | 236 | ∞ | |
| 173 | ¡ | 237 | φ | |
| 174 | « | 238 | ε | |
| 175 | » | 239 | ∩ | |
| 176 | ░ | 240 | ≡ | |
| 177 | ▒ | 241 | ± | |
| 178 | ▓ | 242 | ≥ | |
| 179 | │ | 243 | ≤ | |
| 180 | ┤ | 244 | ⌠ | |
| 181 | ╡ | 245 | ⌡ | |
| 182 | ╢ | 246 | ÷ | |
| 183 | ╖ | 247 | ≈ | |
| 184 | ╕ | 248 | ≈ | |
| 185 | ╣ | 249 | ∙ | |
| 186 | ║ | 250 | · | |
| 187 | ╗ | 251 | √ | |
| 188 | ╝ | 252 | ⁿ | |
| 189 | ╜ | 253 | ² | |
| 190 | ╛ | 254 | ■ | |
| 191 | ┐ | 255 | |
ASCII 表上的数字 0–31 分配给了控制字符，用于控制像打印机等一些外围设备。例如，12 代表换页/新页功能。此命令指示打印机跳到下一页的开头。
| 十进制 | 字符 | 十进制 | 字符 | |
|---|---|---|---|---|
| 0 | 空 | 16 | 数据链路转意 | |
| 1 | 头标开始 | 17 | 设备控制 1 | |
| 2 | 正文开始 | 18 | 设备控制 2 | |
| 3 | 正文结束 | 19 | 设备控制 3 | |
| 4 | 传输结束 | 20 | 设备控制 4 | |
| 5 | 查询 | 21 | 反确认 | |
| 6 | 确认 | 22 | 同步空闲 | |
| 7 | 震铃 | 23 | 传输块结束 | |
| 8 | backspace | 24 | 取消 | |
| 9 | 水平制表符 | 25 | 媒体结束 | |
| 10 | 换行/新行 | 26 | 替换 | |
| 11 | 竖直制表符 | 27 | 转意 | |
| 12 | 换页/新页 | 28 | 文件分隔符 | |
| 13 | 回车 | 29 | 组分隔符 | |
| 14 | 移出 | 30 | 记录分隔符 | |
| 15 | 移入 | 31 | 单元分隔符 |
另一个更新的字符表称为 Unicode （Unicode：Unicode Consortium 开发的一种字符编码标准。该标准采用多（于一）个字节代表每一字符，实现了使用单个字符集代表世界上几乎所有书面语言。）。 因为 Unicode 表大得多，它可以表示 65,536 个字符，而 ASCII 表只能表示 128 个字符，扩展的 ASCII 表也只能表示 256 个字符。这一更大的容量使不同语言的大多数字符都能包含在同一个字符集中。
]]>转自：Potain 的BLOG
另外，你不愿意你的DAO测试代码每次都打开关系Session，因此，我们一般会采用OpenSessionInView模式。
protected void doFilterInternal(HttpServletRequest request, HttpServletResponse response, FilterChain filterChain) throws ServletException, IOException { SessionFactory sessionFactory = lookupSessionFactory(); logger.debug("Opening Hibernate Session in OpenSessionInViewFilter"); Session session = getSession(sessionFactory); TransactionSynchronizationManager.bindResource(sessionFactory, new SessionHolder(session)); try { filterChain.doFilter(request, response); } finally { TransactionSynchronizationManager.unbindResource(sessionFactory); logger.debug("Closing Hibernate Session in OpenSessionInViewFilter"); closeSession(session, sessionFactory); } }
为什么绑定以后，就可以防止每次不会新开一个Session呢？看看HibernateDaoSupport的情况：
public final void setSessionFactory(SessionFactory sessionFactory) { this.hibernateTemplate = new HibernateTemplate(sessionFactory); } protected final HibernateTemplate getHibernateTemplate() { return hibernateTemplate; }
我们的DAO将使用这个template进行操作：
public abstract class BaseHibernateObjectDao extends HibernateDaoSupport implements BaseObjectDao { protected BaseEntityObject getByClassId(final long id) { BaseEntityObject obj = (BaseEntityObject) getHibernateTemplate() .execute(new HibernateCallback() {
public Object doInHibernate(Session session) throws HibernateException { return session.get(getPersistentClass(), new Long(id)); }
}); return obj; }
public void save(BaseEntityObject entity) { getHibernateTemplate().saveOrUpdate(entity); }
public void remove(BaseEntityObject entity) { try {
getHibernateTemplate().delete(entity); } catch (Exception e) { throw new FlexEnterpriseDataAccessException(e); } }
public void refresh(final BaseEntityObject entity) { getHibernateTemplate().execute(new HibernateCallback() {
public Object doInHibernate(Session session) throws HibernateException { session.refresh(entity); return null; }
}); }
public void replicate(final Object entity) { getHibernateTemplate().execute(new HibernateCallback() {
public Object doInHibernate(Session session) throws HibernateException { session.replicate(entity, ReplicationMode.OVERWRITE); return null; }
}); }
public Object execute(HibernateCallback action) throws DataAccessException { Session session = (!this.allowCreate ? SessionFactoryUtils.getSession(getSessionFactory(), false) : SessionFactoryUtils.getSession(getSessionFactory(), getEntityInterceptor(), getJdbcExceptionTranslator())); boolean existingTransaction = TransactionSynchronizationManager.hasResource(getSessionFactory()); if (!existingTransaction && getFlushMode() == FLUSH_NEVER) { session.setFlushMode(FlushMode.NEVER); } try { Object result = action.doInHibernate(session); flushIfNecessary(session, existingTransaction); return result; } catch (HibernateException ex) { throw convertHibernateAccessException(ex); } catch (SQLException ex) { throw convertJdbcAccessException(ex); } catch (RuntimeException ex) { // callback code threw application exception throw ex; } finally { SessionFactoryUtils.closeSessionIfNecessary( session, getSessionFactory()); } }
public static void closeSessionIfNecessary(Session session, SessionFactory sessionFactory) throws CleanupFailureDataAccessException { if (session == null || TransactionSynchronizationManager.hasResource(sessionFactory)) { return; } logger.debug("Closing Hibernate session"); try { session.close(); } catch (JDBCException ex) { // SQLException underneath throw new CleanupFailureDataAccessException( "Cannot close Hibernate session", ex.getSQLException()); } catch (HibernateException ex) { throw new CleanupFailureDataAccessException( "Cannot close Hibernate session", ex); } }
使用同样的方法，这两个Interceptor可以用来解决问题。但是关键的不同之处在于，它们的力度只能定义在DAO或业务方法上，而不是在我们的Test方法上，除非我们把它们应用到TestCase的方法上，但你不大可能为TestCase去定义一个接口，然后把Interceptor应用到这个接口的某些方法上。直接使用HibernateTransactionManager也是一样的。因此，如果我们有这样的测试：
Category parentCategory = new Category (); parentCategory.setName("parent"); dao.save(parentCategory); Category childCategory = new Category(); childCategory.setName("child");
parentCategory.addChild(childCategory); dao.save(childCategory);
Category savedParent = dao.getCategory("parent"); Category savedChild = (Category ) savedParent.getChildren().get(0); assertEquals(savedChild, childCategory);
一种方法是对TestCase应用Interceptor或者TransactionManager，但这个恐怕会造成很多麻烦。除非是使用增强方式的AOP.我前期采用这种方法(Aspectwerkz)，在Eclipse里面也跑得含好。
另一种方法是在TestCase的setup和teardown里面实现和Filter完全一样的处理，其他的TestCase都从这个TestCase继承，这种方法是我目前所使用的。
posted on 2004-11-18 15:11 逃离开发 阅读(856) 评论(1) 编辑 收藏 收藏至365Key
建立和配置操作都是在Redhat Linux8.0上做的。系统带的CVS可执行程序在/usr/bin下面，版本信息为：Concurrent Versions System (CVS) 1.11.2 (client/server)。系统带的这个cvs可执行程序既可以当客户端使用，也可以用来建立cvs源代码库服务器。
建立一个源代码库主要有以下几步：
（1）初始化cvs服务器环境。
#cvs -d/usr/local/source init
之后进入/usr/local/source，可以看到有一个目录CVSROOT, 下面是初始化后的CVS服务器配置文件。暂且保持不动。
（2）把cvs服务放到xinetd系统服务中。
首先在/etc/xinetd.d目录下生成任务配置文件cvspserver，文件名称可以随便用。
其中内容大致如下：
|
建立和配置操作都是在Redhat Linux8.0上做的。系统带的CVS可执行程序在/usr/bin下面，版本信息为：Concurrent Versions System (CVS) 1.11.2 (client/server)。系统带的这个cvs可执行程序既可以当客户端使用，也可以用来建立cvs源代码库服务器。
建立一个源代码库主要有以下几步：
（1）初始化cvs服务器环境。
#cvs -d/usr/local/source init
之后进入/usr/local/source，可以看到有一个目录CVSROOT, 下面是初始化后的CVS服务器配置文件。暂且保持不动。
（2）把cvs服务放到xinetd系统服务中。
首先在/etc/xinetd.d目录下生成任务配置文件cvspserver，文件名称可以随便用。
其中内容大致如下：
|
毕业后，我来到北京，开始了自己的工作和生活。
After I graduated, I came to Beijing, began working and started a whole new life.
繁忙的工作让我感觉到了生活的不易，还有就是我一个人在夜晚的寂寞和落寞。
I find that a working life is not easy, and it is also lonely at times, especially when I am alone at night.
那是一个周二的上午，办公室来了一个新的同事，她叫方若圆。
It is a Tuesday morning when a new colleague start at my office. Her name is Fong-Raw-Yuen.
方是一个很健谈很有朝气的女孩，对待工作和生活，她无比热情和投入。
I find she is a good conversationalist, very lively. She never takes life too seriously, always looking on the positive side of situations.
同为异乡客，我们很自然地走到了一起。
As strangers in Beijing, although we came from different cities, we become close due to the similar situation we are now in.
一个多月的相处，使我注意到她对我朋友般地好，我也开始慢慢喜欢上了她。
After we have been close friends for a month, I realize Fong is always very nice to me, and I begin to really like having her as my best friend.
我开始不自觉地为她做些事情，没有别的奢求，只是愿意对她好，想做她最好的朋友。
I want to tread her well as my friend unconditionally.
周末的时候，我们会骑车看北京的胡同。去爬香山，还在动物园给猴子起外号。
At weekends we often ride bicycles around the alley ways of Beijing, climb Shi-ang Mountain or even visit the zoo to give the monkeys nick-names.
我们把工作处理得井井有条，在单位，我们是相互帮助的好姐妹。
we work hard in the office, helping each other like sisters,
后来，我们一起搬出单位宿舍，在北京海淀区租了一套两居室的楼房。
We soon left our accommodations provided by work, and rent a 2 bedroom flat in Huai-diam District
方住在靠阳光的那间，我住在背阳光的那间。我们觉得很温暖。
Fong’s room faces daylight but mine is always in shadow. However we both feel warmth from our friendship.
我们在客厅里看电视，写文字，还常常上网和朋友们聊天。
We often write our thoughts down, watch TV or chat to others on the internet
最幸福的是晚上下班，我们一起去超市买蔬菜和食品。
Our happiest moment of the day would be after work when we go to the super market to buy things for tea.
我喜欢吃芹菜腐竹，方喜欢吃小鸡炖蘑菇。我们两个人一般要做3个或者4个菜。
I know Fong would like to eat different food from me, so we often cook 3 or 4 dishes for dinner.
方的英语都过了6级，而我却还停留在初级的水平。她就找时间给我补习单词和口语。
My English is very basic, but she has passed level 6, so I could practice my English with her
隔壁门口经常放着一双球鞋，门永远是关的，只是经常在夜里听到梁静茹的《勇气》：只要你一个眼神肯定，我的爱就有意义……
Our neighbor’s door is always closed, with a pair of trainers outside. We hear the music from the room, which is sang by a famous pop star, the lyrics described a love story.
感情就是这样，说不出原因。我和方互相喜欢，愿意在一起。
I and Fong think that the song describes the emotions we both feel, but there is no reason for us to feel that way.
我们终究没有逃开感情的网，虽然明知没有结果。
We can not deny our mutual attraction any more, but we know nothing would come of it.
仿佛世间只有我们两个，幸福地过着属于我们俩的日子。
The happiness is ours and it feel like the world belonged to us.
方要考研究生，她说那一直是她的一个梦想。我劝她不要上班了，在家里专心复习。
Fong’s dream is to take the ‘Master course’, I persuade her to quit work and follow her dream.
方就真的不再上班了，在家里看书。我每天下班她都做好了晚饭等我。
She stays at home each day studying and preparing food for when I get home from work.
有天快下班的时候，方约我晚上去吃酸汤鱼。饭后她送我一只可爱的小熊，我才知道今天是我的生日。
One day after work, Fong ask me to have dinner outside. After dinner she gives me a nice teddy bear and I realize it is my birthday today.
因有了方的关心，让我觉得这个大都市是我的。我抱住她流着自己的眼泪。
Because I feel so secure in her presence, I hug her and cry. I feel the whole city belonged to me.
晚上睡觉我都抱着小熊，我知道，我已经找到了归属的感觉。
Every night when I cuddle the teddy bear, I feel that I have found the place where I belong.
方的妈妈来北京了。吃着从家乡给我们带来的咸水鸭想起了我的妈妈，我笑笑也管方妈妈叫妈妈。
Fong’s Mother come to visit us in Beijing, she bring some traditional food from their hometown. She reminds me of my Mum. I even begin to call her ‘Mum’.
方妈妈给我讲了很多方的童年趣事，方小的时候和我一样，也玩过过家家游戏。
Her Mum tells me lots of interesting stories about when Fong was younger. She would play ‘house’
方妈妈就这一个宝贝女儿，她希望方早点结婚成家，她好来抱外孙。我和方相视一笑，都低下了头。
Fong is the only child in her family. Her Mum wants her to marry earlier, so she could be able to see
其实很多时候我也在想，我和方的感情到底是什么？
We do not know what our feeling for each other really is.
方妈妈走后，我问方，我们这样会有结果吗？我们刚刚开始，还是分开吧。
After Fong’s Mum left, I suggest that we should split apart because I am not sure about our future.
门里门外，我们俩都泣不成声。
We stand either side of the door crying heavily
我没有告诉方，周一上班的时候我带了很多的衣服，我准备回公司去住。
I take my belongings back to work on the following Monday, and plan to stay at the arranged accommodation, without telling Fong.
夜晚还是来了。我想方，辗转反侧。
The night finally comes, but I can not sleep. I am tossing and turning on the bed, thinking about Fong.
我决定给方打电话。在号码还没有拨完的时候，我收到了方发来的短信：玫玫，回来吧，我想你~-~。
I decide to call Fong, but receive a text message form her as I was dialing. It said that she miss me and ask me to come back to hers.
我擦下眼泪拿起包就往外跑，全然不顾同事的劝阻和莫名的表情。
I grab my clothes and things and run out the office. My colleagues try to stop me from going, but I ignore their confused expressions and leave.
道理我们都明白，但感情却是实实在在的。
We know it won’t be accepted, but our feeling is too strong
我的英语进步很快，方说是因为我聪明。我打她一下说，那当然了。
Fong say my English really improved because I am very clever. I laugh and playfully tap her.
打开日记本，这里面装的都是我和方的昨天。我认真记录着今天，也憧憬着我们的明天。
Looking at my journal, I read the past time shared between us, and write what I feel now, and ponder our future
天冷了。冬天还是来了。
The weather is getting colder as winter draws closer.
方是南方人，我怕她承受不了北京冬天的冷，去商场买了毛线，我要织件毛衣给她穿。
Fong is from southern China, so I worry that the weather in Beijing will be too cold for her. I go to buy wool to knit her a jumper.
最近单位老是加班，回到家都很晚了。每次进家总是方在看书，饭桌上放着做好的饭菜。我的心里有种莫名的感动。
Recently, I work at lot of OT, so I get home late, but I find Fong is studying and the food is ready. I fall touch by this.
毛衣织好了。方穿在身上高兴得什么似的，不停地照着镜子。
I finish the jumper for Fong. She is very happy and wears it in front of the mirror.
有天夜里我醒来，走到方的屋子，她睡着的姿势完全像个孩子，我轻轻地吻了一下她的额，我突然觉得，我们俩是那么的平凡和幸福啊！
At midnight one night I awake, and go into Fong’s room. She is sleeping like a baby; I kiss her forehead and realized how happy we are.
今天晚上有流星雨。我站在楼顶看流星，我想让流星等一等，我要许个愿，可是等一等就什么也看不见了。
At night there is a meteor shower. I stand at the top of the building to watch them, I hope the shooting stars could continue long enough for me to make a wish, but they never stop.
方来接我下班，雨伞下我搂着她的肩膀。看着路边行人望过来的目光，我赶紧松开了手。
Fong pick me up from work. I get under her umbrella ant put my arm around her. When I see people’s reactions to this, I put my arm back down.
方考上了研究生，真为她高兴。周末我拉着她一起去逛街。
We find out that Fong have got on to the ‘master course’. I am very proud and happy for her. We go shopping together at the weekend to celebrate.
夏天真好，蝉儿欢跃，街上到处都是漂亮的男生和女生。
The summer is come, and the cicada bug’s are singing loudly. The streets are filled with good looking boys and girls.
方经常给我讲她在学校的故事，还有排队去食堂打饭和有个连普通话都说不好的同学。
Fong tell me funny stories about her friends in university, who she chat in the canteen with. Some of them have strong regional accents, even sometimes she can not understand them.
上楼时看见一个男生手里拿个篮球匆匆忙忙地往下跑。我打开房门，方还没有回来。
One day, when I go into our apartment, I see a boy past me in the opposite direction carrying a basketball. I soon find that Fong is not in.
方最近总是回来很晚。我边看电视边收拾房间
Often lately, Fong has been coming home late. I have the television on while I tidy up.
慢慢地我发现，方说话的时候经常提到广这个名字。
After a few days I realize Fong have mentioned a boy called Gu-ang several times.
广是她们学校别的系的研究生，人很好。方说这话看我的时候，眼神有点游离。
Gu-ang is in a different department of Fong in university, he is always nice to people. When Fong talk about him, she avoids eye contact with me.
我披件衣服在自己身上，我觉得有点冷，心里。
Even though I throw on the clothes, I still felt cold in my heart.
今年的苹果不甜。望着远处的香山，叶子应该还没有红吧。
This year’s apples do not taste as good. I look into the distance at the red leaves on Shi-ang mountain should not be that colour yet
去学校看方，她和几个同学在操场上打羽毛球，还有个男生，我想就是广吧。
I visit Fong at her university and see her playing badminton with her friends. She is also whit a boy. I realize he must be Gu-ang.
傍晚，我和方去肯德基吃东西。
I and Fong go to KFC for dinner in the evening
我讲着未来也说些过去。方望过来的目光，让我假装自己做了个深呼吸。
We discuss the past and the future of us, she seems different from before, and this make me feel cold inside.
眼前的方模糊与清晰并存。模糊的是身影，清晰的是感觉。
I can not see Fong clearly, but her coldness towards me is easy to see.
我煮好她喜欢吃的小鸡炖蘑菇。我们专心地吃，没有一句对话。其实，这菜的盐放多了，非常咸，可我们却吃得干干净净...
I cook her favorite food. We ate without talking. Actually, I put too much salt in, but we still eat it all.
夜晚是美丽伤感的。天黑黑，心灰灰。
The night is beautiful but sad. It is black, but my heart feels darker.
扩展的 ASCII 打印字符表
评论
Karl Baum's Weblog
All | General | Java
Thursday July 08, 2004
Lazy Initialization and the DAO pattern with Hibernate and Spring
Hibernate and Lazy Initialization
Hibernate object relational mapping offers both lazy and non-lazy modes of object initialization. Non-lazy initialization retrieves an object and all of its related objects at load time. This can result in hundreds if not thousands of select statements when retrieving one entity. The problem is compounded when bi-directional relationships are used, often causing entire databases to be loaded during the initial request. Of course one could tediously examine each object relationship and manually remove those most costly, but in the end, we may be losing the ease of use benefit sought in using the ORM tool.
The obvious solution is to employ the lazy loading mechanism provided by hibernate. This initialization strategy only loads an object's one-to-many and many-to-many relationships when these fields are accessed. The scenario is practically transparent to the developer and a minimum amount of database requests are made, resulting in major performance gains. One drawback to this technique is that lazy loading requires the Hibernate session to remain open while the data object is in use. This causes a major problem when trying to abstract the persistence layer via the Data Access Object pattern. In order to fully abstract the persistence mechanism, all database logic, including opening and closing sessions, must not be performed in the application layer. Most often, this logic is concealed behind the DAO implementation classes which implement interface stubs. The quick and dirty solution is to forget the DAO pattern and include database connection logic in the application layer. This works for small applications but in large systems this can prove to be a major design flaw, hindering application extensibility.
Being Lazy in the Web Layer
Fortunately for us, the Spring Framework has developed an out of box web solution for using the DAO pattern in combination with Hibernate lazy loading. For anyone not familiar with using the Spring Framework in combination with Hibernate, I will not go into the details here, but I encourage you to read Hibernate Data Access with the Spring Framework. In the case of a web application, Spring comes with both the OpenSessionInViewFilter and the OpenSessionInViewInterceptor. One can use either one interchangeably as both serve the same function. The only difference between the two is the interceptor runs within the Spring container and is configured within the web application context while the Filter runs in front of Spring and is configured within the web.xml. Regardless of which one is used, they both open the hibernate session during the request binding this session to the current thread. Once bound to the thread, the open hibernate session can transparently be used within the DAO implementation classes. The session will remain open for the view allowing lazy access the database value objects. Once the view logic is complete, the hibernate session is closed either in the Filter doFilter method or the Interceptor postHandle method. Below is an example of the configuration of each component:
Interceptor Configuration
<beans>
<bean id="urlMapping"
class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
<property name="interceptors">
<list>
<ref bean="openSessionInViewInterceptor"/>
</list>
</property>
<property name="mappings">
...
</bean>
...
<bean name="openSessionInViewInterceptor"
class="org.springframework.orm.hibernate.support.OpenSessionInViewInterceptor">
<property name="sessionFactory"><ref bean="sessionFactory"/></property>
</bean>
</beans>
Filter Configuration
<web-app>
...
<filter>
<filter-name>hibernateFilter</filter-name>
<filter-class>
org.springframework.orm.hibernate.support.OpenSessionInViewFilter
</filter-class>
</filter>
...
<filter-mapping>
<filter-name>hibernateFilter</filter-name>
<url-pattern>*.spring</url-pattern>
</filter-mapping>
...
</web-app>
Implementing the Hibernate DAO's to use the open session is simple. In fact, if you are already using the Spring Framework to implement your Hibernate DAO's, most likely you will not have to change a thing. The DAO's must access Hibernate through the convenient HibernateTemplate utility, which makes database access a piece of cake. Below is an example DAO.
Example DAO
public class HibernateProductDAO extends HibernateDaoSupport implements ProductDAO {
public Product getProduct(Integer productId) {
return (Product)getHibernateTemplate().load(Product.class, productId);
}
public Integer saveProduct(Product product) {
return (Integer) getHibernateTemplate().save(product);
}
public void updateProduct(Product product) {
getHibernateTemplate().update(product);
}
}
Being Lazy in the Business Layer
Even outside the view, the Spring Framework makes it easy to use lazy load initialization, through the AOP interceptor HibernateInterceptor. The hibernate interceptor transparently intercepts calls to any business object configured in the Spring application context, opening a hibernate session before the call, and closing the session afterward. Let's run through a quick example. Suppose we have an interface BusinessObject:
public interface BusinessObject {
public void doSomethingThatInvolvesDaos();
}
The class BusinessObjectImpl implements BusinessObject:
public class BusinessObjectImpl implements BusinessObject {
public void doSomethingThatInvolvesDaos() {
// lots of logic that calls
// DAO classes Which access
// data objects lazily
}
}
Through some configurations in the Spring application context, we can instruct the HibernateInterceptor to intercept calls to the BusinessObjectImpl allowing it's methods to lazily access data objects. Take a look at the fragment below:
<beans>
<bean id="hibernateInterceptor" class="org.springframework.orm.hibernate.HibernateInterceptor">
<property name="sessionFactory">
<ref bean="sessionFactory"/>
</property>
</bean>
<bean id="businessObjectTarget" class="com.acompany.BusinessObjectImpl">
<property name="someDAO"><ref bean="someDAO"/></property>
</bean>
<bean id="businessObject" class="org.springframework.aop.framework.ProxyFactoryBean">
<property name="target"><ref bean="businessObjectTarget"/></property>
<property name="proxyInterfaces">
<value>com.acompany.BusinessObject</value>
</property>
<property name="interceptorNames">
<list>
<value>hibernateInterceptor</value>
</list>
</property>
</bean>
</beans>
When the businessObject bean is referenced, the HibernateInterceptor opens a hibernate session and passes the call onto the BusinessObjectImpl. When the BusinessObjectImpl has finished executing, the HibernateInterceptor transparently closes the session. The application code has no knowledge of any persistence logic, yet it is still able to lazily access data objects.
Being Lazy in your Unit Tests
Last but not least, we'll need the ability to test our lazy application from J-Unit. This is easily done by overriding the setUp and tearDown methods of the TestCase class. I prefer to keep this code in a convenient abstract TestCase class for all of my tests to extend.
public abstract class MyLazyTestCase extends TestCase {
private SessionFactory sessionFactory;
private Session session;
public void setUp() throws Exception {
super.setUp();
SessionFactory sessionFactory = (SessionFactory) getBean("sessionFactory");
session = SessionFactoryUtils.getSession(sessionFactory, true);
Session s = sessionFactory.openSession();
TransactionSynchronizationManager.bindResource(sessionFactory, new SessionHolder(s));
}
protected Object getBean(String beanName) {
//Code to get objects from Spring application context
}
public void tearDown() throws Exception {
super.tearDown();
SessionHolder holder = (SessionHolder) TransactionSynchronizationManager.getResource(sessionFactory);
Session s = holder.getSession();
s.flush();
TransactionSynchronizationManager.unbindResource(sessionFactory);
SessionFactoryUtils.closeSessionIfNecessary(s, sessionFactory);
}
}
( Jul 08 2004, 09:39:55 AM EDT ) Permalink Comments [2]
Trackback URL: http://jroller.com/trackback/kbaum/Weblog/orm_lazy_initialization_with_dao
Comments:
A few things to keep in the back of your mind if you take this approach; 1. If any errors occur while attempting to lazy load relationships in the view (JSP) it would be hard to present a nice error to the user. 2. This would result in at least 2 hibernate sessions (db connections being open for any one request), so you might want to up the number of connections available. Cheers, Dan
Posted by Dan Washusen on July 08, 2004 at 09:02 PM EDT #
I am a little confused on why it would be difficult to show a nice error jsp. Couldn't we just use the provided servlet container error page mechanisms? In regards to the 2 hibernate sessions being opened. Are you saying that the OpenSessionInViewInterceptor would be run twice if an exception was thrown? Thanks for your feedback!
Posted by Karl Baum (63.170.158.133) on July 09, 2004 at 09:48 AM EDT #