BlogJava-Have been sleeping for long time

Something you may ingore when to use Hibernate and JPA.

Find it, try it, experience it — Thu, 03 Apr 2008 08:32:00 GMT

The first is about identity generator, this is something I ingored and find really interesting later when I read back the document.

    When you choose "native" (for plain hibernate) or "AUTO" (for JPA which use hibernate as provider) as identity generator, it (actually they are the same identity generator but with different name in different scope) will pick other identity generators like identity, sequence, or hilo, depending on the capabilities of the underlying database. Use this generator to keep your mapping metadata portable to different database management systems.
    If your underlying DB is oracle, it will automatically create a sequence for you which means choose the sequence as identity generator, that's really interesting, at least for me for the first time when it comes to me.

The second is about the flush and close session operations when to use hibernate with JTA transaction.

    You should manually flush your operation by call flush method and close your session by calling close method when you try to use JTA transaction instead of hibernate Transaction API, these is because hibernate Transaction API does thoes operations automatically for you. But, with following configuration, it can also be done automatically for you by hibernate, though you are still with JTA transaction.

    hibernate.transaction.flush_before_completion=true
    hibernate.transaction.auto_close_session=true

The third is about an interesting code snatch listed as follow:

1     Session session = sessionFactory.openSession();
2     session.beginTransaction();
3     session.save(new Item());
4     session.close();

What happen if you don't commit the transaction? It's depends on the underlying DB, for oracle it will commit any uncommited transactions, but for many other DB vendors, they will roll back any pending transactions.

Find it, try it, experience it 2008-04-03 16:32 发表评论

A "Hello" program on EJB3 with Jboss server 4.2.2GA (PART 3) - EJB3 Timer service.

Find it, try it, experience it — Wed, 26 Mar 2008 05:30:00 GMT

Timer service in EJB3 with anotation is fairly simple, I give you an example as follow, and it's really simple and self-explanation:

1 package com.ramon.expejb3.session.impl;
2
3 import javax.annotation.Resource;
4 import javax.ejb.Stateless;
5 import javax.ejb.Timeout;
6 import javax.ejb.Timer;
7 import javax.ejb.TimerService;
8
9 import com.ramon.expejb3.session.Greeting;
10
11 @Stateless(name = "Greeting")
12 public class GreetingBean implements Greeting {
13
14     @Resource
15     TimerService ts;
16
17     /* (non-Javadoc)
18      * @see com.ramon.expejb3.session.Greeting#greeting(java.lang.String)
19      */
20     public void greeting(String name) {
21         System.out.println("Hello " + name + ".");
22         ts.createTimer(1 * 1000, 5 * 1000, name);
23         System.out.println("Create timer for " + name + ".");
24     }
25
26     @Timeout
27     public void timeout(Timer timer) {
28         String name = (String)timer.getInfo();
29         System.out.println(name + " TIME OUT.");
30         //timer.cancel();
31     }
32 }
33

    It's the "GreetingBean" I introduced in part one of this series article with TimerService injected, @Resource anotation inject the time service we want, it's totally free which is supported by the J2EE container that means we do not need any further steps to get the powerful schedule service. In the line 22, I crate a new timer, I think this could be more fit if it was called Task instead, there are several "createTimer" methods with different parameters, the one I used here describe the task should be execute 1 second delay and every 5 second one time in the future, the third parameter can be anything you want to pass in to the task, it can be get back use method Timer.getInfo() like line 28 does here.
    Another important anotation here is the @Timeout anotation, this anotation tell container which method will be called when timeout for this task to be executed, you can only specify one timeout method for each Bean, if there is no @Timeout anotation at all, you will get some exception like "No timeout method specified" in Jboss server. Something funny here is that you should mark the timeout method as "public", otherwise, you will get the same error as no timeout method does, I do NOT think it's necessary, because the time out method should only be called by the container, "private" signature is enought for that, with "private" signature container still has the right to access this method with java reflection, nevertheless timer service in EJB3 is still a good tools for use.
    I summarize what good/bad for timer service in EJB3 as follow:
    Good news:

It's free, it's supported by the EJB container.
It's portable, it's supported by the EJB container as specified in EJB3 specification.
It's easy to use, no need to learn more.

Bad news:

The feature of EJB3 timer sevice is not as powerful as some third party timer service such as Quartz, but it's enough with EJB3 for ordinary daily job.
There is no UI for you to monitor the timer you created.

