1)将 冬瓜去皮、去瓤，切成小厚片；瘦肉剁成末待用。 不宜用肉片。

2）将植物油放入锅内，下入肉末煸至变色，投入葱姜蒜末，散发香味后放入酱油、榨菜、冬瓜煸炒几下，加少许水烧3～4分钟（一般足够），视冬瓜已烂，淋入淀粉勾芡，淋上香油，出锅即成。

盐要早放。

材料：瘦肉末、北豆腐、辣椒酱

工序：

1、瘦肉末炒熟盛出

2、油七成热加入辣椒酱，炒出香味，加入豆腐翻炒。

3、加水稍炖，让辣椒酱入味。

4、加入肉末翻炒，加入盐、味精、收汁淋芝麻油。

其实做法与酱汁豆腐大同小异，只是酱汁豆腐味道咸香、麻婆豆腐麻辣。

find a "web service debug tool". It should have some features:
1) monitor SOAP message. a common http monitor can reach this
2) modify the out/in SOAP message. Some like the IDE debug stepping mode
3) invoke a web service. Some like "web service explorer". Every SOAP has a method name?



否定的才是真实的(X)。
/《门徒》中刘德华演绎的很真实贴切。
/《投名状》中李连杰是电影中的亮点，也是其演艺技术发展的一个转折点。
这些演员在影片中原来都是典型的正面角色，正义和勇敢的化身。为什么他们在演反面角色能让人感到眼前一亮呢？
多数人的人性中多多少少隐藏有恶的一面，把这一面显示出来，就摆脱了虚伪，显示了真实的残酷。

  Ajax4JSF is a framework which inserts AJAX function to JSF. It is easy to transform orginal JSF code to Ajax-able. Ajax4JSF just changed the way of    http message.

    It's document is here. It has a simple example. Look at blow code:
     <a4j:commandButton action="#{Page1.do2}" reRender="rep2" value="Link"/>
     <h:outputText binding="#{Page1.rep2}" id="rep2" value="#{RequestBean1.name}"/>
   the reRender property points out whose data in JSF component tree should be return from server. After JSF engine renders that component, Ajax4JSF then sends response. So this approach didn't do harsh to JSF. We can code in JSF bean:
     private HtmlOutputText rep2 = new HtmlOutputText();
     ......
     String style="border-color: rgb(204, 0, 255); backgroun.....";
     this.rep2.setStyle(style);
   We can see the benefit of JSF component model. But this model don't consider the position of the javascript or it is hard to add javascript function. For example, if we want to hightlight the outputText, Should I write a new class extends HtmlOutputText which has a cool appearance? Maybe a Decrtor Pattern is better. No matter which approach we use, we should encapsulate the javascript into JSF component and give user a consistent usage. On the other hand, If we have a JSF component which is not ajax-able but provides hightlight function, we can use it directly in Ajax4JSF. So the problem is the matter of JSF instead of Ajax4JSF.

    By comparison with other plugs such as RadRails, CDT is more mature. It is a full-functional developing environment. It is open-source and managed by eclipse.org.
    After installing it to eclipse, you should install a c++ compiler. I use gnu provided by cygwin. Maybe It is easiest approach to setup the environment in Windows. Then install g++ compiler, make and gdb in cygwin setup. At last add the cygwin/bin to system path, so you can invoke those library in eclipse. Eclipse don't provide an entry to configure which compiler you want to use as do for jdk. But I think there is some way to change the compiler to your favorite one.
    (Later I tested it in linux, and I found that the compile process was much more quickly than in Windows.)
    In evaluating CDT, you will find that only after you has compiled your code, then you will get some error. But eclipse will analyse the result from compiler and can point out at which line in code maybe there is an error. Will done! But the hint is some confused and javac will give us more information.
    There is a nice feature: when you save your code, eclipse will build or make the project automatically. Some like the way done in java.
    In summary, if you will develop c++ code with gnu compiler or in linux environment, CDT is a good choice.

support drag&drop, generate SQL, and criteria editing.
video is here.

    最近RIA好像比较火，一直没大注意，今天看了看Flex。（微软的RIA方案是WPE。）
    从Java开发人员的角度看，Flex最大的优点在于其是基于J2EE的，且将其势力范围局限到前端显示，显然这是明智的，也提高了认可度。
    Flex的砝码在于flash的广泛的支持，可以有跨平台的美誉，其拥有的用户数量就是它的最大财富。

    而比较AJAX，缺点可能在于效率方面。网络速度提高后，这应该不是问题。个人觉得主要还是习惯上的，企业级的应用可能觉得flash有些花哨，现在Web2.0的主流站点都将页面做的极端简洁，这也是审美的一个趋势。
    RIA的强处在于良好的交互性和丰富的页面显示，问题在于：是这些强处只在某些特定的应用程序（比如数据的图表显示）才有“英雄用武之地”，还是一个好的web应用程序所必须的呢？如果web的本质在于传递文字信息，而AJAX也只是在HTTP基础上的一个锦上添花，Flex还能撼动DHTML地位吗？
    在开源流行的今天，Flex几乎所有的技术都是私有的，ActionScript也不是标准，只有其IDE是基于eclipse的这点还能让人感到一丝兴奋。其进入主流技术还是比较困难。
    也许用户的口味需要Flex来培养，需要一个killer级的程序，就如GMail转眼就让大家接受了AJAX一样。

    这个帖子很不错，可以参照来学习Ruby。总结来说Ruby的优点在于：
* closures
* multiple implementation inheritance via mixins (simplifies a lot designs where we would use decorators and factories in java)
* messages to objects as if they were first class methods (natural way of doing AOP, used a lot in ActiveRecord). This actually also counts for the famous java properties support planned for java 7...
    缺点在于没有了Java的类型检查，而这是提高Java开发效率的关键：通过编译就可以排除大部分的错误，也提高了系统的安全性。但是在开发一个完整的Java应用时，经常会遇到DSL语言的地方，比如jsp, sql，这些都是没有办法进行类型检查的地方（DSL的特点吗？）。再比如对Session的处理不可避免的会用到类型cast。
    在RJS里面，html, rjs, rb这些文件之间存在的变量type和name的合约（或契约）更多，而只能手工检查。
    疑问：Ruby里面method的参数的类型会在运行时进行类型检查？
    那JRuby会起到一个粘合剂的作用吗？这会提高系统的复杂性，而且一个系统中使用两种语言也少见，除非是一个遗留系统。

    最近忙于找工作，荒疏了一些东西。
    1.pet store 2.0发布了。看上去好像是web 2.0的跟风作品，AJAX，RSS，TAG，SEARCH都用上了，还没来仔细研究。用了不少开源的库，可以借鉴下。
    2.一则netbeans有了新的插件：Visual Web Pack，看上去很不错的东西，应该是从creator里面提取出来的，这样比较eclipse的web开发，netbeans强了很多。记得原来使用creator时，由于deploy服务器只能使用sun application server，速度很慢，还设法过把部署环境改为tomcat，这下方便多了。
    产品的定位跟Microsoft visual web developer express类似。
    相比下，eclipse的可视化编辑界面就差了很多，VE发展到现在还是个小玩具。个人感觉Swing比较swt可能难看点，但是灵活性更好些。
    3.新的application server增加了很多SOA的支持，比如REST，BPEL。有个netbeans演示BPEL开发过程的Video，图形拖放的方式，很是cool。

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

embrace change
quickly iterate
incremental design
xp's value: communication, simplicity, feedback, courage, respect
baby step
continuous integration
start with the hardest