Find it, try it, experience it 2008-03-26 13:30 发表评论

A "Hello" program on EJB3 with Jboss server 4.2.2GA (PART 2) - EJB3 MDB with Jboss server.

Find it, try it, experience it — Tue, 25 Mar 2008 09:42:00 GMT

摘要: MDB is the MVP(most valuable player) both in previous EJB version and EJB3. Although coding with MDB is simple in EJB2.x, EJB3 make it much more friendly to you. Let's get to the ... 阅读全文

Find it, try it, experience it 2008-03-25 17:42 发表评论

A "Hello" program on EJB3 with Jboss server 4.2.2GA.

Find it, try it, experience it — Fri, 21 Mar 2008 08:02:00 GMT

    Recently I did some research on EJB3 programming, find that it's really simple than programming with previous EJB version. Coding in EJB2.X or previous version is really a nightmare for most developers, maybe for this, EJB3 gives me much more impression than Spring when it first comes to me, this article is the first one of these series articles which record the new knowledge I find interesting in EJB3.

    Well, let's begin.

    EJB3 is simple with AOP and DI, there is no Home interface any more, only with Service Interface and your Service implementation you can create an typical EJB3 application. I will create a simple hello world program in this article, the service interface as follow:

1 package com.ramon.expejb3.session;
2
3 import javax.ejb.Remote;
4
5 @Remote
6 public interface Greeting {
7
8     /**
9      * say hello test
10      * @param name
11      */
12     void greeting(String name);
13
14 }

It's really simple, especially for you that are familiar with programing with Interface, after that is the service implementation code:

1 package com.ramon.expejb3.session.impl;
2
3 import javax.annotation.PostConstruct;
4 import javax.annotation.PreDestroy;
5 import javax.ejb.Stateless;
6
7 import com.ramon.expejb3.session.Greeting;
8
9 @Stateless(name = "Greeting")
10 public class GreetingBean implements Greeting {
11
12     @PostConstruct
13     public void init() {
14         System.out.println("Init Greeting Bean.");
15     }
16
17     @PreDestroy
18     public void destroy() {
19         System.out.println("Garbage collect Greeting Bean.");
20     }
21
22     /* (non-Javadoc)
23      * @see com.ramon.expejb3.session.Greeting#greeting(java.lang.String)
24      */
25     public void greeting(String name) {
26         System.out.println("Hello " + name + ".");
27     }
28 }
29

Still simple and very self-explanation, @Stateless(name = "Greeting") specify the JNDI name for client invocation. OK, that's all for our EJB jar file, no more file needed for this simple hello application. Execute your ANT script make a jar for it, part of ANT script may look like:

1     <target name="prepareexpejb3" description="Create exp_jsf distribution.">
2         <mkdir dir="${dist.dir}" />
3         <mkdir dir="${build.dir}" />
4         <mkdir dir="${build.core.dir}"/>
5     target>
6
7
10     <target name="compileexpejb3" depends="cleanDist,prepareexpejb3">
11         <javac destdir="${build.core.dir}" debug="yes" deprecation="on" srcdir="${src.dir}">
12             <include name="${core.src.dir}/**" />
13             <classpath refid="expejb3.classpath" />
14         javac>
15
16     target>
17
18
21     <target name="createEJB3Jar" depends="compileexpejb3">
22         <jar jarfile="${dist.dir}/${expejb3.core.name}.jar">
23             <fileset dir="${build.core.dir}">fileset>
24         jar>
25     target>

Put the EJB jar into jboss server server\default\deploy, you should see some log from jboss console like:

1 10:59:27,036 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.St
2 atelessContainer
3 10:59:27,051 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=expejb3core.jar,name=Gree
4 ting,service=EJB3 with dependencies:
5 10:59:27,208 INFO  [EJBContainer] STARTED EJB: com.ramon.expejb3.session.impl.GreetingBean ejbName:
6 Greeting

Which mean that you have successfully deploy your EJB into jboss server, create a client code to invoke your EJB service:

1 package com.ramon.expejb3.session;
2
3 import java.util.Properties;
4
5 import javax.naming.Context;
6 import javax.naming.InitialContext;
7
8 import junit.framework.TestCase;
9
10 public class ExpEJB3BaseTestCase extends TestCase {
11
12     private Properties properties = null;
13
14     private Context context;
15
16     protected void setUp() throws Exception {
17         super.setUp();
18         properties = new Properties();
19         properties.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
20         properties.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
21         properties.put("java.naming.provider.url", "localhost:1099");
22         context = new InitialContext(properties);
23     }
24
25     protected void tearDown() throws Exception {
26         super.tearDown();
27         context = null;
28         properties = null;
29     }
30
31     public final Context getContext() {
32         return context;
33     }
34
35     public final void setContext(Context context) {
36         this.context = context;
37     }
38
39 }
40

1 package com.ramon.expejb3.session.impl;
2
3 import javax.naming.NamingException;
4
5 import com.ramon.expejb3.session.ExpEJB3BaseTestCase;
6 import com.ramon.expejb3.session.Greeting;
7
8 public class GreetingBeanTest extends ExpEJB3BaseTestCase {
9
10     public void testGreeting() {
11         try {
12             Greeting greetService = (Greeting)this.getContext().lookup("Greeting/remote");
13             greetService.greeting("Ramon");
14         } catch (NamingException e) {
15             // TODO Auto-generated catch block
16             e.printStackTrace();
17         }
18     }
19
20 }
21

That's really simple, right? What you should note is that you must include following jars into your classpath when you run this clien test case, otherwise you will get the annoying classNotFound Exception:

1 concurrent.jar
2 jboss-aop-jdk50.jar
3 jboss-aspect-library-jdk50.jar
4 jboss-common.jar
5 jboss-ejb3.jar
6 jboss-ejb3-client.jar
7 jboss-remoting.jar
8 jbossx-client.jar
9 jboss-transaction-client.jar
10 jnp-client.jar

Find it, try it, experience it 2008-03-21 16:02 发表评论

编码字符集与Java －Java World乱码问题根源之所在。

Find it, try it, experience it — Sat, 23 Sep 2006 16:08:00 GMT

摘要: 本文介绍了编码字符集的概念以及Java与编码字符集之间的关系，文章的内容来自于本人工作过程中的经验积累以及网络中的相关文章介绍，如果文章中有任何纰漏欢迎读者指正，让我们共同讨论学习J1．字符字符是抽象的最小文本单位。它没有固定的形状（可能是一个字形），而且没有值。“A”是一个字符，“€”（德国、法国和许多其他欧洲国家通用货币的标志）也是一个字符。“中”“国”这是两个汉字字符。字符仅仅代... 阅读全文

Find it, try it, experience it 2006-09-24 00:08 发表评论

计算机中[1]和[-1]的趣事.

Find it, try it, experience it — Wed, 20 Sep 2006 12:59:00 GMT

首先感谢南老师!

      在计算机里的有符号数，最高位的1用来表示负号，所以，用 0000 0001表示正1，1000 0001表示-1，确实对人来说很直观。但其实，计算机里的数是用“补码”表示的。其中正数的补码就是原来的数（称为原码），而负数的补码是这么算的，我用倒推的来说：
      补码 = 反码 + 1
      反码 = 原码按位取反（1变0，0变1）
      所以，-1就是1取补码，过程如下：
      先取反 0000 0001 ---> 1111 1110
      然后加1得补码： 1111 1110 + 1 = 1111 1111
    （当然这里为了方便，就取了8位，其实整数现在都是32位了，结果是32个1）。

     现在，你知道如何计算-2了吗？为什么要搞反码，补码这么个转换呢？这个原因要说长就很长的，但简单地讲，这又是一个在人的直观和机器的高效之间取一个平衡：
     我们先来看一个10进制的数运算：
     1 + (-1) = 0 //10进制中，1加负1应为0.
     然后，假如用1000 0001来表示－1的话。按照计算机计算加法的规则，它是每位加的，结果是：
     0000 0001 + 1000 0001 = 1000 0010  //-2
     结果变成－2了，其中后面两个0001 相加变成2，而前面的用于表示负号的1，被“继承”下来了……显然，原来计算机最直观的（对人来说也很直观的）算法，不灵了！怎么办？痛苦

    但更痛苦的事还在0这个数上。按10进制，0和-0可是完全相等的。但如果用二进制，0000 0000 和 1000 0000 参加起运算，可是完全不同。或许可以通过电路设计，来强制让计算机去实现一个规则：碰到1000 0000就先转换为0000 0000。但可要知道加减法计算是计算机计算一切的基础，如果从这最底层就必须有一个转换会极大影响性能！何况前面那个问题也必须有个强制规则！规则最好越简单越好，那就是规定前面的补码转换规则，这个转换过程对于计算机来说很迅速的逻辑电路转换。

    你看，第一个问题 1 ＋（－1）
0000 0001 + 1111 1111 = 0000 0000
    看明白这个计算过程吗？其实就是最低位的两个1相加后，造成每一位都进位，最高位直接溢出（丢了）。如果你还算不清，就算算这个10进制的：
    1 + 999 =  1000 (最高位1丢失，就成0了)
    然后是第二个问题，0的表示。如果您把0当成正数，那么它是这样表示的：
    0000 0000
    如果你当它是负数，那么
    取反 1111 1111 ，再加1，以求补，哈哈又成 0000 0000这回在逻辑上没有错误了！明白了吧？当补我在学习这一段知识时，只能说：高，实在高！想出补码的前辈，真是高人啊。

Find it, try it, experience it 2006-09-20 20:59 发表评论

Unit Testing against Struts action(Controller in MVC), In-Container or Mock Objects which One Should We Choose?

Find it, try it, experience it — Thu, 06 Jul 2006 15:11:00 GMT

This article is focused on which approach we should choose for unit testing against Struts action, I hope it will give you some help when you have question on how to do unit testing against the controller in MVC.

OK, let's begin!

In container? Mock objects?

There are two kinds of testing, one is in-container and the other is do testing with mock objects. Generally speaking, it was considered to be more really and truly unit testing when you do testing with mock objects, especially when you do testing against java source files which should be run in J2EE container, but as our code become complex which contain more layers, the controller(Struts) will have more depends on the other layer which may be EJB service or other business objects, so when you do unit testing against view layer(here is Struts), it will be a huge work for you to construct the mock objects and also it will have more source code changed as you apply mock objects in your source code, the following is a simply description which describe the classic three layers project, and also considerd to be the most common type of web based project.

e.g. the Struts action class first call the EJB factory to get an EJB service, and then ask this EJB service to do the work according to the business logic and return the value we need, with the value EJB service returned the action class can choose which page to redirect or do some other data processing ,this could be the classic three layers type, maybe the most common type project we used in our project.

Therefore, it may not be the best choice for every web based project to apply mock objects unit testing. In the case that Struts action class is close tied with your business object, in-container testing may be an alternate choice for you, because it save your time to write mock objects and the workload to apply the mock objects into your source files but supply the same testing resluts.

In-container testing sounds good, but when you do testing in this style, it first assume that the depended business service classes used in our Struts action must be verified, if the depended service classes have some defect that happen to be met when we run in-container testing, it will take more time to find which cause the error indeed.

But I think if we have a complete testing procedure, which cover the service layer and the controller, the service layer have already been verified properly, in-container testing is really the best choice for you to use for testing action class. For project in practice, the Struts action is more or less close tied with other layer, it's not realistic to spend more time on writing mock objects or modifying your source code to apply the mock objects. In my opinion, the recommended solution is that you should focus on Struts layer testing, if the Struts action code is close tied with other service layer which I mean is that there may be only one execute() method in every Struts action take charge for the whole business logic, you should use in-container testing, let other unit testing stuff take charge for service layer which may be out of container unit testing against EJB, in this way you can write your test case at your pleasure, forget the depended layers for a while, the container will take care for other layers for you, and also it will save you lots of time for writing mock objects, the container will give you the real objects instead of mock objects.Mock object testing is more often used for the simple Struts action or the case that it could be influenced by the container when you do unit testing against Struts action.

Find it, try it, experience it 2006-07-06 23:11 发表评论

Wow~~ It will be a new beginning for me!

Find it, try it, experience it — Tue, 04 Jul 2006 17:06:00 GMT

I will write some thing when I have time tomorrow, sorry, it's already 1:00 AM at midnight, so you guys could see some thing right now, hey hey. It's mainly about how to automatic do unit testing in container with strutstestcase and ANT, hope it will be useful for you guys.

Find it, try it, experience it 2006-07-05 01:06 发表评论

好久一段时间没有更新了....明天继续java学习旅途，哈哈哈，加油！

Find it, try it, experience it — Sat, 07 May 2005 09:16:00 GMT

自己的激励帖！

Find it, try it, experience it 2005-05-07 17:16 发表评论

one-to-one的效率问题，用one-to-many来替代？

Find it, try it, experience it — Wed, 30 Mar 2005 05:26:00 GMT

         由于最近在把以前的一个设计移到hibernate上来，所以需要用到one-to-one，因为在以前的设计中需要用到在一个主表中对于多个子表的主键关联，所以一开始就想到了one-to-one的应用，觉得这样解决不但不会引起以前数据设计的改变，也能够很好的利用hibernate所带来的OR优势，可是当实际使用的时候发现，在插入数据的时候可以有选择的在任意子表中进行插入，所有的结果都在原来的预期之中，但是在查询的时候，比如说只查询主表中的内容

         From tableMain

仅仅执行看起来十分简单的一条语句，你所期望的是他紧紧查询T_MAIN这张主表，可是结果确实hibernate通过多个外连接将所有的子表一口气的全部查询出来

         select * from t_main main outer join t_sub1 sub1 on main.id = sub1.id outer join t_sub2 sub2 on main.id = sub2.id...

如此的效率绝对让你头痛不已，不仅如此，如果你通过首先获得子表t_sub1的某个主键ID，然后通过这个主键查询出子表对象，在关联至住表，同样的情况又会发生，又会生成类似的SQL语句，这样一来看来对于这个设计应用one-to-one本身就是一种错误，是这样吗？

         或许有人认为我们在每个one-to-one中加入lazy="true"这个属性会杜绝上述情况的发生，经过笔者的证实即便你加入了lazy="true"，也不会带来任何的改变；又或者在hibernate.config中加入fetch depth属性以及在每个关联中设置outer-join="false"，这些都不会引起本质上的变化，加入outer-join="false"其实结果只是将原有的outer join语句改变成多条sql语句而已，并没发生什么本质变化，反而效率更低了。

         该怎么办呢？我们先仔细研究一下one-to-one的概念，one to one代表一对一，在一般的模型中很少会遇到one-to-one这种概念，因为他十分强调一对一的概念，就好比一个人他只有一个身体和一个头而已，头和身体是十分好的例子，因为有身体必定只有一个头，而且说到了身体必定要说头，就好像看了某个女孩的身材必定想知道她的长相如何（-_-），所以在这时我们使用one-to-one，因为这种一对一的关系是很强的，而且从对象中取得body必定会取得他所关联的head，这样的情况下使用outer-join是十分方便和有效率的，因为它使用了outer join查询从而避免了两条到数据库的查询语句，而且在这种情况下也只需要在body_hbm.xml中设置一个one-to-one即可，所以在这种确实是一对一而且在主表中一对一的关联个数（即主表中one-to-one标签）十分少的情况下，使用one-to-one是一种很不错的解决办法。

         如果一个主表会对多个子表都进行one-to-one关联呢，就像我们一开始遇到的这种情况，比如你不仅仅只想了解那个你中意的女孩的身材和脸蛋，而且还想知道他的学历，身世等等一切，在这种情况下，如果我们都是用多个one-to-one在主表中的话，那情况正如我们一开始看见的，是十分可怕的，该怎么做呢？不妨考虑一下使用one-to-many，什么，many?一开始听到many这个词的时候，我也觉得挺惊讶的这明明是多个一对一的关联为什么要用到many呢？其实many并没有一定要说是大于一的，你就只在它的many中存在一个关联它有能乃你何呢？如果用到many的话，我们就需要改动数据表的设计了，在每个有关连的子表中加入一列main_id代表主表中该记录的主键子段值，只需要这样子改动就可以了，这样所带来的效果绝对是值得你这样做的，然后我们就按照以往的one-to-many来设计就好了

         在body.hbm.xml加入（一到head的关联举例，其他的关联按照这样的格式添加即可）

在head.hbm.xml加入

         行了，经过上面的改动我们就摆脱了查询时多个outer-join的困扰，只在需要的时候才对子表进行查询，因为设置了lazy="true"，所以一切的一切都在我们的预料之中，我们如果希望获得body的话hibernate绝对不会把它的head 也查询出来，节省了查询是所需要的负担，除非到了我们十分需要head的情况才会进行关联查询，获得所需要的head结果。

         所以由此看来在one-to-one这种一对一的关系不是很强的情况下，或者是在一张表中存在多个one-to-one的情况下，使用one-to-many来代替one-to-one不失为一种不错的做法，当然更重要的良好的数据库设计，hibernate毕竟只是末，千万不要本末倒置。

Find it, try it, experience it 2005-03-30 13:26 发表评论